Originally assigned to: @oschwartz10612 on GitHub.
Hey!
im testing pangolin right now, really nice peace of Software! But i have a litte problem:
when i activate the e-mail 2fa (or any other auth. method) the site is always online for tools like uptime-kuma, even if the newt connection is down because of an network interruption or the target server is powered off.
That makes monitoring of the websites a bit complicated.
Is there anyway to get an 404 or 502 or something else instead of the Auth. Screen when the target is offline?
Originally created by @maieredv-manuel on GitHub (Jul 11, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1051
Originally assigned to: @oschwartz10612 on GitHub.
Hey!
im testing pangolin right now, really nice peace of Software! But i have a litte problem:
when i activate the e-mail 2fa (or any other auth. method) the site is always online for tools like uptime-kuma, even if the newt connection is down because of an network interruption or the target server is powered off.
That makes monitoring of the websites a bit complicated.
Is there anyway to get an 404 or 502 or something else instead of the Auth. Screen when the target is offline?
@maieredv-manuel commented on GitHub (Jul 11, 2025):
Ive found an "workaround" i can add my Monitoring-Solution WAN-IP Adress to the "Always-Allow" Rule :-) So its not urgent, but i think its not a bad idea that the sign-in page dont appears when the target isnt online.
<!-- gh-comment-id:3062935043 -->
@maieredv-manuel commented on GitHub (Jul 11, 2025):
Ive found an "workaround" i can add my Monitoring-Solution WAN-IP Adress to the "Always-Allow" Rule :-) So its not urgent, but i think its not a bad idea that the sign-in page dont appears when the target isnt online.
@github-actions[bot] commented on GitHub (Jul 26, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
<!-- gh-comment-id:3120783795 -->
@github-actions[bot] commented on GitHub (Jul 26, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
This issue made me think of something interesting. Not sure how easily it could be done with pangolin, it might involve some funky config of traefik.
I use a wildcard as I imagine most others do for the subdomains. If all of my resources have authentication enabled this presents a method of "learning" valid subdomains by brute force with something similar to dirbuster (there is a subdomain equivalent). Any real resources will present the auth page and all others are dead. It would nice if we could enable an optional "honeypot" mode that makes all subdomains return the auth page.
As for this issue, I also have the same problem and I am using a similar workout to you. Although I have recently added tailscale and I am using the tailnet to check status with uptime kuma, so the traffic doesn't pass through pangolin.
<!-- gh-comment-id:3138221356 -->
@ryanehamil commented on GitHub (Jul 31, 2025):
This issue made me think of something interesting. Not sure how easily it could be done with pangolin, it might involve some funky config of traefik.
I use a wildcard as I imagine most others do for the subdomains. If all of my resources have authentication enabled this presents a method of "learning" valid subdomains by brute force with something similar to dirbuster (there is a subdomain equivalent). Any real resources will present the auth page and all others are dead. It would nice if we could enable an optional "honeypot" mode that makes all subdomains return the auth page.
As for this issue, I also have the same problem and I am using a similar workout to you. Although I have recently added tailscale and I am using the tailnet to check status with uptime kuma, so the traffic doesn't pass through pangolin.
@oschwartz10612 commented on GitHub (Aug 7, 2025):
Adding health checks in the next release of pangolin 1.9.0. Thinking we can expose a status page or something from that? Would have to to give it some thought. Maybe a path you define.
Otherwise now year it would make sense to use a bypass rule I think thats the easiest.
<!-- gh-comment-id:3166013001 -->
@oschwartz10612 commented on GitHub (Aug 7, 2025):
Adding health checks in the next release of pangolin 1.9.0. Thinking we can expose a status page or something from that? Would have to to give it some thought. Maybe a path you define.
Otherwise now year it would make sense to use a bypass rule I think thats the easiest.
This is because even if the site is down the middleware always redirects to the auth page. It's "kind of" feature because it obscured what is real and what is not.
<!-- gh-comment-id:3342134496 -->
@miloschwartz commented on GitHub (Sep 28, 2025):
This is because even if the site is down the middleware always redirects to the auth page. It's "kind of" _feature_ because it obscured what is real and what is not.
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 @maieredv-manuel on GitHub (Jul 11, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1051
Originally assigned to: @oschwartz10612 on GitHub.
Hey!
im testing pangolin right now, really nice peace of Software! But i have a litte problem:
when i activate the e-mail 2fa (or any other auth. method) the site is always online for tools like uptime-kuma, even if the newt connection is down because of an network interruption or the target server is powered off.
That makes monitoring of the websites a bit complicated.
Is there anyway to get an 404 or 502 or something else instead of the Auth. Screen when the target is offline?
@maieredv-manuel commented on GitHub (Jul 11, 2025):
Ive found an "workaround" i can add my Monitoring-Solution WAN-IP Adress to the "Always-Allow" Rule :-) So its not urgent, but i think its not a bad idea that the sign-in page dont appears when the target isnt online.
@github-actions[bot] commented on GitHub (Jul 26, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@ryanehamil commented on GitHub (Jul 31, 2025):
This issue made me think of something interesting. Not sure how easily it could be done with pangolin, it might involve some funky config of traefik.
I use a wildcard as I imagine most others do for the subdomains. If all of my resources have authentication enabled this presents a method of "learning" valid subdomains by brute force with something similar to dirbuster (there is a subdomain equivalent). Any real resources will present the auth page and all others are dead. It would nice if we could enable an optional "honeypot" mode that makes all subdomains return the auth page.
As for this issue, I also have the same problem and I am using a similar workout to you. Although I have recently added tailscale and I am using the tailnet to check status with uptime kuma, so the traffic doesn't pass through pangolin.
@oschwartz10612 commented on GitHub (Aug 7, 2025):
Adding health checks in the next release of pangolin 1.9.0. Thinking we can expose a status page or something from that? Would have to to give it some thought. Maybe a path you define.
Otherwise now year it would make sense to use a bypass rule I think thats the easiest.
@miloschwartz commented on GitHub (Sep 28, 2025):
This is because even if the site is down the middleware always redirects to the auth page. It's "kind of" feature because it obscured what is real and what is not.