mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-07 21:30:36 -05:00
[GH-ISSUE #1865] Health Check disables "unsecured" site #8796
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#8796
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 @Kornelius777 on GitHub (Nov 15, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1865
Describe the Bug
Dear all,
The ressource will no longer be accessible, but get a 404
Environment
To Reproduce
Expected Behavior
Still be accessible
@Kornelius777 commented on GitHub (Nov 15, 2025):
Oh, and you cannot just disable Health Check. You will need to delete the resource and recreate it.
@keonramses commented on GitHub (Nov 15, 2025):
I can confirm this happens on my instance. What I do notice is that if the health check fails once, the entire resource becomes unavailable and you have to delete and recreate it in order to access it again.
OS Type & Version: Rocky Linux 10
Pangolin Version: ee-1.12.2
Gerbil Version: 1.2.2
Traefik Version: 3.5.3
Newt Version: 1.6.0
Olm Version: N/A
@maxus-git commented on GitHub (Nov 17, 2025):
Same here.
I spent 3 days on finding out that finally deleting the target and add it again without healthcheck enabled brings my Joplin Server actually back to life. Played around with custom headers and so on like for hours.
Also changing only the healthcheck port to a Service on the same IP which is working, enables the Resource again.
OS Type & Version: Ubuntu 24.04
Pangolin Version: 1.12.2
Gerbil Version: 1.2.2
Traefik Version: 3.6.1
Newt Version: 1.6.0
@oschwartz10612 commented on GitHub (Nov 18, 2025):
When you are removing the target is the status still "unhealthy"? If so
thats why because it wont be included in the rotation if the status is
"unhealthy" and disabling it does not reset the status.
Maybe we should reset the status to "unknown" when disabling the health
checks?
@maxus-git commented on GitHub (Nov 18, 2025):
No, if I remove the target, the status of the health check in the overview is "unknown".
If I deactivate only the health check, nothing changes -> after Saving Resource -> status still unhealthy and Resource is not working.
Yes I agree with resetting the status to "unknown" when disabling the health check (That was also what I expected).
I have 10 services that are checked by health check and all report "healthy". Only the Joplin server (https://github.com/laurent22/joplin) is causing problems here. Maybe this is a problem with Joplin, but I don't understand why the health check isn't working here, as the service is functioning normally.
@drazvt commented on GitHub (Nov 19, 2025):
Something similar just happened to me with different services. I disabled and re-enabled the health checks, and now it works.
@lachermeierm commented on GitHub (Nov 20, 2025):
For me, it’s the same—when the health check is enabled for my Nextcloud AIO, it becomes unreachable.
I get the error message: 404 page not found.
If I disable the health check for my NC, it works.
Ubuntu 24.04.3 LTS
Pangolin Version: 1.12.2
Gerbil Version: 1.2.2
Traefik Version: 3.6.1
Newt Version: 1.6.0
@github-actions[bot] commented on GitHub (Dec 5, 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.
@maxus-git commented on GitHub (Dec 5, 2025):
Still an issue.
@Node815 commented on GitHub (Dec 8, 2025):
I concur, this is happening, Baserow dies as soon as I enable it. As per the other posters, manual removal and re-addition of this is required to get it back online.