I’m sure I’m massively overlooking something, but wondered if someone could help me out, please?
I’m trying to switch from Traefik to Nginx Proxy Manager on my Synology NAS, and I’ve opted to run NPM via a bridge network and a macvlan, so as to not have to mess around with ports 80 and 443 on the NAS (usually reserved for Synology services).
I’ve got the following:
Bridge network (npm_bridge):
Subnet = 192.168.10.0/24
IP range = 192.168.10.2/32
Gateway of 192.168.10.1.
Macvlan network (npm_network):
Subnet = 192.168.1.0/24 (same as my LAN)
IP range = 192.168.1.216/32
Gateway = 192.168.1.1 (same as my LAN).
NPM is connected to these two networks, and I have a MariaDB container connected to the host - everything works great with NPM and MariaDB - no issues.
However, I have a third network, medianet:
Subnet = 192.168.96.0/24
Gateway = 192.168.96.1.
Connected to that network I have a Gluetun container (via docker-compose).
I then have multiple other containers that run through the Gluetun container (several “arrs” and Portainer) using network_mode: service:gluetun.
What I used to have via Traefik was a local hostname I created (let’s say, nas.local for posting’s sake) and I could simply create labels in my docker-compose for each service to assign ports. I could then access all of these containers via nas.local/portainer, nas.local/sonarr, etc. and they would be accessible via the VPN container.
However, I’m completely stuck on how to do this via NPM. I’ve tried all kinds of combinations via the Proxy Host configuration, but I don’t know how to set it up.
Do I need an overarching nas.local entry as the top level? If so, what hostname/IP and port combination do I use?
Do I think setup Custom Locations behind it, one for each service, i.e. Portainer? If so, what is the hostname/IP and port for this?
Or do I create a new Proxy Host per entry, i.e. portainer.nas.local?
Do I even need to have Portainer behind the VPN as well, or do I add that direct to the medianet network, and then somehow link NPM to the medianet network as well?
I’m really at a loss, and as it stands all my containers are offline at the moment because I can’t figure out how to connect them (except Homebridge and MariaDB - they’re both up as they’re connected to the host network).
Yeah choose something not reserved. I was gonna use .local too untill I read it was used for mDNS. So I went with .home for all my local stuff (using piHole as the DNS server)
Thanks. Yeah, .local was just an example for the sake of posting something on here. In reality, I would be using ds1618plus.home. But good to know .local is reserved!
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
In case you actually have a DNS server serving the .local TLD, don’t, it’s reserved for mDNS
Yeah choose something not reserved. I was gonna use .local too untill I read it was used for mDNS. So I went with .home for all my local stuff (using piHole as the DNS server)
Thanks. Yeah, .local was just an example for the sake of posting something on here. In reality, I would be using ds1618plus.home. But good to know .local is reserved!