One last thing. I assume you checked if your DNS changes got propagated? I tend to use DNS Checker. And even if the changes are propagated, it can sometimes still not work because of DNS cache in

• your browser
• your pc
• your router

So assuming that you checked the DNS propagation and it was propagated enough, I’d also

• clean all DNS caches from browser, pc and router
• try different, large DNS provider (Google, Cloudflare, etc.)
• try it on my phone over mobile network and not wifi

Okey, so if you skip the whole DNS and use PUBLICIP:PORT for any of your docker services, does your browser reach them?

You said you have Caddy on bare metal Ubuntu and your services in CasaOS. Sadly I’ve never used that, but is that a VM on your Ubuntu Server and inside that run your docker containers? If so, maybe that’s what’s stopping Caddy from reaching your containers?! Just guessing tbh.

You need to point your sub-domain in the Caddyfile to your designated local port. So just add an entry like this to your Caddyfile

sub.yourdomain.com { reverse_proxy XXX.XXX.XXX.XXX:PORT { header_up X-Real-IP {remote_host} } encode zstd gzip }``` Replace XXX with your public IP and PORT with the local port in your docker container / compose.

Wen intressiert es denn, wenn ich mein Haus abfackel oder mein Kind vergiftet, wenn ich 5€ spare \s

Ich werde nie Menschen verstehen, die sinnlosen Müll bei solchen Shops bestellen.

I can confirm this behavior on my machine. And after a (far too) long internet search, I think it might be connected to this Muffin bug report from 2023.

I checked every single setting window and tab and scoured the gsettings with dconf editor and as far as I can tell, there is no way to disable this strange window snapping behavior when dragging a window with SHIFT held down.

Of course, the fact that people keep confusing snapping with tiling did not help in my search.

Thanks! I am happy, if people find it helpful.

The amount of baseless Ubuntu Server hate in this sub is pretty sad. I’ve used Ubuntu Server, without any problems, for more than a decade. And at no point where there any significant changes to the way things are done. So I really think your comment about articles becoming useless has no basis in reality.

As for using your own hardware. Nothing in this guide necessarily requires a VPS. And you seem to completely ignore the upkeep and electricity costs of having your own hardware at home.

Not to mention the convenience of a public IP, which is something not every ISP around the world offers. And yes, you can use a dynamic DNS provider to get around that, but then you publish your private IP onto the entire internet.

The guide was focused on being as simple and convenient as possible, with the target audience being absolute beginners to self-hosting. If it doesn’t speak to you, feel free to write your own.

Thank you for your very helpful and friendly criticism. I temporarily used Netlify, because I haven’t gotten around to program a proper deploy script for my Forgejo git repo.

You mean from one LTS to the next? It’s been a while, but as far as I remember, it worked fine on my first server (22.04 to 24.04).

And even if something doesn’t work, I can have all my stuff spun up on a new server in less than an hour. But that, of course, depends on the amount of data you host.