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 GitHub (Jan 27, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2348
### 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
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @shaftspanner on GitHub (Jan 27, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2348
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):
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
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