Proxy Host Not Working

[capriciousduck]

Hello. Proxy hosts are not working. I pointed my proxy domain to my server IP in my DNS records, but still not working.

In the container logs I see this:

Duplicate relation "access_list" in a relation expression. You should use "a.[b, c]" instead of "[a.b, a.c]". This will cause an error in objection 2.0

[capriciousduck]

If I use port 80 instead of 8080 on host and I point my domain to the IP of server Nginx Proxy Manager is running on, then it WORKS, else it doesn't.

How can I point an A record to 8080?

[jlesage]

I'm not sure I fully understand your issue, but Nginx Proxy Manager needs to be reachable from the Internet on port 80 and 443. You usually need to configure port forwarding on your router.

Can you share the configuration (your docker run command) of the container ?

[capriciousduck]

Here's my docker run command:

docker run -d --restart unless-stopped \ --name=nginx-proxy-manager \ -p 8181:8181 \ -p 8080:8080 \ -p 4443:4443 \ -e USER_ID=0 \ -e GROUP_ID=0 \ -e KEEP_APP_RUNNING=1 \ -v nginx-proxy-manager_config:/config:rw \ jlesage/nginx-proxy-manager

[capriciousduck]

Do you mean I "have" to change host port 8080 to 80 and 4443 to 443?

[jlesage]

According to your configuration, you need to configure port forwarding on your router:

• Port 80 should be redirected to the IP of your host on port 8080.
• Port 443 should be redirected to the IP of your host on port 4443.

[capriciousduck]

Well, I am not doing this on my local machine. I am running this on my server located in Finland. Now do I have to do anything on my server to use 8080 and 4443 instead of 80 and 443?

[jlesage]

You mean how to make Nginx Proxy Manager reachable over the Internet via port 4443 and 8080?

[capriciousduck]

Exactly!

[capriciousduck]

I mean I can point my domain to port 80 but not 8080 and that is why I'm having issues (which is obvious). Since I am already using port 80 for another purpose, I need to use some other port for Nginx Proxy Manager.

[jlesage]

Unfortunately this won't work. You won't be able to generate certificates for sure and if I remember correctly, access to your configured proxy hosts won't work as expected, because you have to manually set the port on the URL.

For example, instead of accessing your site via http://example.com, you will have to access it via http://example.com:8080.

[jlesage]

But let's give it a try, to see if using something like http://example.com:8080 is working.

[capriciousduck]

Is it not possible to forward traffic from port 80 to 8080 on my server?

On Mon, Nov 1, 2021 at 6:09 PM Jocelyn Le Sage @.***> wrote:

But let's give it a try, to see if using something like http://example.com:8080 is working.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jlesage/docker-nginx-proxy-manager/issues/215#issuecomment-956199280, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2VBQ62CIUBL3KXRIGJ6D3UJ2DBXANCNFSM5HA33IWA .

[jlesage]

But you said that you already have another application on your server that uses port 80 ?