August 28, 20223 yr Hello! I have to tell, that I'm new in Unraid and need your help please, as I wasted almost a week for this task and you are my last hope. I have installed docker and created a container with Nginx Proxy manager. My Unraid server is reachable in LAN via http://nas.local. I would like to make subdomain for each container inside docker to be reachable via name without pointing port number (for example: http://nginx.nas.local opens nginx webGUI (port 7818), http://nextcload.nas.local opens Nextcloud webGUI etc). I have separate DNS server (pihole) as resolver (in my example nas.local = 10.220.0.100 LAN IP and I have added CNAME nginx.nas.local points to nas.local). I have read a lot information about reverse proxy in Nginx but I can't get it work properly. Now both links nas.local and nginx.nas.local opens me unraid webGUI (10.220.0.100:80) that is incorrect. How to point http://nginx.nas.local to 10.220.0.100:7818 (Nginx WebGUI) directly? Sorry in advance if I have duplicated the question, but I searched for a lot, but couldn't find solution yet
August 28, 20223 yr Community Expert This video is a few years old now but might be some help. Be sure to check out other videos on that youtube channel.
August 28, 20223 yr Author 2 minutes ago, trurl said: This video is a few years old now but might be some help. Be sure to check out other videos on that youtube channel. Hello trurl and thanks for your fast response! I have already watched that video, tried to make configuration with "SWAG" but didn't succeed. I don't need SSL and I don't want to register domain as I would like my Unraid and containers to be reachable only in LAN via local subdomains (I use Wireguard on my Mikrotik's core router to connect to the local subnet where I have my Unraid server). Is it possible to use only functionality of Nginx proxying to get everything work? Just to proxy domain name to the each container in my Docker?
November 11, 20241 yr On 8/29/2022 at 12:38 AM, Ripstor said: I have resolved my problem, thanks! How did you solve it..?
November 11, 20241 yr 34 minutes ago, johyphenel said: How did you solve it..? Here's one way to do it (IMO, much better than running NPM in Docker) - just to note, that if you want a real signed certificate, you have to register your domain name and use a site like Cloudflare to keep track of its DNS settings. This allows Let's Encrypt to validate domain ownership when issuing a certificate. If you just want your own self-signed certificates, you can use whatever domain name you'd like. Just make sure the TLD is a legitimate one so your browser will look up the address and also make sure not to use ".local" as that's reserved for mdns and will never work properly with regular DNS. Edited November 11, 20241 yr by Espressomatic
February 26, 20251 yr On 8/29/2022 at 2:38 AM, Ripstor said: I have resolved my problem, thanks! can you share how you solved the issue please?
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.