[Feature Request] Pangolin auth over non standard HTTPS ports #1587

New Issue

MrUnknownDE · 2026-04-05T19:36:20+02:00

MrUnknownDE commented

2026-04-05 19:36:20 +02:00

Originally created by @stryk3rr3al on 4/23/2025

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.

*Originally created by @stryk3rr3al on 4/23/2025* 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. ![image](https://github.com/user-attachments/assets/ee6a4a56-b099-4b41-a529-847cf6511d3d) 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.

MrUnknownDE closed this issue

2026-04-05 19:36:20 +02:00

Sign in to join this conversation.

Branches Tags

main

dev

dependabot/npm_and_yarn/dev-minor-updates-b4e5d6b9c5

revert-2766-feature/systemd-install-instructions

dependabot/npm_and_yarn/prod-patch-updates-05702d39f2

dependabot/npm_and_yarn/next-16.2.1

dependabot/npm_and_yarn/recharts-3.8.1

alerting-rules

private-site-ha

dependabot/docker/docker/library/node-25-slim

ssh

delete-account

msg-delivery

org-only-idp

cicd

patch

site-targets-auto-login

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/pangolin#1587