Hi All,

 

I have held off for weeks and weeks before posting this and have tried everything I can, Hopefully someone here with a bit more experience can tell me what I have set wrong. I have a couple of containers that I want to be able to access, The main one being Immich. I have Nginx installed and configured with the default settings (see Pic attached)

 

 

I have Forwarded ports 80 and 443 to 8080 and 4443 probing the ports on my external IP shows that they are open so Im guessing that side is good. Once I turn off the port forwarding it shows as closed.

 

All my cloudflare stuff is done, DNS records are all configured. Immich.thisismydomain.com (not my domain by the way) sends traffic to my external IP. I can ping my domain and get a reply back from my IP. I can turn on proxies in cloudflare and then pinging my domain gets a reply back from cloudflare servers.  Everything so far is looking good.

 

 

In NGINX when I create the certificate and test server reachability I get Your server is reachable and creating certificates should be possible.

 

Everything seems to be looking like it should work but when I try to connect I get bad gateway error (see attached)

 

If anyone knows what I have missed or done wrong I would really appreciate the help.

 

 

  

So if that is your Nginx template then 80 external port needs to be forwarded to port 1880 and 443 external port to 18443.

12 hours ago, Gragorg said:

So if that is your Nginx template then 80 external port needs to be forwarded to port 1880 and 443 external port to 18443.

So I tried that but when I probed the ports on my external IP they where closed. Why does the template state that the container port is 8080 and 4443? Probing my external IP with them ports forwarded to my Nginx IP shows them as been open.

 

I’ll give it another shot. Appreciate your reply 

52 minutes ago, Smokie said:

Why does the template state that the container port is 8080 and 4443?

Because that is how whoever created the container and its associated template have it configured to be.    Note that it quite normal for the port at the Unraid level to be different (which is the whole idea of port mapping) to the internal port seen by the container.

I have forwarded ports 1880 and 18443 to my NGINX server and now when I probe my external IP on them two ports they are closed.

Doesnt make sense. As soon as I switch it back to forwarding ports 8080 and 4443 they replay as being open.

 

What Am I missing??

It should not matter where the internal port points to.  If you want to use ports 8080 and 4443 on your NPM docker than you need to change them to that in the docker template.  Just check to make sure you are not using them elsewhere.

Edited September 26, 20241 yr by Gragorg

Got it resolved. Just for anytime in the future that has a similar issue. What it was is that I didn’t create a custom docker network when I first created my unraid server. I had most of my apps running as standard on the same IP as the server 192.168.1.132 all using different ports etc but my NGINX setup I had running with a static IP of 192.168.1.201 after I created a custom docker network and moved everything over it’s working as expected.

 

i never knew they could not communicate with each other. Lesson learned and thanks for helping out.