Since last week, Newt is starting to fail on Docker for Windows. My newt instance in Linux is still working fine. I've recreated the container with no change in behavior.
This causes issues with accessing my resources, it's not just the health checks. All resources are timing out every few seconds, making it impossible to use them.
INFO: 2026/02/06 18:05:23 Target 14 status changed: healthy -> unhealthy
INFO: 2026/02/06 18:05:53 Target 13 status changed: unhealthy -> healthy
INFO: 2026/02/06 18:05:53 Target 6 status changed: unhealthy -> healthy
INFO: 2026/02/06 18:05:53 Target 24 status changed: unhealthy -> healthy
INFO: 2026/02/06 18:05:53 Target 9 status changed: unhealthy -> healthy
INFO: 2026/02/06 18:05:53 Target 14 status changed: unhealthy -> healthy
INFO: 2026/02/06 18:05:55 Target 23 status changed: unhealthy -> healthy
OS Type & Version: Ubuntu 24.04.3 for Pangolin and Windows Server 2025 for Newt client experiencing issues
Pangolin Version: 1.15.2
Gerbil Version: 1.3.0
Traefik Version: 3.6.7
Newt Version: 1.9.0
To Reproduce
Recreating the containers makes no changes (both newt and pangolin).
Same timeouts without health checks enabled, just not measurable as I can still ping it consistently its just giving me errors such that it can't fully resolve the page/freezes when loading.
Expected Behavior
Newt remains consistent.
Originally created by @Viceman256 on GitHub (Feb 6, 2026).
Original GitHub issue: https://github.com/fosrl/newt/issues/244
### Describe the Bug
Since last week, Newt is starting to fail on Docker for Windows. My newt instance in Linux is still working fine. I've recreated the container with no change in behavior.
This causes issues with accessing my resources, it's not just the health checks. All resources are timing out every few seconds, making it impossible to use them.
INFO: 2026/02/06 18:05:23 Target 14 status changed: healthy -> unhealthy
INFO: 2026/02/06 18:05:53 Target 13 status changed: unhealthy -> healthy
INFO: 2026/02/06 18:05:53 Target 6 status changed: unhealthy -> healthy
INFO: 2026/02/06 18:05:53 Target 24 status changed: unhealthy -> healthy
INFO: 2026/02/06 18:05:53 Target 9 status changed: unhealthy -> healthy
INFO: 2026/02/06 18:05:53 Target 14 status changed: unhealthy -> healthy
INFO: 2026/02/06 18:05:55 Target 23 status changed: unhealthy -> healthy
WARN: 2026/02/06 18:06:15 Target 23: health check failed: Get "http://host.docker.internal:4533/": context deadline exceeded
INFO: 2026/02/06 18:06:15 Target 23 status changed: healthy -> unhealthy
WARN: 2026/02/06 18:06:18 Target 13: health check failed: Get "http://host.docker.internal:2283/": context deadline exceeded
INFO: 2026/02/06 18:06:18 Target 13 status changed: healthy -> unhealthy
WARN: 2026/02/06 18:06:18 Target 6: health check failed: Get "http://host.docker.internal:8096/": context deadline exceeded
INFO: 2026/02/06 18:06:18 Target 6 status changed: healthy -> unhealthy
WARN: 2026/02/06 18:06:18 Target 24: health check failed: Get "http://host.docker.internal:8015/": context deadline exceeded
INFO: 2026/02/06 18:06:18 Target 24 status changed: healthy -> unhealthy
WARN: 2026/02/06 18:06:18 Target 9: health check failed: Get "http://host.docker.internal:3011/": context deadline exceeded
INFO: 2026/02/06 18:06:18 Target 9 status changed: healthy -> unhealthy
WARN: 2026/02/06 18:06:18 Target 14: health check failed: Get "http://host.docker.internal:5055/": context deadline exceeded
INFO: 2026/02/06 18:06:18 Target 14 status changed: healthy -> unhealthy
services:
newt:
image: fosrl/newt
container_name: newt
restart: unless-stopped
environment:
### Environment
- OS Type & Version: Ubuntu 24.04.3 for Pangolin and Windows Server 2025 for Newt client experiencing issues
- Pangolin Version: 1.15.2
- Gerbil Version: 1.3.0
- Traefik Version: 3.6.7
- Newt Version: 1.9.0
### To Reproduce
Recreating the containers makes no changes (both newt and pangolin).
Same timeouts without health checks enabled, just not measurable as I can still ping it consistently its just giving me errors such that it can't fully resolve the page/freezes when loading.
### Expected Behavior
Newt remains consistent.
GiteaMirror
added the bug label 2026-04-12 06:38:06 -05:00
Same issue for me. Tried to find some info in the debug logs but they've not really been helpful.
I tried to narrow down when this happens as it was running without issues (or without me noticing) for a while. It looks like the issue only starts to appear once I've got 5+ health checks enabled. If I enable 6 it starts to appear every couple of checks, and with every other enabled health check the frequency increases.
Another thing I've noticed, since I enabled/disabled health checks a few times, sometimes a disabled a check gets re-enabled by itself instantly.
Feb 09 20:31:30 newt-01 newt[8368]: INFO: 2026/02/09 20:31:30 Stopping health check monitoring for target 1
Feb 09 20:31:30 newt-01 newt[8368]: INFO: 2026/02/09 20:31:30 Starting health check monitoring for target 1 (cloud01.mydomain.com:443)
<!-- gh-comment-id:3961688146 -->
@StillLoading commented on GitHub (Feb 9, 2026):
Same issue for me. Tried to find some info in the debug logs but they've not really been helpful.
I tried to narrow down when this happens as it was running without issues (or without me noticing) for a while. It looks like the issue only starts to appear once I've got 5+ health checks enabled. If I enable 6 it starts to appear every couple of checks, and with every other enabled health check the frequency increases.
Another thing I've noticed, since I enabled/disabled health checks a few times, sometimes a disabled a check gets re-enabled by itself instantly.
```
Feb 09 20:31:30 newt-01 newt[8368]: INFO: 2026/02/09 20:31:30 Stopping health check monitoring for target 1
Feb 09 20:31:30 newt-01 newt[8368]: INFO: 2026/02/09 20:31:30 Starting health check monitoring for target 1 (cloud01.mydomain.com:443)
```
@github-actions[bot] commented on GitHub (Feb 24, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
<!-- gh-comment-id:3961688168 -->
@github-actions[bot] commented on GitHub (Feb 24, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
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 @Viceman256 on GitHub (Feb 6, 2026).
Original GitHub issue: https://github.com/fosrl/newt/issues/244
Describe the Bug
Since last week, Newt is starting to fail on Docker for Windows. My newt instance in Linux is still working fine. I've recreated the container with no change in behavior.
This causes issues with accessing my resources, it's not just the health checks. All resources are timing out every few seconds, making it impossible to use them.
INFO: 2026/02/06 18:05:23 Target 14 status changed: healthy -> unhealthy
INFO: 2026/02/06 18:05:53 Target 13 status changed: unhealthy -> healthy
INFO: 2026/02/06 18:05:53 Target 6 status changed: unhealthy -> healthy
INFO: 2026/02/06 18:05:53 Target 24 status changed: unhealthy -> healthy
INFO: 2026/02/06 18:05:53 Target 9 status changed: unhealthy -> healthy
INFO: 2026/02/06 18:05:53 Target 14 status changed: unhealthy -> healthy
INFO: 2026/02/06 18:05:55 Target 23 status changed: unhealthy -> healthy
WARN: 2026/02/06 18:06:15 Target 23: health check failed: Get "http://host.docker.internal:4533/": context deadline exceeded
INFO: 2026/02/06 18:06:15 Target 23 status changed: healthy -> unhealthy
WARN: 2026/02/06 18:06:18 Target 13: health check failed: Get "http://host.docker.internal:2283/": context deadline exceeded
INFO: 2026/02/06 18:06:18 Target 13 status changed: healthy -> unhealthy
WARN: 2026/02/06 18:06:18 Target 6: health check failed: Get "http://host.docker.internal:8096/": context deadline exceeded
INFO: 2026/02/06 18:06:18 Target 6 status changed: healthy -> unhealthy
WARN: 2026/02/06 18:06:18 Target 24: health check failed: Get "http://host.docker.internal:8015/": context deadline exceeded
INFO: 2026/02/06 18:06:18 Target 24 status changed: healthy -> unhealthy
WARN: 2026/02/06 18:06:18 Target 9: health check failed: Get "http://host.docker.internal:3011/": context deadline exceeded
INFO: 2026/02/06 18:06:18 Target 9 status changed: healthy -> unhealthy
WARN: 2026/02/06 18:06:18 Target 14: health check failed: Get "http://host.docker.internal:5055/": context deadline exceeded
INFO: 2026/02/06 18:06:18 Target 14 status changed: healthy -> unhealthy
services:
newt:
image: fosrl/newt
container_name: newt
restart: unless-stopped
environment:
Environment
To Reproduce
Recreating the containers makes no changes (both newt and pangolin).
Same timeouts without health checks enabled, just not measurable as I can still ping it consistently its just giving me errors such that it can't fully resolve the page/freezes when loading.
Expected Behavior
Newt remains consistent.
@StillLoading commented on GitHub (Feb 9, 2026):
Same issue for me. Tried to find some info in the debug logs but they've not really been helpful.
I tried to narrow down when this happens as it was running without issues (or without me noticing) for a while. It looks like the issue only starts to appear once I've got 5+ health checks enabled. If I enable 6 it starts to appear every couple of checks, and with every other enabled health check the frequency increases.
Another thing I've noticed, since I enabled/disabled health checks a few times, sometimes a disabled a check gets re-enabled by itself instantly.
@github-actions[bot] commented on GitHub (Feb 24, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.