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
• your custom DNS provider

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 the domain in a different browser / private window
• try it on my phone over mobile network and not wifi

I recently had the problem that the custom secure DNS I use on Firefox took almost a day to update their cache, while every other provider had my changes in a couple of minutes at most.

Okey, so if you skip the whole DNS and use http://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.

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 last 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.

I think you are conflating desktop Ubuntu with Ubuntu Server. On a server, you absolutly want a stable, long supported LTS version.

I've been hosting on Ubuntu Server for over 10 years now, and at no point were any packages required to keep it up to date and running outdated.

I see your point. But to me, self-hosting just means being responsible for the server and services and not necessarily having my own hardware server at home. And just calling it hosting is too broad a definition for me. And at the end of the day, the guide works just as well for your own hardware or a VM, as it does for a VPS.

Took me an embarrassing amount of time to realize my mistake. I forgot to actually use the npx @11ty/eleventy build command instead of always relying on npx @11ty/eleventy --serve. Now the images are properly linked and transformed / optimized.

I've personally never found the need to do that. If you follow basic security guidelines and keep your server os and the docker service up-to-date, there really isn't any real threat.

Though I have heard of Authelia before and was interested in reading up on SSO, one of these days.

Yeah, took me a while to get the hang with Nunjucks, which I had never heard of or used before. But once I got it all properly set up, it was super simple and easy. I'll definetly write a guide to it too, eventually.