[GH-ISSUE #3109] Ports with new streams won't open #2108

Closed
opened 2026-02-26 07:34:03 +03:00 by kerem · 3 comments
Owner

Originally created by @mrbcast on GitHub (Aug 10, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3109

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes
  • Are you sure you're not using someone else's docker image?
    • Yes
  • Have you searched for similar issues (both open and closed)?
    • Yes

Describe the bug

Right after initial installation I added several streams for port forwarding to services in my setup. I had no trouble til about a month ago. Now when I add a new stream (and the accompanying posting of the ports to the docker-compose.yml file) it will record it and it shows good, but when I try to access the port it is closed. I have checked firewalls, ufw, iptables, hosting provider and everything else I can think of and no joy. I can ping the port internally but it won't connect to the ip of the service nor will it allow it to go from outside wan to inside ip4 address. Netstat shows it is listening on the ports not open. Not sure where to go from here. Any advice or suggestions would be appreciated.

Nginx Proxy Manager Version

v2.9.20 © 2022 jc21.com. Theme by Tabler

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'streams'
  2. Click on 'new stream, add a new stream'
  3. Scroll down to '....'
  4. See error No joy on opening port through to service. Following same steps since installation. Worked til about a month ago.

Expected behavior

Screenshots

Operating System

Ubuntu 20.04 server on proxmox container

Additional context

Originally created by @mrbcast on GitHub (Aug 10, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3109 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** <!-- A clear and concise description of what the bug is. --> Right after initial installation I added several streams for port forwarding to services in my setup. I had no trouble til about a month ago. Now when I add a new stream (and the accompanying posting of the ports to the docker-compose.yml file) it will record it and it shows good, but when I try to access the port it is closed. I have checked firewalls, ufw, iptables, hosting provider and everything else I can think of and no joy. I can ping the port internally but it won't connect to the ip of the service nor will it allow it to go from outside wan to inside ip4 address. Netstat shows it is listening on the ports not open. Not sure where to go from here. Any advice or suggestions would be appreciated. **Nginx Proxy Manager Version** <!-- What version of Nginx Proxy Manager is reported on the login page? --> v2.9.20 © 2022 [jc21.com](https://jc21.com/?utm_source=nginx-proxy-manager). Theme by [Tabler](https://tabler.github.io/?utm_source=nginx-proxy-manager) **To Reproduce** Steps to reproduce the behavior: 1. Go to 'streams' 2. Click on 'new stream, add a new stream' 3. Scroll down to '....' 4. See error No joy on opening port through to service. Following same steps since installation. Worked til about a month ago. **Expected behavior** <!-- A clear and concise description of what you expected to happen. --> **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> **Operating System** <!-- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. --> Ubuntu 20.04 server on proxmox container **Additional context** <!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. -->
kerem 2026-02-26 07:34:03 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

@logclinker commented on GitHub (Aug 19, 2023):

I have installed a fresh copy of proxy manager, created some streams, my very first created stream worked fine, anything after, didn't work at all.

I have then removed all my streams, however, the very first stream was still working, even after deleting all of them.

It seems that there is a bug, and at some point something hangs and no changes to streams give any effect.

<!-- gh-comment-id:1685078234 --> @logclinker commented on GitHub (Aug 19, 2023): I have installed a fresh copy of proxy manager, created some streams, my very first created stream worked fine, anything after, didn't work at all. I have then removed all my streams, however, the very first stream was still working, even after deleting all of them. It seems that there is a bug, and at some point something hangs and no changes to streams give any effect.
Author
Owner

@github-actions[bot] commented on GitHub (Apr 8, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:2041724671 --> @github-actions[bot] commented on GitHub (Apr 8, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Jun 6, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2947820158 --> @github-actions[bot] commented on GitHub (Jun 6, 2025): Issue was closed due to inactivity.
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#2108
No description provided.