February 3, 20242 yr Hi everyone! I've been pulling my hair the last few hours trying to set this up. It should be pretty simple and I have 80% of it working, so I'll detail exactly what I'm doing. Goals: Expose specific dockers for me to manage outside the home Expose Plex + Overseer with custom DNS domains for easier sharing with friends and family What I've done so far: Changed unRAID's HTTP and HTTPS port as to not expose the webgui. Installed NGINX Proxy Manager with the following settings: Setup duckdns with my wan ip pointing to, let's call is. myserver.duckdns.org Bought a domain on Cloudflare and set it up as such: Forwarded all necessary ports on my AX88U router. (I manually changed in Plex's Settings the external port to be 14008 hence the mapping below) Setup NPM (example of Sonarr) Attempt to connect to sonarr results in: But, if I attempt to connect to myserver.duckdns.org:8989 it works perfectly. As well as if I connect to my wanip:8989. So the issue is definitely in the latter stage with NGINX PM / Cloudflare. BUT, if I go to the plex one: So, for some reason the plex dns leads to the "default page" but anything else just errors out. Any idea on where to go from here? Thanks!
February 3, 20242 yr I wouldn't recommend changing 80 and 443 for unraid. Change the ports in the NPM docker instead and be sure to forward the rights ones. I would get rid of duck dns if you bought a domain and use Cloudflare-DDNS by selfhosters. Use Spaceinvader video here and skip ahead to 9:20 in the video. You can setup you DNS challenge as cloudflare in NPM. Also do not forward a port for Overseerr or Sonar that is the whole point of NPM to direct traffic to those containers. The myserver.duckdns.org:8989 works because you forwarded the port to the gui. This is not secure. Edited February 3, 20242 yr by Gragorg type
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.