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.
Well at least now you can actually see the damn black ports on the silver chassis. The M2 Mac Mini has the black ports on the black backside and it’s such a pain in the ass trying to find the USB C ports when I have to connect something.
But yeah, putting the power button on the bottom is peak Apple stupidity.
Nice alternative to Figma. Gave it a try a couple of months ago but the snapping was super unreliable and exporting to PDF screwed up the quality of any pictures to an unusable point. Might have to give it another try and see if some of my problems have been fixed.
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
So assuming that you checked the DNS propagation and it was propagated enough, I’d also
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.