Health check status still showing after converting to local site

[jongrall]

Describe the Bug

The health check feature for targets previously worked fine for me. Now I cannot turn on health check for any new targets, nor edit health checks for any targets that have it already setup (they do show status correctly in the Resources table). It seems a recent update broke something.

All I see in the health check column where the settings would be is "–". Screenshot attached.

Note this is for a local Site (no tunneling). The targets are all Tailscale nodes over 100.0.0.0/8 IPv4 addresses.

Environment

• OS Type & Version: Debian GNU/Linux 13 (trixie)
• Pangolin Version: 1.13.1
• Gerbil Version: 2.40.1
• Traefik Version: 3.6.5
• Newt Version: n/a (not using)
• Olm Version: (if applicable)

To Reproduce

Try to configure a target for a local site on the latest version of Pangolin.

Expected Behavior

Health checks can be turned on, edited, and turned off for all targets.

[oschwartz10612]

Hi! Health checks have always only worked for newt sites and not local sites. The newt itself is what is making the health check request. I am not sure why it would have been previously working? Unfortunately this is expected behavior but please feel free to reopen if I am misunderstanding.

[jongrall]

@oschwartz10612 Thanks for looking at this bug report so quickly!

So I have never used Pangolin with Newt because I found it to be a bit slow with limited bandwidth (possibly because of some overhead) for communication between my server running Pangolin and my remote private targets. I have found Tailscale to be a lot more performant, which worked out nicely because all my targets already have Tailscale running on them.

As a result, I have only used Pangolin with a local site (the Pangolin server is running Tailscale and can access Tailscale targets using their tailnet IP address). However, I was previously able to configure Health Check with these targets, and my Resources table does show that targets that were configured before a recent update do have Health Check working and report their status. See attached screenshot. The ones with status "Unknown" are the new targets which I added in the last week, for which Health Check does not work.

There's a bug somewhere here. Either I should be able to configure Health Check for local site targets, or I shouldn't be seeing Health Check status for any of my local site targets.

I do not have permission to reopen this issue, but perhaps you may want to given this additional information.

[oschwartz10612]

Ahh okay I wonder if what happened here is you had health checks running when it was a newt and then switched to local sites and the status was not cleared so it still shows in the table. I think the status should clear when you switch the site to a local site. I am thinking thats the bug maybe?

I marked and assigned this to myself to take a look! 😄

[jongrall]

@oschwartz10612 You're probably correct that I had health checks running when my first target was a newt connection. However, I only installed newt on a single target machine and resource, quickly abandoned it, and setup all my other resources targets on a local site over Tailscale. They had Health Checks working (or at least, showing a "Healthy" status - that could have been inaccurate), but now the existing Health Checks are not editable (but still showing "Healthy"), and any new local targets show an "Unknown" status (which you said is expected behavior for local targets).

[suddenelfilio]

I use the same setup, local site with tailscale and would like to see health checks working in these scenarios since eventhough for pangolin it seems local, the tailscale does distribute over de netwerk...

[oschwartz10612]

Duplicate of #2181 I think. Tracking there.