-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error #127
Comments
Hi!
You mention the server is running Pleroma, do you know which version specifically? 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 |
Hi, pleroma version is 2.5.1 HTTP/2 200 {"blurhash":null,"description":"","id":"88","pleroma":{"mime_type":"text/plain"},"preview_url":"https:///media/d9295dfe-f978-4dd5-ac04-fbe689a5be99/test.txt","remote_url":"https:///media/d9295dfe-f978-4dd5-ac04-fbe689a5be99/test.txt","text_url":"https:///media/d9295dfe-f978-4dd5-ac04-fbe689a5be99/test.txt","type":"unknown","url":"https:///media/d9295dfe-f978-4dd5-ac04-fbe689a5be99/test.txt"} |
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
The text was updated successfully, but these errors were encountered: