I'm looking to replace CF Tunnels with this and one thing I can't seem to get to work that works with CF Tunnels is the ability to assign a resource (example.domain.com) to my internal Traefik instance, which handles routing and optional authentication via Authentik.
In CF Tunnels, I have the following:
example.domain.com hostname pointing to internal Traefik ip (https://10.x.x.x)
Traefik handles all forwarding and optional auth via Authentik
Having the same setup in Pangolin results in a Misdirect error
I'd love to know this is already possible and I'm just missing something! If not, is this something that can be added to the roadmap?
Originally created by @rfrank on GitHub (Feb 9, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/178
I'm looking to replace CF Tunnels with this and one thing I can't seem to get to work that works with CF Tunnels is the ability to assign a resource (example.domain.com) to my internal Traefik instance, which handles routing and optional authentication via Authentik.
In CF Tunnels, I have the following:
example.domain.com hostname pointing to internal Traefik ip (https://10.x.x.x)
Traefik handles all forwarding and optional auth via Authentik
Having the same setup in Pangolin results in a Misdirect error
I'd love to know this is already possible and I'm just missing something! If not, is this something that can be added to the roadmap?
I don't think what you're describing is currently supported by Pangolin but it may be in the future. Can you describe a little bit more how this would function? If you point one subdomain to another Traefik instance, do you access the individual services via sub paths?
<!-- gh-comment-id:2646690752 -->
@miloschwartz commented on GitHub (Feb 10, 2025):
I don't think what you're describing is currently supported by Pangolin but it may be in the future. Can you describe a little bit more how this would function? If you point one subdomain to another Traefik instance, do you access the individual services via sub paths?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @rfrank on GitHub (Feb 9, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/178
I'm looking to replace CF Tunnels with this and one thing I can't seem to get to work that works with CF Tunnels is the ability to assign a resource (example.domain.com) to my internal Traefik instance, which handles routing and optional authentication via Authentik.
In CF Tunnels, I have the following:
example.domain.com hostname pointing to internal Traefik ip (https://10.x.x.x)
Traefik handles all forwarding and optional auth via Authentik
Having the same setup in Pangolin results in a Misdirect error
I'd love to know this is already possible and I'm just missing something! If not, is this something that can be added to the roadmap?
@miloschwartz commented on GitHub (Feb 10, 2025):
I don't think what you're describing is currently supported by Pangolin but it may be in the future. Can you describe a little bit more how this would function? If you point one subdomain to another Traefik instance, do you access the individual services via sub paths?