Whenever the "Health Check" is enabled for a public resource, it will cause that public resource to go offline.
This behavior happens with Server Version 1.17.1 + Newt 1.12.0 , Reverting to Newt 1.11.0 fixes this issue.
This is a copy of the logs while the preview video was running
INFO: 2026/04/28 17:16:59 Newt version 1.12.0
ERROR: 2026/04/28 17:17:09 Error checking for updates: failed to fetch release info: Get "https://api.github.com/repos/fosrl/newt/releases/latest": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
INFO: 2026/04/28 17:17:09 Config file does not exist at /root/.config/newt-client/config.json, will create it
ERROR: 2026/04/28 17:17:39 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.whoisjason.me/api/v1/auth/newt/get-token": context deadline exceeded. Retrying in 3s...
INFO: 2026/04/28 17:17:43 Server version: 1.17.1
INFO: 2026/04/28 17:17:43 Saving config to: /root/.config/newt-client/config.json
INFO: 2026/04/28 17:17:43 Websocket connected
INFO: 2026/04/28 17:17:43 Connecting to endpoint: pangolin.whoisjason.me
INFO: 2026/04/28 17:17:43 Tunnel connection to server established successfully!
INFO: 2026/04/28 17:17:43 Starting monitoring for target 43 (10.0.0.15:3923)
INFO: 2026/04/28 17:17:43 Starting monitoring for target 61 (10.0.0.15:9443)
INFO: 2026/04/28 17:17:43 Starting monitoring for target 63 (10.0.0.15:8096)
INFO: 2026/04/28 17:17:43 Starting monitoring for target 65 (10.0.0.15:2283)
INFO: 2026/04/28 17:17:43 Starting health check monitoring for target 43 (10.0.0.15:3923)
INFO: 2026/04/28 17:17:43 Starting health check monitoring for target 61 (10.0.0.15:9443)
INFO: 2026/04/28 17:17:43 Starting health check monitoring for target 63 (10.0.0.15:8096)
INFO: 2026/04/28 17:17:43 Started tcp proxy to 10.0.0.15:8096
INFO: 2026/04/28 17:17:43 Started tcp proxy to 10.0.0.15:2283
INFO: 2026/04/28 17:17:43 Started tcp proxy to backend:3001
INFO: 2026/04/28 17:17:43 Started tcp proxy to invidious:3000
INFO: 2026/04/28 17:17:43 Started tcp proxy to 10.0.0.15:9443
INFO: 2026/04/28 17:17:43 Starting health check monitoring for target 65 (10.0.0.15:2283)
INFO: 2026/04/28 17:17:43 Started tcp proxy to client:3002
INFO: 2026/04/28 17:17:43 Started tcp proxy to vaultwarden:80
INFO: 2026/04/28 17:17:43 Started tcp proxy to searxng:8080
INFO: 2026/04/28 17:17:43 Started tcp proxy to 10.0.0.15:3923
WARN: 2026/04/28 17:17:43 Target 63: health check failed with status code 302
INFO: 2026/04/28 17:17:43 Target 63 initial status: unhealthy
INFO: 2026/04/28 17:17:43 Target 65 initial status: healthy
INFO: 2026/04/28 17:17:43 Target 43 initial status: healthy
INFO: 2026/04/28 17:17:43 Target 61 initial status: healthy
INFO: 2026/04/28 17:17:45 Client connectivity setup. Ready to accept connections from clients!
WARN: 2026/04/28 17:18:13 Target 63: health check failed with status code 302
INFO: 2026/04/28 17:18:14 Started tcp proxy to 10.0.0.15:8096
INFO: 2026/04/28 17:18:14 Replacing existing target with ID 63
INFO: 2026/04/28 17:18:14 Stopping health check monitoring for target 63
INFO: 2026/04/28 17:18:36 Started tcp proxy to 10.0.0.15:8096
INFO: 2026/04/28 17:18:36 Replacing existing target with ID 63
INFO: 2026/04/28 17:18:36 Starting monitoring for target 63 (10.0.0.15:8096)
INFO: 2026/04/28 17:18:36 Starting health check monitoring for target 63 (10.0.0.15:8096)
WARN: 2026/04/28 17:18:36 Target 63: health check failed with status code 302
INFO: 2026/04/28 17:18:36 Target 63 initial status: unhealthy
INFO: 2026/04/28 17:18:47 Started tcp proxy to 10.0.0.15:8096
INFO: 2026/04/28 17:18:47 Replacing existing target with ID 63
INFO: 2026/04/28 17:18:47 Stopping health check monitoring for target 63
INFO: 2026/04/28 17:19:51 Started tcp proxy to 10.0.0.15:8096
INFO: 2026/04/28 17:19:51 Replacing existing target with ID 63
INFO: 2026/04/28 17:19:51 Starting monitoring for target 63 (10.0.0.15:8096)
INFO: 2026/04/28 17:19:51 Starting health check monitoring for target 63 (10.0.0.15:8096)
WARN: 2026/04/28 17:19:51 Target 63: health check failed with status code 302
INFO: 2026/04/28 17:19:51 Target 63 initial status: unhealthy
WARN: 2026/04/28 17:20:21 Target 63: health check failed with status code 302
INFO: 2026/04/28 17:20:22 Started tcp proxy to 10.0.0.15:8096
INFO: 2026/04/28 17:20:22 Replacing existing target with ID 63
INFO: 2026/04/28 17:20:22 Stopping health check monitoring for target 63
Environment
OS Type & Version: Debian 13 Trixie
Pangolin Version: Self Hosted 1.17.1
Gerbil Version: 1.3.1
Traefik Version: v3.6.13
Newt Version: 1.12.0
To Reproduce
Self host server on version 1.17.1
Deploy Newt with 1.12.0 (docker)
Setup a health check to a public resource
Watch public resource drop when health check is enabled.
Expected Behavior
Health Checks should not cause public resources to stop working, This appears to be a regression from Newt 1.11.0
Originally created by @ljis120301 on GitHub (Apr 28, 2026).
Original GitHub issue: https://github.com/fosrl/newt/issues/332
### Describe the Bug
https://next.whoisjason.me/s/EPSrd9PJQPaQJMq
Whenever the "Health Check" is enabled for a public resource, it will cause that public resource to go offline.
This behavior happens with Server Version 1.17.1 + Newt 1.12.0 , Reverting to Newt 1.11.0 fixes this issue.
This is a copy of the logs while the preview video was running
```
INFO: 2026/04/28 17:16:59 Newt version 1.12.0
ERROR: 2026/04/28 17:17:09 Error checking for updates: failed to fetch release info: Get "https://api.github.com/repos/fosrl/newt/releases/latest": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
INFO: 2026/04/28 17:17:09 Config file does not exist at /root/.config/newt-client/config.json, will create it
ERROR: 2026/04/28 17:17:39 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.whoisjason.me/api/v1/auth/newt/get-token": context deadline exceeded. Retrying in 3s...
INFO: 2026/04/28 17:17:43 Server version: 1.17.1
INFO: 2026/04/28 17:17:43 Saving config to: /root/.config/newt-client/config.json
INFO: 2026/04/28 17:17:43 Websocket connected
INFO: 2026/04/28 17:17:43 Connecting to endpoint: pangolin.whoisjason.me
INFO: 2026/04/28 17:17:43 Tunnel connection to server established successfully!
INFO: 2026/04/28 17:17:43 Starting monitoring for target 43 (10.0.0.15:3923)
INFO: 2026/04/28 17:17:43 Starting monitoring for target 61 (10.0.0.15:9443)
INFO: 2026/04/28 17:17:43 Starting monitoring for target 63 (10.0.0.15:8096)
INFO: 2026/04/28 17:17:43 Starting monitoring for target 65 (10.0.0.15:2283)
INFO: 2026/04/28 17:17:43 Starting health check monitoring for target 43 (10.0.0.15:3923)
INFO: 2026/04/28 17:17:43 Starting health check monitoring for target 61 (10.0.0.15:9443)
INFO: 2026/04/28 17:17:43 Starting health check monitoring for target 63 (10.0.0.15:8096)
INFO: 2026/04/28 17:17:43 Started tcp proxy to 10.0.0.15:8096
INFO: 2026/04/28 17:17:43 Started tcp proxy to 10.0.0.15:2283
INFO: 2026/04/28 17:17:43 Started tcp proxy to backend:3001
INFO: 2026/04/28 17:17:43 Started tcp proxy to invidious:3000
INFO: 2026/04/28 17:17:43 Started tcp proxy to 10.0.0.15:9443
INFO: 2026/04/28 17:17:43 Starting health check monitoring for target 65 (10.0.0.15:2283)
INFO: 2026/04/28 17:17:43 Started tcp proxy to client:3002
INFO: 2026/04/28 17:17:43 Started tcp proxy to vaultwarden:80
INFO: 2026/04/28 17:17:43 Started tcp proxy to searxng:8080
INFO: 2026/04/28 17:17:43 Started tcp proxy to 10.0.0.15:3923
WARN: 2026/04/28 17:17:43 Target 63: health check failed with status code 302
INFO: 2026/04/28 17:17:43 Target 63 initial status: unhealthy
INFO: 2026/04/28 17:17:43 Target 65 initial status: healthy
INFO: 2026/04/28 17:17:43 Target 43 initial status: healthy
INFO: 2026/04/28 17:17:43 Target 61 initial status: healthy
INFO: 2026/04/28 17:17:45 Client connectivity setup. Ready to accept connections from clients!
WARN: 2026/04/28 17:18:13 Target 63: health check failed with status code 302
INFO: 2026/04/28 17:18:14 Started tcp proxy to 10.0.0.15:8096
INFO: 2026/04/28 17:18:14 Replacing existing target with ID 63
INFO: 2026/04/28 17:18:14 Stopping health check monitoring for target 63
INFO: 2026/04/28 17:18:36 Started tcp proxy to 10.0.0.15:8096
INFO: 2026/04/28 17:18:36 Replacing existing target with ID 63
INFO: 2026/04/28 17:18:36 Starting monitoring for target 63 (10.0.0.15:8096)
INFO: 2026/04/28 17:18:36 Starting health check monitoring for target 63 (10.0.0.15:8096)
WARN: 2026/04/28 17:18:36 Target 63: health check failed with status code 302
INFO: 2026/04/28 17:18:36 Target 63 initial status: unhealthy
INFO: 2026/04/28 17:18:47 Started tcp proxy to 10.0.0.15:8096
INFO: 2026/04/28 17:18:47 Replacing existing target with ID 63
INFO: 2026/04/28 17:18:47 Stopping health check monitoring for target 63
INFO: 2026/04/28 17:19:51 Started tcp proxy to 10.0.0.15:8096
INFO: 2026/04/28 17:19:51 Replacing existing target with ID 63
INFO: 2026/04/28 17:19:51 Starting monitoring for target 63 (10.0.0.15:8096)
INFO: 2026/04/28 17:19:51 Starting health check monitoring for target 63 (10.0.0.15:8096)
WARN: 2026/04/28 17:19:51 Target 63: health check failed with status code 302
INFO: 2026/04/28 17:19:51 Target 63 initial status: unhealthy
WARN: 2026/04/28 17:20:21 Target 63: health check failed with status code 302
INFO: 2026/04/28 17:20:22 Started tcp proxy to 10.0.0.15:8096
INFO: 2026/04/28 17:20:22 Replacing existing target with ID 63
INFO: 2026/04/28 17:20:22 Stopping health check monitoring for target 63
```
### Environment
- OS Type & Version: Debian 13 Trixie
- Pangolin Version: Self Hosted 1.17.1
- Gerbil Version: 1.3.1
- Traefik Version: v3.6.13
- Newt Version: 1.12.0
### To Reproduce
1. Self host server on version 1.17.1
2. Deploy Newt with 1.12.0 (docker)
3. Setup a health check to a public resource
4. Watch public resource drop when health check is enabled.
### Expected Behavior
Health Checks should not cause public resources to stop working, This appears to be a regression from Newt 1.11.0
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 @ljis120301 on GitHub (Apr 28, 2026).
Original GitHub issue: https://github.com/fosrl/newt/issues/332
Describe the Bug
https://next.whoisjason.me/s/EPSrd9PJQPaQJMq
Whenever the "Health Check" is enabled for a public resource, it will cause that public resource to go offline.
This behavior happens with Server Version 1.17.1 + Newt 1.12.0 , Reverting to Newt 1.11.0 fixes this issue.
This is a copy of the logs while the preview video was running
Environment
To Reproduce
Expected Behavior
Health Checks should not cause public resources to stop working, This appears to be a regression from Newt 1.11.0
@ljis120301 commented on GitHub (Apr 28, 2026):
Issue has been Resolved in Newt 1.12.1
@oschwartz10612 commented on GitHub (Apr 28, 2026):
Great! Thanks for letting us know.