[GH-ISSUE #1536] Https-Port isn´t reachable #1167

Closed
opened 2026-02-26 06:36:01 +03:00 by kerem · 3 comments
Owner

Originally created by @thannerfabian on GitHub (Oct 29, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1536

I ran my docker container on a complete new ubuntu server with the command:
sudo docker run -d --name=nginx-proxy-manager -p 81:8181 -p 80:8080 -p 443:4443 -v /docker/appdata/nginx-proxy-manager:/config:rw jlesage/nginx-proxy-manager

I can reach Port 80 and 81 but when i call the https-Port i get the error ERR_CONNECTION_REFUSED.
I also tried another browser, disabling all firewall, and a complete reinstallation.

What can the problem be.

Thank you very much in advance.

Originally created by @thannerfabian on GitHub (Oct 29, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1536 I ran my docker container on a complete new ubuntu server with the command: sudo docker run -d --name=nginx-proxy-manager -p 81:8181 -p 80:8080 -p 443:4443 -v /docker/appdata/nginx-proxy-manager:/config:rw jlesage/nginx-proxy-manager I can reach Port 80 and 81 but when i call the https-Port i get the error ERR_CONNECTION_REFUSED. I also tried another browser, disabling all firewall, and a complete reinstallation. What can the problem be. Thank you very much in advance.
kerem 2026-02-26 06:36:01 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@chaptergy commented on GitHub (Oct 29, 2021):

You have the ports the wrong way round. Docker expects the following syntax when exposing ports: <hostPort>:<containerPort>. So you are acutally exposing the containers port 4443 on your host machine on port 443. Not sire why you can reach port 80 and 81 but it should not be possible.

<!-- gh-comment-id:954797750 --> @chaptergy commented on GitHub (Oct 29, 2021): You have the ports the wrong way round. Docker expects the following syntax when exposing ports: `<hostPort>:<containerPort>`. So you are acutally exposing the containers port 4443 on your host machine on port 443. Not sire why you can reach port 80 and 81 but it should not be possible.
Author
Owner

@thannerfabian commented on GitHub (Oct 29, 2021):

If i have to expose it like : , I think it´s correct. I use the port 443 on the host to route to 4443 on the container. Is this wrong?

<!-- gh-comment-id:954820598 --> @thannerfabian commented on GitHub (Oct 29, 2021): If i have to expose it like <hostPort>:<containerPort> , I think it´s correct. I use the port 443 on the host to route to 4443 on the container. Is this wrong?
Author
Owner

@chaptergy commented on GitHub (Oct 29, 2021):

You are using the jlesage image, with the official image it shouldn't work at all as it uses port 80, 81 and 441 inside the container. This issue tracker is only for the official image, please head over there with this issue.

<!-- gh-comment-id:954835654 --> @chaptergy commented on GitHub (Oct 29, 2021): You are using the jlesage image, with the official image it shouldn't work at all as it uses port 80, 81 and 441 inside the container. This issue tracker is only for the official image, please head [over there](https://github.com/jlesage/docker-nginx-proxy-manager) with this issue.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#1167
No description provided.