mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #164] Add sshttp Support #143
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#143
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cdrfun on GitHub (Jul 3, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/164
Nginx Proxy Manager is often used by professional home users who want to host several services by themselves. Those are also often confronted with another problem: workplace oder client networks which are "secured" by a proxy which doen't allow them to SSH to their beloved machines. SSHTTP uses several ways to distingish HTTP(S) from SSH traffic and re-route it accordingly.
Ideally you would define a seperate subdomain (ssh.example.com), set the scheme to ssh and define the host and port ssh shall be forwarded to. All irrelevant options (imho all other) could be disabled.
@Xaero252 commented on GitHub (Sep 15, 2019):
Perhaps even use SSLH since that also allows one to add OpenVPN to the list of things that can be directed through the SSL port.
I've been trying to do this with two separate dockers but it's not easy since the hosts get confused as to where the traffic originated.
@github-actions[bot] commented on GitHub (Apr 3, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@cdrfun commented on GitHub (Apr 3, 2024):
I still think this would be a useful addition to Nginx Proxy Manager.
@github-actions[bot] commented on GitHub (Dec 23, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@cdrfun commented on GitHub (Jan 6, 2025):
I still think this would be a useful addition to Nginx Proxy Manager.
@github-actions[bot] commented on GitHub (Nov 13, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@cdrfun commented on GitHub (Nov 13, 2025):
Ping