Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate listening and access port #9

Mika56 opened this issue May 17, 2019 · 2 comments


None yet
2 participants
Copy link

commented May 17, 2019


I our deployment, Sish listens on port 443, but it is behind a firewall that does a PAT on port 30443.
It would be nice to have a new option, something like -sish.https_access=30443 (or a better name).
This wouldn't change any of the operations done by Sish, it would just change the message when connection is done:

HTTP requests for 80 and **30443** can be reached on host: <hidden>
Press Ctrl-C to close the session.

This comment has been minimized.

Copy link

commented May 20, 2019

I think this is useful, but my intentions for that message wasn't to describe what ports can be accessed, but instead to report the ports on the backend side of the SSH connection that can be accessed. Maybe it would be more worthwhile to make the message more explicit? Something like:

HTTP(S) requests can be made to http://<hidden>:<port> or https://<hidden>:<port>
Press Ctrl-C to close the session.

What're your thoughts on this, do you think it would suffice? Feel free to hop on IRC to chat about it too.


This comment has been minimized.

Copy link

commented May 30, 2019

With the latest version I released, I've added two options -sish.httpport and -sish.httpsport both of these don't change where the listeners are, they are only visual flags for the output message when a connection is established with forwarding requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.