My instance posts are accessible from other instances but comments from other instances aren't accessible from my instance (jlai.lu)

submitted 1 day ago by KaKi87@jlai.lu to c/lemmy_support@lemmy.ml

11 comments fedilink hide all child comments

Here's the link to the original instance : https://blog.kaki87.net/c/kaki_blog?dataType=Post&sort=New

Here's an example comment from another instance : https://0d.gs/comment/5903730

Here's the same comment on yet another instance : https://jlai.lu/post/21115531/15881483

But from the original instance, the comment doesn't show up.

What to do ?

Thanks

you are viewing a single comment's thread
view the rest of the comments

[-] asudox@lemmy.asudox.dev 1 points 1 day ago* (last edited 1 day ago)

~~Check this out: https://join-lemmy.org/docs/administration/troubleshooting.html#you-dont-receive-actions-reliably~~

~~(However, afaik your instance must receive activity so that said activity can be federated to other instances. That's why you can comment on dead instance comms, but they never will be seen on other instances. Take lemm.ee for example.)~~

~~Also, as davel said, the instances page seems to be broken, and that doesn't seem to be a frontend issue as not even lemmy federation state checker is able to query it, so either something is wrong at the backend or your reverse proxy config.~~

~~Check the logs and config.~~

edit: wrong, ignore.

[-] KaKi87@jlai.lu 2 points 1 day ago

Check the logs and config.

What should I be looking for ?

[-] asudox@lemmy.asudox.dev 2 points 1 day ago* (last edited 1 day ago)

Sorry, forget my previous comment. It seems to be a bad design choice in the frontend. The backend is working fine, probably.

Your instance is not federating with other instances, and this definitely is because someone manually turned off federation or changed the federation mode (otherwise your community and its posts wouldn't have appeared on other instances).

The comment on the jlai.lu instance seems to be there because someone manually fetched it. That would explain why "your instance did not receive the activity but federated it over to other instances".

Go to the admin page in the lemmy UI and turn on federation. If you selected "Allowlist" or "Blacklist", select "Open" as the federation mode.

https://join-lemmy.org/docs/administration/federation_getting_started.html

Then comment or like posts from other instances, ideally a popular community so your instance starts federating with lots of instances faster.

Though I think that's what happening, this wouldn't explain why 0d.gs shows that your instance successfully keeps receiving activities from it. I wonder if there is no check being done for that.

[-] KaKi87@jlai.lu 1 points 1 day ago

Go to the admin page in the lemmy UI and turn on federation. If you selected "Allowlist" or "Blacklist", select "Open" as the federation mode.

All I see is a "Federation enabled" checkbox that is checked, an "allowed instances" list that is empty, a "blocked instances" list that is empty as well, and a "federation debug mode" checkbox that is unchecked.

I don't see "allowlist", "blocklist" or "federation mode".

Thanks

[-] asudox@lemmy.asudox.dev 1 points 20 hours ago* (last edited 20 hours ago)

To double check, you are accessing the Lemmy admin page through the official Lemmy UI, correct?

Also do you mind sharing (if there are any) error logs of the Lemmy backend?

Btw you might want to close the registrations. They are open right now.

[-] KaKi87@jlai.lu 1 points 16 hours ago* (last edited 16 hours ago)

you are accessing the Lemmy admin page through the official Lemmy UI, correct?

Correct.

do you mind sharing (if there are any) error logs of the Lemmy backend?

I've got no "error" lines, but outside of "trace", "debug" and "info", I have the following "warn" line :

WARN Error encountered while processing the incoming HTTP request: pan_builder: InboxTimeout: InboxTimeout
   0: lemmy_server::root_span_builder::HTTP request
           with http.method=POST http.scheme="https" http.host=blog.kaki87.net http.target=/inbox otel.kind="server" d432-40fa-a865-6690f61e11dc http.status_code=400 otel.status_code="OK"
             at src/root_span_builder.rs:16

Btw you might want to close the registrations. They are open right now.

Indeed, which is weird, because I'm sure I closed them when I first created the instance. Are settings lost during upgrades ?

load more comments (1 replies)

this post was submitted on 29 Jul 2025

6 points (100.0% liked)

Lemmy Support

4942 readers

5 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 6 years ago

MODERATORS

dessalines@lemmy.ml