Resource health status not updating when Newt tunnel is down #315

New Issue

MrUnknownDE · 2026-04-05T17:05:49+02:00

MrUnknownDE commented

2026-04-05 17:05:49 +02:00

Originally created by @shaftspanner on 1/27/2026

Describe the Bug

I've successfully connected Pangolin to lots of docker containers running in Proxmox LXCs and the health checks reflect the state of those docker containers. I have a Newt instance running in docker in each LXC.

I've just noticed that if I shut down the Proxmox LXC, obviously all docker containers in that LXC stop (including NEWT):

The site status (i.e. the status of the connection to a NEWT instance) is correct - it shows offline
The resource status (i.e. the status of the docker container accessed via the NEWT tunnel) remains as it was before the NEWT tunnel shut down

This is misleading - if the Newt tunnel is down, the resources (docker containers) aren't going to be available - I think the resource health should reflect this in some way

Environment

OS Type & Version: (e.g., Ubuntu 22.04)
Pangolin Version: 1.15.1
Gerbil Version: 1.3.0
Traefik Version: 3.6.7
Newt Version: 1.8.1 / 1.9.0

Proxmox Instance: 8.4.14

To Reproduce

Run Newt (and other containers) in docker inside Proxmox LXC
Create site in Pangolin tunnelling to Newt instance
Create resources (for the docker containers) with Pangolin health checks
Shut down LXC

Expected Behavior

Resource health should reflect the fact that the resources (docker containers) can't be reached rather than reflecting the last known status before the site became unavailable

*Originally created by @shaftspanner on 1/27/2026* ### Describe the Bug I've successfully connected Pangolin to lots of docker containers running in Proxmox LXCs and the health checks reflect the state of those docker containers. I have a Newt instance running in docker in each LXC. I've just noticed that if I shut down the Proxmox LXC, obviously all docker containers in that LXC stop (including NEWT): - The site status (i.e. the status of the connection to a NEWT instance) is correct - it shows offline - The resource status (i.e. the status of the docker container accessed via the NEWT tunnel) remains as it was before the NEWT tunnel shut down This is misleading - if the Newt tunnel is down, the resources (docker containers) aren't going to be available - I think the resource health should reflect this in some way ### Environment - OS Type & Version: (e.g., Ubuntu 22.04) - Pangolin Version: 1.15.1 - Gerbil Version: 1.3.0 - Traefik Version: 3.6.7 - Newt Version: 1.8.1 / 1.9.0 Proxmox Instance: 8.4.14 ### To Reproduce Run Newt (and other containers) in docker inside Proxmox LXC Create site in Pangolin tunnelling to Newt instance Create resources (for the docker containers) with Pangolin health checks Shut down LXC ### Expected Behavior Resource health should reflect the fact that the resources (docker containers) can't be reached rather than reflecting the last known status before the site became unavailable

MrUnknownDE closed this issue

2026-04-05 17:05:49 +02:00

Sign in to join this conversation.

Branches Tags

main

dev

dependabot/npm_and_yarn/dev-minor-updates-b4e5d6b9c5

revert-2766-feature/systemd-install-instructions

dependabot/npm_and_yarn/prod-patch-updates-05702d39f2

dependabot/npm_and_yarn/next-16.2.1

dependabot/npm_and_yarn/recharts-3.8.1

alerting-rules

private-site-ha

dependabot/docker/docker/library/node-25-slim

ssh

delete-account

msg-delivery

org-only-idp

cicd

patch

site-targets-auto-login

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/pangolin#315