Open SJoWie80 opened 1 year ago
Hi!
The second error seems to be due to the tweets
folder having leftover files from the first failed try, so that's no the real issue here.
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://<*>/api/v1/media
Very interesting, an error HTTP 404 Not Found
seems to be returned from the endpoint https://<*>/api/v1/media
You mention the server is running Pleroma, do you know which version specifically? Perhaps there were some changes on a newer version to their API?
Could you try the endpoint directly like this to confirm it exists?:
$ echo "test" > test.txt
$ curl -i -X POST -H 'Authorization: Bearer YOURPLEROMATOKEN' \
-H "Content-Type: multipart/form-data" -F "file=@test.txt" https://<*>/api/v1/media
I find it a bit weird it returns 404
, it shouldn't at least according to their documentation:
https://api.pleroma.social/#operation/MediaController.create
Hi,
pleroma version is 2.5.1 The result of the curl is:
HTTP/2 200
server: nginx/1.22.1
date: Wed, 22 Mar 2023 08:30:22 GMT
content-type: application/json; charset=utf-8
content-length: 466
access-control-allow-credentials: true
access-control-allow-origin: *
access-control-expose-headers: Link,X-RateLimit-Reset,X-RateLimit-Limit,X-RateLimit-Remaining,X-Request-Id,Idempotency-Key
cache-control: max-age=0, private, must-revalidate
content-security-policy: upgrade-insecure-requests;script-src 'self' 'wasm-unsafe-eval';connect-src 'self' blob: https://
{"blurhash":null,"description":"","id":"88","pleroma":{"mime_type":"text/plain"},"preview_url":"https://
Hello,
Any idea? i get firstime running (with empty tweets folder etc):
pleroma-bot --forceDate 2023-02-28
Second time running:
pleroma-bot --forceDate 2023-02-28
i om on the latest version: 1.2.1rc20 Connecting to an pleroma server
My config file
ofcourze with the right info instead of the <*> :)
Regards, Joey