[GH-ISSUE #994] Stream not listening on configured port #834

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

Originally created by @zaclively on GitHub (Apr 1, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/994

Hello,

I am configuring a Stream in the UI and it is not working.

image

When I attempt to connect to the application directly it works, however when my destination in NGINX, it does not work.

I also am not seeing a listening port for the configured stream as well:

systemd-r 801 systemd-resolve 13u IPv4 16338 0t0 TCP 127.0.0.53:53 (LISTEN) container 1053 root 8u IPv4 21412 0t0 TCP 127.0.0.1:44867 (LISTEN) sshd 1316 root 3u IPv4 21345 0t0 TCP *:22 (LISTEN) sshd 1316 root 4u IPv6 21347 0t0 TCP *:22 (LISTEN) docker-pr 2079 root 4u IPv6 25483 0t0 TCP *:443 (LISTEN) docker-pr 2092 root 4u IPv6 25510 0t0 TCP *:81 (LISTEN) docker-pr 2104 root 4u IPv6 25535 0t0 TCP *:80 (LISTEN)

Is there a step I am missing? I have attempted to reboot NGINX, however the issue persists.

Originally created by @zaclively on GitHub (Apr 1, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/994 Hello, I am configuring a Stream in the UI and it is not working. ![image](https://user-images.githubusercontent.com/69009469/113361095-68128e00-9308-11eb-88b4-34761cf0b383.png) When I attempt to connect to the application directly it works, however when my destination in NGINX, it does not work. I also am not seeing a listening port for the configured stream as well: `systemd-r 801 systemd-resolve 13u IPv4 16338 0t0 TCP 127.0.0.53:53 (LISTEN) container 1053 root 8u IPv4 21412 0t0 TCP 127.0.0.1:44867 (LISTEN) sshd 1316 root 3u IPv4 21345 0t0 TCP *:22 (LISTEN) sshd 1316 root 4u IPv6 21347 0t0 TCP *:22 (LISTEN) docker-pr 2079 root 4u IPv6 25483 0t0 TCP *:443 (LISTEN) docker-pr 2092 root 4u IPv6 25510 0t0 TCP *:81 (LISTEN) docker-pr 2104 root 4u IPv6 25535 0t0 TCP *:80 (LISTEN) ` Is there a step I am missing? I have attempted to reboot NGINX, however the issue persists.
kerem 2026-02-26 06:34:36 +03:00
  • closed this issue
  • added the
    stale
    label
Author
Owner

@chaptergy commented on GitHub (May 12, 2021):

Have you exposed the port to outside of your docker container in your docker-compose?

<!-- gh-comment-id:840167858 --> @chaptergy commented on GitHub (May 12, 2021): Have you exposed the port to outside of your docker container in your docker-compose?
Author
Owner

@adifelice-godaddy commented on GitHub (Oct 6, 2021):

Have you exposed the port to outside of your docker container in your docker-compose?

That fixed my problem. Exposed both TPC and UDP ports in compose, 554 in my case:

    ports:
      - 80:80
      - 81:81
      - 443:443
      - 554:554
      - 554:554/udp

I hope that helps. Thanks @chaptergy

<!-- gh-comment-id:936154998 --> @adifelice-godaddy commented on GitHub (Oct 6, 2021): > Have you exposed the port to outside of your docker container in your docker-compose? That fixed my problem. Exposed both `TPC` and `UDP` ports in compose, `554` in my case: ```yaml ports: - 80:80 - 81:81 - 443:443 - 554:554 - 554:554/udp ``` I hope that helps. Thanks @chaptergy
Author
Owner

@sanegaming commented on GitHub (Apr 19, 2022):

I am also having this problem, is there any chance to get this to work without manual file changes?

<!-- gh-comment-id:1102029315 --> @sanegaming commented on GitHub (Apr 19, 2022): I am also having this problem, is there any chance to get this to work without manual file changes?
Author
Owner

@github-actions[bot] commented on GitHub (Mar 15, 2024):

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

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

@github-actions[bot] commented on GitHub (Apr 26, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2831741996 --> @github-actions[bot] commented on GitHub (Apr 26, 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#834
No description provided.