Health Check disables "unsecured" site

[Kornelius777]

Describe the Bug

Dear all,

• create a ressource
• turn off Platform SSO
• turn on Health Check

The ressource will no longer be accessible, but get a 404

Environment

• OS Type & Version: (e.g., Ubuntu 22.04)
• Pangolin Version: 1.12.2
• Gerbil Version: latest
• Traefik Version: latest
• Newt Version: latest

To Reproduce

• create a ressource
• turn off Platform SSO
• turn on Health Check

Expected Behavior

Still be accessible

[Kornelius777]

Oh, and you cannot just disable Health Check. You will need to delete the resource and recreate it.

[keonramses]

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]

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]

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]

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?

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]

Something similar just happened to me with different services. I disabled and re-enabled the health checks, and now it works.

[lachermeierm]

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