Actually, one thing I want to do is switch from services being on a subdomain to services being on a path.

immich.myserver.com -> myserver.com/immich jellyfin.myserver.com -> myserver.com/jellyfin

I’m getting tired of having to update DNS records every time I want to add a new service.

I guess the tricky part will be making sure the services support this kind of routing…

Why are you having to update your DNS records when you add a new service? Just set up a wildcard A record to send *.myserver.com to the reverse proxy and you never have to touch it again. If your DNS doesn’t let you set wildcard A records, then switch to a better DNS.

Not OP but a lot of people probably use pi-hole which doesn’t support wildcards for some inane reason

That’s my case. I send every new subdomain to my nginx IP on pi-hole and then use nginx as a reverse proxy

That was my exact setup as well until I switched to a different router which supported both custom DNS entries and blocklists, thereby making the pi-hole redundant

I run opnsense, so I need to dump pi-hole. But I don’t have the energy right now to do that.

Pi-Hole was pretty straightforward at the time and I did not look back since then. Annoying, but easy.