In this case. Make sure you have cash at hand at least for the next couple of days until the storm passes.

Is it just me or the link returns a 404?

Honestly I would replace Ubuntu with an actual operating system designed for servers.

Self-hosted Bitwarden.

Trillium

You’re most welcome.

The truth is that his army had been doing a really great job over the past year so his high hopes are clearly motivated. /s

Well it is a different type of mail system. I use it for catch all. I have like 200 domain names for various projects or registered to sell and I want to catch all emails sent to those domains without setting them up in mailcow. With Anonaddy I verify their DNS records and that’s it. I can capture all emails sent to them and forward to a specific address. Also, I can use whatever email address I want with whatever domain I want to subscribe to services and keep track of who sells my email for instance. They also have a Chrome extension that you can use to generate emails, but imho that is overkill. Then if you see that one email gets too much spam you can simply delete that forwarder and it gets rejected in the future.

I work with VMs mostly, so I go for Veeam B&R. The free tier allows you to backup 10 VMs or machines.

Yes, with mailcow.email and a catchall and random email system with Anonaddy.

Well thanks to the soon to be dead /r/selfhosted on reddit I started selfhosting few years ago and now approximately 90% of my stuff is selfhosted:

• Gitlab
• RocketChat
• VS Code
• Anonaddy
• Etherpad
• Min.io
• Archivebox
• FreshRSS
• FileStash
• Matomo
• InfiniteWP
• piHole

as daily drivers and several others that I use from time to time.

Well if you are using docker-compose you could probably get rid of the nginx container and only deploy the other four: lemmy, lemmy-ui, pictrs, postgres. You would then use the nginx.conf stuff you have in place for the docker container of nginx to proxy to lemmy-ui and lemmy on ports 1234 and 8536. Or if you plan to keep using the docker container for nginx then you can change the listening port in the nginx.conf of the container:

listen 80;

to something different like

listen 1080;

Also in the docker-compose.yml you would update the nginx ports to 1080:1080.

Hope this answers your question.

I used docker-compose version and had to work around a couple of bugs like needing to redundantly install Nginx and Let’s Encrypt for it to work properly with SSL and also having to add the lemmy container to the internet facing network due to the DNS not working on it and subsequently loosing federation capability. Overall a bit of a struggle, but this is common with FOSS.