Wow this “policy” has 3700 lines in total. It must take a lot of time to create and maintain it. How does someone even find the time for that?

I tried to access some blocked users and communities via tesseract.dubvee.org and it simply shows a generic “Not Found” error. So this is impossible to figure out for the average user. Even for developers it would be hard to figure out if the JSON file was hidden a bit better.

Strange, I opened an issue: https://github.com/LemmyNet/lemmy/issues/6609

Okay in the browser dev tools open “Storage” tab and go to “Local Storage”. There should be an item oauth_state with a value like {"state":"xxx","oauth_provider_id":1,"redirect_uri":"https://voyager.lemmy.ml/oauth/callback","prev":"/","expires_at":1783389838355}. Sounds like one of those items is missing.

Request error while calling POST /oauth/authenticate with {“code”:“3ed55281d78996fe5c2f”,“oauth_provider_id”:1,“redirect_uri”:“https://voyager.lemmy.ml/oauth/callback”}

This must be the problem but I dont know what it means. Check the network tab in browser dev tools for that request, and see whats the response or why it failed.

Tried the Github signup just now and it worked fine. You approved the Lemmy login once it redirected to Github right? Maybe try going into your Github settings and removing Voyager entry, then try again. Also check the browser console for any errors. And try a different browser, or disabling privacy plugins.

We wiped the data on voyager at some point so your existing account is probably gone. You can just make a new account with the same name.

Normally Lemmy returns an error if activities cant be handled (eg instance is down). Then the sending instance keeps retrying until it is successful. But in this case its a bit different, and the sending looked successful.

Anyway I made a change to the federation library to add Host header automatically if missing, then this problem wont happen anymore in the future.

Old posts and comments will come in when we receive votes or replies for them. But missing votes won’t be federated.

I found it now, posts are coming in normally again.

Its unrelated, problem was from removing Host header in nginx.

Found the problem, I had commented out the Host header in nginx thinking it would not be necessary. Turns out I was wrong. Adding the header back in fixed the problem.

Big thanks for notifying about this!

You’re right, its also really noticable if you just compare the All feed, on lemmy.ml almost everything from local users. Most posts from other instances are missing. In the server logs are a lot of errors like this:

lemmy-1  |    0: lemmy_server::root_span_builder::HTTP request
lemmy-1  |            with http.method=POST http.scheme="http" http.host=0.0.0.0:10633 http.target=/inbox otel.kind="server" request_id=780b6573-2672-4361-87c2-6ece46e272ee
lemmy-1  |              at src/root_span_builder.rs:16
lemmy-1  | 2026-06-09T17:34:25.537123Z  WARN lemmy_server::root_span_builder: Unknown: Incoming activity has invalid signature

I thought at first that it would be related to the new 0.19.19 release, but downgrading to 0.19.18 doesnt fix the problem.

Issue link: https://github.com/LemmyNet/lemmy/issues/6581

Dont know whats going on with these comments, but federation status shows up to date in both directions:

• https://phiresky.github.io/lemmy-federation-state/site?domain=hexbear.net
• https://phiresky.github.io/lemmy-federation-state/site?domain=lemmy.ml

Right, 1.0 still needs some more months of development before it’s ready for production.

We are running a beta version on lemmy.ml right now. But it only has minor changes, I guess it should properly be called a release candidate too.

Why do you think that? We are actually running a beta version right now.

Edit: or do you mean testing 1.0 on lemmy.ml? There are still various changes needed before it’s ready for that.

Youre right, made a PR to fix that.

https://github.com/LemmyNet/lemmy/pull/6562

Okay Ive added it.

Found the problem, on 0.19 you have a very long displayname and 1.0 cant fetch your profile for that reason. So all federation with your account is broken. Made a PR to fix it.

Its intentional because not every post and comment needs to show that a user is admin or mod. Makes it difficult to participate in normal discussions as everything looks like “official” communication. Also the distinguish feature was barely being used.