

You have a lot going on there all at once that could be contributing to the whole thing failing.
If it were me, I would try to get caddy working independently of everything else first, since it was your original problem, then layer in the other containers one by one in case you’ve got configuration problems in them too.
Caddy by itself is super easy to verify with something like a browse directive pointed at an empty directory.
Then add your tailscale container and configs, and check that you can still access the browse page from caddy.
Then add your Jellyfin container and adjust the Caddyfile to proxy to it.



Incompatible with every website in which browser? It works for years in both Chrome and Firefox. Is this a meme for Safari users only?
The fact that Google invented this format is the most annoying thing about webp, but the complaints in this image haven’t been an issue for a very long time in my experience.