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
Question: Mastodon AUTHORIZED_FETCH not working? #4451
Comments
You need to enable |
Can you tell me how? |
Firefox has an option to copy the request from dev tools as curl command, then edit it and add the param. Otherwise simply edit directly in the db with psql. |
Sounds like you wrote it wrong. Best try it directly via psql. |
Hi, sorry to jump in here but hoping for some clarification from the user side.
Pointers much appreciated, just trying to wrap my head around the issue before trying to action anything. Thanks! |
this is what mastodon says |
Yeah federation from my Mastodon server to Lemmy broke when this was turned on on the Mastodon side. Been living without crosspost ability for three months now and it sucks! But if I'm understanding this thread correctly, in order for federation to start working again it's the Lemmy admins that would need to enable a setting on their side? The This is the one I'm struggling to find info on, sorry if that was unclear. |
Open
Its disabled mainly because its not required for Lemmy to work. Specific disadvantages are: every federation request gets signed now so it will use slightly more cpu (but I doubt it would be noticable in practice). Also remote servers know which instance is fetching which objects. This could be considered a privacy issue for single-user instances. |
Does anyone happen to have the commands to hand? I work relatively rarely with docker |
|
here is a short guide for those who also want to change it:
|
According to /api/v3/site "federation_signed_fetch" is now active but when I activate AUTHORIZED_FETCH on the mastodon instance it still comes up:
|
Are there any relevant logs on the Mastodon side? |
In the sidekiq_push log: HTTP::TimeoutError: Read timed out after 10 seconds on https://hubzilla.eu/inbox
|
Those logs dont look relevant, and anyway what does Hubzilla have to do with it? |
I have simply provided all the logs I have found for this case. I don't run a hubzilla instance, so I can't answer that for you. |
Just wanted to share that we're getting this error after restart when enabling it:
|
Ah after a restart I get the same error and the ui no longer connects |
@corgana Thanks, I just noticed the same problem and fixed it in #4516. Not sure if anything else is needed, there is some additional discussion in superseriousbusiness/gotosocial#2697 |
is the branch available as a docker build? then I would test it. |
You can test with ds9.lemmy.ml where Ive deployed it. Anyway its not working yet because Mastodon has some weird requirements. Edit: Got it working now. |
Tested to ds9.lemmy.ml from a Mastodon instance with |
Also tested, works: https://ds9.lemmy.ml/post/9603 |
Question
Hello,
can it be that Lemmy cannot talk to Mastodon instances if the instance AUTHORIZED_FETCH is activated?
The text was updated successfully, but these errors were encountered: