nginx-proxy-manager icon indicating copy to clipboard operation
nginx-proxy-manager copied to clipboard
Published 2 months ago • verified publisher icon NginxProxyManager

ssh port

Open fahadshery opened this issue 4 years ago • 6 comments

Hi,

I have set up my gitlab instance on port 80 and 443 with no issues. I had to forward ports (80, 443) to npm and that was it.

Now my gitlab instance supports ssh on lets say on ssh://[email protected]:30022/group/project.git. Obviously, this wouldn't work because there are only two options available http and https as show in below picture: Screenshot 2022-01-18 at 22 43 36

How do I forward traffic to my gitlab instance when I get the destination port of 30022?? (this is the port my gitlab server is listening for ssh connections)...

I have already opened the port 30022 and my router and forwarded it to the npm container

Many thanks

fahadshery avatar Jan 18 '22 22:01 fahadshery

I guess you are looking for a stream proxy.

SamuelNitsche avatar Jan 21 '22 09:01 SamuelNitsche

Did you find the answer? I solved it using duckdns.org outside the domain used in npm, what I mean is that I do a parallel domain with exposed ports... I would love to access ssh through npm. Thanks

valkanoise avatar Sep 10 '22 01:09 valkanoise

Any luck? I was expecting stream proxy to be the solution, but I cannot have it working :(

gregfr avatar Dec 07 '22 07:12 gregfr

Any luck? I was expecting stream proxy to be the solution, but I cannot have it working :(

Hello @gregfr you can solve our issue using a ddns, for me was the easiest way. Either duckdns.org or if you have you own domain you can try cloudflare tunnels = cloudflared. The latest is a really amazing tool, you don't even need to expose your ports to internet. I am right now using cloudflared for each of my raspberries, and the ip is even proxied, so no one can see you public ip. Nice! Best regards,

Fede

valkanoise avatar Dec 07 '22 07:12 valkanoise

Thanks for the tip, but my problem was in fact an upstream firewall I didn't know about. Now it's working with the basic "stream" proxy.

gregfr avatar Dec 07 '22 19:12 gregfr

Thanks for the tip, but my problem was in fact an upstream firewall I didn't know about. Now it's working with the basic "stream" proxy.

@gregfr I am glad to read that you were able to solve it, would you be kind enough to describe your solution? Would be nice to see it and maybe I can also apply it, just for the sake of learning something new. Thanks!!!

valkanoise avatar Dec 08 '22 08:12 valkanoise

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

github-actions[bot] avatar Feb 27 '24 01:02 github-actions[bot]