mirror of
https://github.com/fosrl/pangolin.git
synced 2026-07-17 07:04:36 -05:00
[GH-ISSUE #570] [Feature Request] Pangolin auth over non standard HTTPS ports #18596
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#18596
Reference in New Issue
Block a user
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 @stryk3rr3al on GitHub (Apr 23, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/570
Hello everyone,
I am currently using Pegolin as a standard reverse proxy behind a VPN provider that allows limited port forwarding (specifically, port 17787 for me). The Pegolin admin interface is successfully accessible externally at pegolin.mydomain.xyz:17787. However, any resources or applications hosted behind Pegolin are not accessible externally, auth seems to fail since pangolin is passing 443 based redirects back in the auth URLS.
I have included a schematic of my intended use case.
Port 17787 is forwarded from the VPN provider to my internal network.
The Pegolin administrative dashboard is reachable via pegolin.mydomain.xyz:17787.
Services proxied through Pegolin (e.g., web applications) do not become accessible externally through the same forwarded port.
I understand that this is an unconventional setup, as most reverse proxies operate over standard ports (80/443), but the ability to forward services through a single custom port would allow Pegolin to be accessed when port 443 and 80 can't be exposed.