[SOLVED]Self hosted docker instance not fetching new posts and comments
[SOLVED]Self hosted docker instance not fetching new posts and comments
Hey all, just wondering if I'm missing something or just have a fundamental misunderstanding of how federation works. I spun up a small docker instance for myself in order to interact with federated lemmy without bogging down the existing servers. I am noticing that although I am subscribed to a lot of communities, some of them don't seem to be updating. I know that my instance will only fetch new posts and comments from the communities I'm subscribed to, but even those are not being updated. Some communities seem to be working, but others just aren't updating. Is there a requirement that I'm not meeting to be able to fetch new data? Appreciate any ideas, thank you!
Edit: the problem was in the instance's language settings. It is not obvious, but you can, and should, select multiple languages in your instance's admin panel (at least Undetermined and your main language). I solved by selecting every language in the admin panel, and then selecting the relevant ones again from the individual user settings.
It should just work. You are able to search for and subscribe to communities on other instances, so it's not the internal networking issue I ran into with federation and smtp.
I'll ask anyway, what do you see in the lemmy logs? Any errors?
sudo docker logs lemmy_lemmy_1I've been monitoring the logs, the only error I've seen go by is the following one from the postgres container:
lemmy-postgres-1 | 2023-06-11 17:37:12.579 UTC [31] ERROR: duplicate key value violates unique constraint "idx_activity_ap_id" lemmy-postgres-1 | 2023-06-11 17:37:12.579 UTC [31] DETAIL: Key (ap_id)=(https://lemmy.world/activities/create/f26c82de-548d-405a-bca3-00775a73411f) already exists. lemmy-postgres-1 | 2023-06-11 17:37:12.579 UTC [31] STATEMENT: INSERT INTO "activity" ("data", "local", "updated", "ap_id", "sensitive") VALUES ($1, $2, DEFAULT, $3, $4) RETURNING "activity"."id", "activity"."data", "activity"."local", "activity"."published", "activity"."updated", "activity"."ap_id", "activity"."sensitive"
Any relevant logs from the lemmy container?
Have you checked the /instances/ url at your instance and those you federate with to ensure they each cross-reference each other?
I have confirmed that we are cross-referencing each other. I've also been monitoring the logs, the only error I've seen go by is the following one from the postgres container:
lemmy-postgres-1 | 2023-06-11 17:37:12.579 UTC [31] ERROR: duplicate key value violates unique constraint "idx_activity_ap_id" lemmy-postgres-1 | 2023-06-11 17:37:12.579 UTC [31] DETAIL: Key (ap_id)=(https://lemmy.world/activities/create/f26c82de-548d-405a-bca3-00775a73411f) already exists. lemmy-postgres-1 | 2023-06-11 17:37:12.579 UTC [31] STATEMENT: INSERT INTO "activity" ("data", "local", "updated", "ap_id", "sensitive") VALUES ($1, $2, DEFAULT, $3, $4) RETURNING "activity"."id", "activity"."data", "activity"."local", "activity"."published", "activity"."updated", "activity"."ap_id", "activity"."sensitive"