Skip to content
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: #5464

Closed
ThorsHammer-GeekRoomTech opened this issue Feb 28, 2025 · 5 comments
Closed

Question: #5464

ThorsHammer-GeekRoomTech opened this issue Feb 28, 2025 · 5 comments

Comments

@ThorsHammer-GeekRoomTech
Copy link

ThorsHammer-GeekRoomTech commented Feb 28, 2025

Question

I am struggling with getting federation to work properly on my new instance. It's been up for around 48 hours and it seems that after an initial search for a community and then a subscribe to the community, I do not get any updates from new posts from those instances... to my own instance.

Additionally, when I commented on a post, I saw 0 comments on that post when viewing from my instance. When I checked the remote instance, I saw there were multiple and more made after my initial comment on that post.

I believe that federation is not working, but I do not know what I am doing wrong to cause it to not federate properly.
When I check the logs of the lemmy backend, I can see that it is showing lemmy_federate::stats: 62 others up to date. 0 instances behind.
This shows even within a few minutes of having attempted a subscribe or attempting to make a comment or post.

I have gone through the federation troubleshooting guide and I'm getting json data back from the CURL commands that it references, and everything seems to be operational, but it's like my instance is stuck.

geekroomtech-lemmy-1 docker container logs.txt

nginx_internal.conf.txt

geekroom.tech.docker-compose.yaml.txt

geekroom.tech_nginx.site.conf.txt

So where am I going wrong? What have I misconfigured incorrectly?

@Nothing4You
Copy link
Collaborator

your instance seems to be confused which domain it's using. your first comment was tied to prd-pub-pod11.geekroom.tech, not geekroom.tech, which doesn't exist in dns. your latest comment is tied to www.geekroom.tech.

on top of that you have just exposed your PICTRS__SERVER__API_KEY in the compose file, you should rotate that key.

@ThorsHammer-GeekRoomTech
Copy link
Author

Originally I was going to use prd-pub-pod11 but when I realized that's where it was going to point people to in emails, I knew that was going to be an issue. So I updated it to GeekRoom.Tech directly, but then I get 550 Bad HELO errors and doesn't allow me to send emails... thus why it is now www.geekroom.tech for the mail.

Any documentation on rotating passwords?

@dessalines
Copy link
Member

Please read the docs it shows you when opening an issue.

https://lemmy.ml/c/lemmy_support

@dessalines dessalines closed this as not planned Won't fix, can't repro, duplicate, stale Feb 28, 2025
@ThorsHammer-GeekRoomTech
Copy link
Author

I updated the pictrs api key and it seems to be working just fine.
However, I'm still not federating properly, not sure why this get closed.

@dessalines
Copy link
Member

This isn't the support forum.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants