starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 09:55:51 +03:00

[GH-ISSUE #1924] Unexpected output on stream #1404

New issue

Closed

opened 2026-02-26 07:30:51 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 07:30:51 +03:00

Owner

Originally created by @stelmaszyk on GitHub (Mar 11, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1924

I am experiencing issues with streams on port 3000.
If I understand correctly, streams are forwarding ports.
I have a VM inside the network that has a configuration panel listening on port 3000.

The screenshot below shows the current configuration

I know that the internal address is correct because I can reach the configuration page from LAN, but for DNS checks, it needs to be public for a while.

The problem is, that instead of configuration panel, I can see this:
{"status":"OK","version":{"major":2,"minor":9,"revision":16}}

Firewall on target VM allows traffic on ports 80, 443, 3000 (output from firewalld):
ports: 80/tcp 443/tcp 3000/tcp

Originally created by @stelmaszyk on GitHub (Mar 11, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1924 I am experiencing issues with streams on port 3000. If I understand correctly, streams are forwarding ports. I have a VM inside the network that has a configuration panel listening on port 3000. The screenshot below shows the current configuration ![image](https://user-images.githubusercontent.com/48010443/157859293-46436655-0c98-4ff9-a2b4-27017c223b24.png) I know that the internal address is correct because I can reach the configuration page from LAN, but for DNS checks, it needs to be public for a while. The problem is, that instead of configuration panel, I can see this: `{"status":"OK","version":{"major":2,"minor":9,"revision":16}}` Firewall on target VM allows traffic on ports 80, 443, 3000 (output from firewalld): `ports: 80/tcp 443/tcp 3000/tcp`

kerem

2026-02-26 07:30:51 +03:00

closed this issue
added the
stale
label

kerem commented

2026-02-26 07:30:51 +03:00

Author

Owner

@EpicLPer commented on GitHub (Dec 1, 2022):

Just coming by to say I have the same weird behavior...

When I put in "127.0.0.1" with HTTP Port 3000 I get the same exact output as above, even tho none of my Docker Containers nor the Linux host itself is even running anything on said port. The only possible option by now is that Nginx Proxy Manager itself somehow hosts an internal service which exposes it this way then which is very weird...

@EpicLPer commented on GitHub (Dec 1, 2022): Just coming by to say I have the same weird behavior... When I put in "127.0.0.1" with HTTP Port 3000 I get the same exact output as above, even tho none of my Docker Containers nor the Linux host itself is even running anything on said port. The only possible option by now is that Nginx Proxy Manager itself somehow hosts an internal service which exposes it this way then which is very weird...

kerem commented

2026-02-26 07:30:51 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 21, 2024):

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

@github-actions[bot] commented on GitHub (Feb 21, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:30:51 +03:00

Author

Owner

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

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Apr 6, 2025): Issue was closed due to inactivity.

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#1404

No description provided.

Rows
Columns