mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #1536] Https-Port isn´t reachable #1167
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1167
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
@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.@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?
@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.