[GH-ISSUE #2736] Health checks are still running when Ressource is disabled #30058

Closed
opened 2026-06-13 10:29:30 -05:00 by GiteaMirror · 6 comments
Owner

Originally created by @maieredv-manuel on GitHub (Mar 29, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2736

Describe the Bug

Health checks are still running when Ressource is disabled

Environment

  • OS Type & Version: Debian 12
  • Pangolin Version: v1.16.2
  • Gerbil Version: 1.3.0
  • Traefik Version: 3.6
  • Newt Version: 1.10.3
  • Olm Version: (if applicable)

To Reproduce

Disable an Ressource with enabled Healthchecks and look in the logs of newt.

Expected Behavior

If i disable a Ressource also the Healthchecks sould be disabled

Originally created by @maieredv-manuel on GitHub (Mar 29, 2026). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2736 ### Describe the Bug Health checks are still running when Ressource is disabled ### Environment - OS Type & Version: Debian 12 - Pangolin Version: v1.16.2 - Gerbil Version: 1.3.0 - Traefik Version: 3.6 - Newt Version: 1.10.3 - Olm Version: (if applicable) ### To Reproduce Disable an Ressource with enabled Healthchecks and look in the logs of newt. ### Expected Behavior If i disable a Ressource also the Healthchecks sould be disabled
GiteaMirror added the buggood first issuehelp wanted labels 2026-06-13 10:29:31 -05:00
Author
Owner

@oschwartz10612 commented on GitHub (Mar 29, 2026):

Yeah we should send a message to add and remove the healthchecks when enabled and disabled to the newt downstream.

<!-- gh-comment-id:4150886818 --> @oschwartz10612 commented on GitHub (Mar 29, 2026): Yeah we should send a message to add and remove the healthchecks when enabled and disabled to the newt downstream.
Author
Owner

@Adarsh-Raj-Jaiswal commented on GitHub (Mar 30, 2026):

Hi! I'd love to work on this issue. I plan to locate the resource update router and dispatch a WebSocket message to the Newt client to add/remove health checks based on the enabled state. Let me know if you have any architectural pointers!

<!-- gh-comment-id:4153880455 --> @Adarsh-Raj-Jaiswal commented on GitHub (Mar 30, 2026): Hi! I'd love to work on this issue. I plan to locate the resource update router and dispatch a WebSocket message to the Newt client to add/remove health checks based on the enabled state. Let me know if you have any architectural pointers!
Author
Owner

@oschwartz10612 commented on GitHub (Mar 30, 2026):

Sure @Adarsh-Raj-Jaiswal give it a shot. I will review the PR when you are ready.

<!-- gh-comment-id:4156587309 --> @oschwartz10612 commented on GitHub (Mar 30, 2026): Sure @Adarsh-Raj-Jaiswal give it a shot. I will review the PR when you are ready.
Author
Owner

@Adarsh-Raj-Jaiswal commented on GitHub (Apr 6, 2026):

Since I have windows so I was facing some issues in setting up pangolin. But now it's done and I'm able to proceed on this. Just wanted to update about this :)

<!-- gh-comment-id:4190215802 --> @Adarsh-Raj-Jaiswal commented on GitHub (Apr 6, 2026): Since I have windows so I was facing some issues in setting up pangolin. But now it's done and I'm able to proceed on this. Just wanted to update about this :)
Author
Owner

@oschwartz10612 commented on GitHub (May 1, 2026):

This was fixed in the 1.18.1 release!

<!-- gh-comment-id:4361972129 --> @oschwartz10612 commented on GitHub (May 1, 2026): This was fixed in the 1.18.1 release!
Author
Owner

@LeonvanHeerden commented on GitHub (Jun 13, 2026):

I am moving some resources to run through the new Newt 1.13.0. The not all the endpoints are active at the moment. Using Pangolin 1.19.1

Enabled health checks and found that the target is offline. I then disable the resource as well as HTTPS Target access. the Health-check on the Newt connection continues to run and fail.

newt  | WARN: 2026/06/13 04:21:43 Target 96: health check failed: Get "http://192.168.1.9:8888/": dial tcp 192.168.1.9:8888: connect: connection refused

I also have to also disabled the health check and I see newt is still continuing the healthcheck.

I restarted the Newt container to see if that stops the checks and it looks like that worked. So maybe there is no instruction to newt to stop checking the health?

<!-- gh-comment-id:4697497009 --> @LeonvanHeerden commented on GitHub (Jun 13, 2026): I am moving some resources to run through the new Newt 1.13.0. The not all the endpoints are active at the moment. Using Pangolin 1.19.1 Enabled health checks and found that the target is offline. I then disable the resource as well as HTTPS Target access. the Health-check on the Newt connection continues to run and fail. ``` newt | WARN: 2026/06/13 04:21:43 Target 96: health check failed: Get "http://192.168.1.9:8888/": dial tcp 192.168.1.9:8888: connect: connection refused ``` I also have to also disabled the health check and I see newt is still continuing the healthcheck. I restarted the Newt container to see if that stops the checks and it looks like that worked. So maybe there is no instruction to newt to stop checking the health?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#30058