github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-07-16 22:55:14 -05:00
Code Issues 1.6k Packages Projects Releases 79 Wiki Activity

[GH-ISSUE #1272] [Feature Request] SSL Proxy on non-standard-ports #1835

New Issue
Closed
opened 2026-04-16 08:41:51 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-16 08:41:51 -05:00
Owner
Copy Link

Originally created by @LukasSchulz on GitHub (Aug 13, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1272

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 GitHub (Aug 13, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/1272 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)?
GiteaMirror commented 2026-04-16 08:41:53 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Aug 15, 2025):

Yeah this is currently not possible as we put all HTTP behind 443. Are you sure you need 8448 and cant have it look at a subdomain on a 443 server?

If not the current work around would be to generate the SSL serverside downstream of pangolin I think. You could throw up anouther Traefik instance and have it manage the cert for you. Not super ideal I know 😬.

<!-- gh-comment-id:3192163056 --> @oschwartz10612 commented on GitHub (Aug 15, 2025): Yeah this is currently not possible as we put all HTTP behind 443. Are you sure you need 8448 and cant have it look at a subdomain on a 443 server? If not the current work around would be to generate the SSL serverside downstream of pangolin I think. You could throw up anouther Traefik instance and have it manage the cert for you. Not super ideal I know :grimacing:.
GiteaMirror commented 2026-04-16 08:41:53 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Aug 16, 2025):

Going to move this to a feature request in the discussions

<!-- gh-comment-id:3193405328 --> @oschwartz10612 commented on GitHub (Aug 16, 2025): Going to move this to a feature request in the discussions
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#1835
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?