[Feature Request] SSL Proxy on non-standard-ports #1072

Closed
opened 2026-04-05 18:13:46 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @LukasSchulz on 8/13/2025

I am currently in the process of migrating my infrastructure to pangolin.

One problem I am facing right now is that I am unable to encrypt the traffic using SSL ports other than the standard port 443.
Matrix/synapse for example needs SSL on port 8448 docs.

As of now I am able to create a RAW TCP Ressource and proxying that to the service publicly, but SSL seems to be only available on the standard ports.

Maybe I overlooked something, is it currently possible to achieve this, if so, how (or maybe there is a workaround for now)?

*Originally created by @LukasSchulz on 8/13/2025* I am currently in the process of migrating my infrastructure to pangolin. One problem I am facing right now is that I am unable to encrypt the traffic using SSL ports other than the standard port `443`. Matrix/synapse for example needs SSL on port `8448` [docs](https://element-hq.github.io/synapse/latest/reverse_proxy.html). As of now I am able to create a RAW TCP Ressource and proxying that to the service publicly, but SSL seems to be only available on the standard ports. Maybe I overlooked something, is it currently possible to achieve this, if so, how (or maybe there is a workaround for now)?
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#1072