mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #1673] NPM not opening port when creating a new stream. #1251
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#1251
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 @FreshImmuc on GitHub (Dec 22, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1673
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
Title
Nginx Proxy Manager Version
latest
To Reproduce
Steps to reproduce the behavior:
Expected behavior
That the port is open
@FreshImmuc commented on GitHub (Dec 22, 2021):
Here I checked if any process is using this port, that I used for the stream in NPM but unfortunately there is none
Here I tested if port 80 is used by NPM (just so you know how it SHOULD look when a port is used):
@chaptergy commented on GitHub (Dec 23, 2021):
Since NPM is a dockerized application, you will also need to expose that port in your docker-compose file, since npm is not able to do that. Then that port will also be accessible from the outside and should work as expected.
@FreshImmuc commented on GitHub (Dec 23, 2021):
Ahhh okay I remembering now. Thank you I just used this a while ago.