starred/nginx-proxy-manager-NginxProxyManager

Fork 0

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

[GH-ISSUE #377] Unable stream #320

New issue

Closed

opened 2026-02-26 06:32:15 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 06:32:15 +03:00

Owner

Originally created by @ghost on GitHub (Apr 17, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/377

I really love this useful project, I already add proxy host and it works perfectly. If I'm not mistaken understanding the stream feature, it can forward tcp/udp. However it fails when I try to forward my ftp or ssh session. Anyone knows how can I troubleshoot this? Any help would be greatly appreciated. Thank you

Originally created by @ghost on GitHub (Apr 17, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/377 I really love this useful project, I already add proxy host and it works perfectly. If I'm not mistaken understanding the stream feature, it can forward tcp/udp. However it fails when I try to forward my ftp or ssh session. Anyone knows how can I troubleshoot this? Any help would be greatly appreciated. Thank you

kerem closed this issue

2026-02-26 06:32:15 +03:00

kerem commented

2026-02-26 06:32:16 +03:00

Author

Owner

@jc21 commented on GitHub (Apr 17, 2020):

So you've probably set up a stream to forward, for example, port 21 to 192.168.0.10:21

But you probably haven't opened up the Docker Container to accept connections on port 21. I know this isn't a widely documented feature, but the ports aren't a widely used feature either.

Modify your docker-compose.yml file to open the ports you want to stream onwards and see how you go

@jc21 commented on GitHub (Apr 17, 2020): So you've probably set up a stream to forward, for example, port 21 to 192.168.0.10:21 But you probably haven't opened up the Docker Container to accept connections on port 21. I know this isn't a widely documented feature, but the ports aren't a widely used feature either. Modify your docker-compose.yml file to open the ports you want to stream onwards and see how you go

kerem commented

2026-02-26 06:32:16 +03:00

Author

Owner

@ghost commented on GitHub (Apr 17, 2020):

The scenario is I want to forward incoming port TCP 1010, to destination IP xx.xx.xx.xx port (SSH) TCP 2020. I tried 1010:1010, 1010:2020, 1-65535:1-65535, but still no luck.
Sorry if it looks silly, I hope I understand this right.

@ghost commented on GitHub (Apr 17, 2020): The scenario is I want to forward incoming port TCP 1010, to destination IP xx.xx.xx.xx port (SSH) TCP 2020. I tried 1010:1010, 1010:2020, 1-65535:1-65535, but still no luck. Sorry if it looks silly, I hope I understand this right.

kerem commented

2026-02-26 06:32:16 +03:00

Author

Owner

@ghost commented on GitHub (Apr 20, 2020):

Hi I got this working now, I just forgot to restart the docker-compose, my bad.
Anyway, can I just open all ports in docker-compose.yml so I don't need to specify one by one, and let me decide which port to use in NPM dashboard?

@ghost commented on GitHub (Apr 20, 2020): Hi I got this working now, I just forgot to restart the docker-compose, my bad. Anyway, can I just open all ports in docker-compose.yml so I don't need to specify one by one, and let me decide which port to use in NPM dashboard?

kerem commented

2026-02-26 06:32:16 +03:00

Author

Owner

@jc21 commented on GitHub (Apr 20, 2020):

I do not recommend opening all ports with 1-65535:1-65535 as this converts to the native docker command -p 1:1 -p 2:2 -p 3:3 ... and it slows a lot of stuff down as well as being impractical.

The better solution is to run NPM docker container in Host Network Mode. If you are running your db in a docker container too, that might also have to be in host network mode and when doing so, the hostname for the database would be 127.0.0.1

@jc21 commented on GitHub (Apr 20, 2020): I do not recommend opening all ports with `1-65535:1-65535` as this converts to the native docker command `-p 1:1 -p 2:2 -p 3:3 ...` and it slows a lot of stuff down as well as being impractical. The better solution is to run NPM docker container in [Host Network Mode](https://docs.docker.com/network/host/). If you are running your db in a docker container too, that might also have to be in host network mode and when doing so, the hostname for the database would be `127.0.0.1`

kerem referenced this issue

2026-02-26 06:34:45 +03:00

[GH-ISSUE #1029] Proxy single file #865

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

No description provided.

Rows
Columns