Writing out the current problem I'm trying to solve and how I think I'll solve it:
At this point the server is running Proxmox and I've settled on using a CasaOS LXC container to run most apps. This means installing most things is one-click. Everything gets set up on its own port, so there's no conflicts. I have dynamic DNS set up. But there's 2 problems:
So I think what I will need to do is two levels of nginx reverse proxies:
I've done one layer of reverse proxying before, and I previously had a reverse proxy inside my network which then routed to an nginx ingress on an internal Kubernetes cluster, which routed to backend services in that cluster. Theoretically, what I want to do should work, I just haven't done it this specific way before.
Hoping I can give this a shot today and have it all working. One of the big benefits of this is that I'll have TLS on everything, too, which is a requirement in this day and age!
At this point the server is running Proxmox and I've settled on using a CasaOS LXC container to run most apps. This means installing most things is one-click. Everything gets set up on its own port, so there's no conflicts. I have dynamic DNS set up. But there's 2 problems:
- I want to be able to call the dynamic DNS name from inside my network; due to my network configuration, this is apparently not possible and can't easily be changed.
- I don't want to have to put everything on different ports. I'm just not gonna remember that.
So I think what I will need to do is two levels of nginx reverse proxies:
- Level 1: set up a reverse proxy on one of my existing public servers. There will be a list of hostnames. Each hostname will be for a different service. So, I'll have to set it up in DNS and in the reverse proxy config, but all it will really do is forward the request to my dynamic DNS host, passing along the original hostname in the header so the next layer will know what to do.
- Level 2: I'll run nginx proxy manager on my server. All requests that hit my public server hostname will be proxied to my router, which will port forward to my server's reverse proxy, which will use the provided hostname from level 1 to figure out which backend service to hit.
I've done one layer of reverse proxying before, and I previously had a reverse proxy inside my network which then routed to an nginx ingress on an internal Kubernetes cluster, which routed to backend services in that cluster. Theoretically, what I want to do should work, I just haven't done it this specific way before.
Hoping I can give this a shot today and have it all working. One of the big benefits of this is that I'll have TLS on everything, too, which is a requirement in this day and age!
the horrors persist, but so do we
(aka large mozz)
(aka large mozz)