Demigodrick

Here’s a handy site to check your federation status: https://phiresky.github.io/lemmy-federation-state/site?domain=social.packetloss.gg

It looks like all the sites are lagging, which can sometimes mean there is an issue. What’s the specs of the server? Can you try restarting it and seeing if that helps?

There are issues for servers hosted in places like Australia because of the latency in communicating with .world due to how big it is and how much data it sends because of this.

I’d say Nginx Proxy Manager is the easiest reverse proxy I’ve used.

There is already an update. 0.18.2-rc1

You can apply it now.

I’m on hetzner who also block port 25. I finally worked out what I needed to change to get it to work. As your using the ansible playbook, all you need to change the lines inside the .hjson file to match those of an external mail service. I used Mailersend (3000 free emails once you’re verified). If you’re using port 587 use starttls as your encryption.

Backup for redundancy. Keep the wife happy when I take one down for maintenance etc.

• Vaultwarden
• 2 pi holes
• the suite of arrrs + nzbget
• jellyfin
• ombi
• OMV for a SMB share
• Nextcloud
• homer as a dashboard
• homeassistsnt
• uptime kuma
• koillection

I did also have a wordpress site but that was too much hassle so the container is stopped at the moment.

All on docker (except OMV, and home assistsnt on its own pi4) and using portainer for sanity.

Internal SSL using a domain and nginx proxy manager.

This has definitely been a problem with communities being created on the bigger instances and not utilising smaller instances. Happy for someone to say I’m wrong etc, but I think there would be merit in capping instances to x number of users or communities, to force the user base to spread out.

Also, the way signups work, (ie you find a community you like then click sign up but that signs you up to that instance), further exacerbates the issue and the confusion around how federation works. The sign up links on each instance should lead either to a page with an instance finder, or to a random instance that matches the profile of, and is already federated with, the instance you were on. Otherwise the larger instances have a monopoly and are just going to lead to a bad user experience when they can’t cope with the traffic.

It’s a self defeating prophecy if users only want to sign up to the instances with the big communities, because then everyone is going to keep creating communities there and nobody is going to want to join a smaller instance.

I might be talking nonsense and am happy to be told why that is all wrong :)