mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #3796] Integration of Protocol-Multiplex (sslh) for using same port on different protocols #2499
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#2499
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 @demlak on GitHub (Jun 9, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3796
Is your feature request related to a problem? Please describe.
heyho..
often, people are inside networks which have port-restrictions and it is not possible to directly use ssh/openvpn/etc. on their default ports to reach (home)servers - but usually ports 80 and 443 are opened to surf the web.
Describe the solution you'd like
sslh is a nice solution/successor for managing different protocols parallel on only one port. for sure it would be possible to use sslh one step before NPM.. but it would be nice to configure protocol-multiplexing inside NPM instead of manually/outside of NPM
Describe alternatives you've considered
maybe an alternative would be to manage the problem totaly on clientside by using corkskrew for ssh-connections and put other protocols ontop of this connection.. but thats 1. complex 2. inefficient 3. not platform-independent (linux, windows, mac-os, iOS, BSD, Android, whatever..) usable.
@github-actions[bot] commented on GitHub (Dec 25, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@demlak commented on GitHub (Dec 25, 2024):
stalebot does stale-things
@github-actions[bot] commented on GitHub (Sep 1, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@demlak commented on GitHub (Sep 1, 2025):
bad stale-bot! =)