Currently my Docker apps (plex, rr's, sabnzbd, etc.) all run in my docker, but I use NGix Proxy Manager to resolve them with an easy to remember domain, i.e plex.domain.com, through a combindation of NPM, Cloudflare and DuckDNS.

 

Pro's to this set-up are;

• Easy to remember domains (family friendly)
• Easy to access outside the home
• SSL certificates, so no annoying browser popup's.
• No having to remember ports for apps, such as plex's 32400.

 

The drawbacks to this I see are;

• They are open to the world.  Anyone could stumble across them and use them to access my internal network.
• If my internet goes down, I lose access to locally hosted apps.
• Doesn't work if you need to access multiple ports, such as Unifi Controller.  I currently host that using vultr.com at unifi.mydomain.com, which adds up when it's $8.50 per month.

 

I've been trying to work out how to move the subdomains to internal domains, i.e. plex.local, sonarr.local, unifi.local, etc. which I can do in PiHole as local DNS records, however I then lose the SSL certifiates and also the ability to mask the ports, i.e. for plex I now need plex.local:32400.

 

How can I re-introduce the SSL certificates on each docker container (or .local in general) and also mask the ports, so that port 80 effectively forwards to the docker containers webGUI port?

 

I'm sure there's away, I just can't find the right tools to do it.

 

Thanks!

 

2 minutes ago, skot4th said:

They are open to the world. 

Just set access rules in NPM to only accept the local subnet.

 

2 minutes ago, skot4th said:

Anyone could stumble across them and use them to access my internal network.

Not really, that'd only be possible if you willlingly expose a service that provides this access with poor security, or one of your services has an improbable critical vulnerability.

 

3 minutes ago, skot4th said:

If my internet goes down, I lose access to locally hosted apps.

Set up local dns so your domains can resolve locally.

2 hours ago, Kilrah said:

Just set access rules in NPM to only accept the local subnet.

 

Not really, that'd only be possible if you willlingly expose a service that provides this access with poor security, or one of your services has an improbable critical vulnerability.

 

Set up local dns so your domains can resolve locally.

Thanks, so if I set plex.mydomain.com in the local DNS, rather than plex.local then that will still work?

 

The only issue I have is with Unifi.  It seems that if I set unifi in NPM then I can access the webgui port (normally 8443) at the unifi.mydomain.com address, however the other ports aren't accessible which are needed by the access points, etc.  Any idea how to get around this?

That should have nothing to do with the RP. It's set to Host networking?