I am running Newt on a TrueNAS server, I have tried both through the app catalog as well as regular docker deployment and encounter this issue with either approach. At least once a day Newt will report:
newt | INFO: 2025/07/02 14:27:32 Pinging [ip redacted]
newt | INFO: 2025/07/02 14:27:33 Ping latency: 142.385859ms
newt | INFO: 2025/07/02 14:28:02 Pinging [ip redacted]
newt | WARN: 2025/07/02 14:28:12 Connection to server lost. Continuous reconnection attempts will be made.
newt | WARN: 2025/07/02 14:28:12 Please check your internet connection and ensure the Pangolin server is online.
newt | WARN: 2025/07/02 14:28:12 Newt will continue reconnection attempts automatically when connectivity is restored.
newt | INFO: 2025/07/02 14:28:32 Pinging [ip redacted]
newt | INFO: 2025/07/02 14:29:02 Pinging [ip redacted]
newt | INFO: 2025/07/02 14:29:32 Pinging [ip redacted]
newt | INFO: 2025/07/02 14:30:02 Pinging [ip redacted]
newt | INFO: 2025/07/02 14:30:32 Pinging [ip redacted]
A connection is never re-established, but if I restart the container there is zero issue reconnecting.
The drop is not at a consistent time and there are no connection issues with any other services.
Originally created by @Ejmathewp on GitHub (Jul 3, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1004
I am running Newt on a TrueNAS server, I have tried both through the app catalog as well as regular docker deployment and encounter this issue with either approach. At least once a day Newt will report:
```
newt | INFO: 2025/07/02 14:27:32 Pinging [ip redacted]
newt | INFO: 2025/07/02 14:27:33 Ping latency: 142.385859ms
newt | INFO: 2025/07/02 14:28:02 Pinging [ip redacted]
newt | WARN: 2025/07/02 14:28:12 Connection to server lost. Continuous reconnection attempts will be made.
newt | WARN: 2025/07/02 14:28:12 Please check your internet connection and ensure the Pangolin server is online.
newt | WARN: 2025/07/02 14:28:12 Newt will continue reconnection attempts automatically when connectivity is restored.
newt | INFO: 2025/07/02 14:28:32 Pinging [ip redacted]
newt | INFO: 2025/07/02 14:29:02 Pinging [ip redacted]
newt | INFO: 2025/07/02 14:29:32 Pinging [ip redacted]
newt | INFO: 2025/07/02 14:30:02 Pinging [ip redacted]
newt | INFO: 2025/07/02 14:30:32 Pinging [ip redacted]
```
A connection is never re-established, but if I restart the container there is zero issue reconnecting.
The drop is not at a consistent time and there are no connection issues with any other services.
@github-actions[bot] commented on GitHub (Jul 18, 2025):
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:3086063465 -->
@github-actions[bot] commented on GitHub (Jul 18, 2025):
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.
I have a similar issue. If I loose WAN connectivity or WAN IP changes I need to restart newt manually. After newt restart everything start working instantly.
Mar 26 11:30:39 access newt[358]: WARN: 2026/03/26 11:30:39 Periodic ping failed (169 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
Mar 26 11:31:42 access newt[358]: WARN: 2026/03/26 11:31:42 Periodic ping failed (170 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
Mar 26 11:32:46 access newt[358]: WARN: 2026/03/26 11:32:46 Periodic ping failed (171 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
Mar 26 11:33:49 access newt[358]: WARN: 2026/03/26 11:33:49 Periodic ping failed (172 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
Mar 26 11:34:53 access newt[358]: WARN: 2026/03/26 11:34:53 Periodic ping failed (173 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
Mar 26 11:35:56 access newt[358]: WARN: 2026/03/26 11:35:56 Periodic ping failed (174 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
Mar 26 11:37:00 access newt[358]: WARN: 2026/03/26 11:37:00 Periodic ping failed (175 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
Mar 26 11:38:03 access newt[358]: WARN: 2026/03/26 11:38:03 Periodic ping failed (176 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
Mar 26 11:39:07 access newt[358]: WARN: 2026/03/26 11:39:07 Periodic ping failed (177 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
Mar 26 11:40:10 access newt[358]: WARN: 2026/03/26 11:40:10 Periodic ping failed (178 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
<!-- gh-comment-id:4133941133 -->
@sandroshu commented on GitHub (Mar 26, 2026):
I have a similar issue. If I loose WAN connectivity or WAN IP changes I need to restart newt manually. After newt restart everything start working instantly.
```
Mar 26 11:30:39 access newt[358]: WARN: 2026/03/26 11:30:39 Periodic ping failed (169 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
Mar 26 11:31:42 access newt[358]: WARN: 2026/03/26 11:31:42 Periodic ping failed (170 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
Mar 26 11:32:46 access newt[358]: WARN: 2026/03/26 11:32:46 Periodic ping failed (171 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
Mar 26 11:33:49 access newt[358]: WARN: 2026/03/26 11:33:49 Periodic ping failed (172 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
Mar 26 11:34:53 access newt[358]: WARN: 2026/03/26 11:34:53 Periodic ping failed (173 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
Mar 26 11:35:56 access newt[358]: WARN: 2026/03/26 11:35:56 Periodic ping failed (174 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
Mar 26 11:37:00 access newt[358]: WARN: 2026/03/26 11:37:00 Periodic ping failed (175 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
Mar 26 11:38:03 access newt[358]: WARN: 2026/03/26 11:38:03 Periodic ping failed (176 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
Mar 26 11:39:07 access newt[358]: WARN: 2026/03/26 11:39:07 Periodic ping failed (177 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
Mar 26 11:40:10 access newt[358]: WARN: 2026/03/26 11:40:10 Periodic ping failed (178 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
```
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 @Ejmathewp on GitHub (Jul 3, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1004
I am running Newt on a TrueNAS server, I have tried both through the app catalog as well as regular docker deployment and encounter this issue with either approach. At least once a day Newt will report:
A connection is never re-established, but if I restart the container there is zero issue reconnecting.
The drop is not at a consistent time and there are no connection issues with any other services.
@oschwartz10612 commented on GitHub (Jul 3, 2025):
Should be fixed in the next newt release!
@Ejmathewp commented on GitHub (Jul 3, 2025):
Perfect, thanks!
@github-actions[bot] commented on GitHub (Jul 18, 2025):
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.
@oschwartz10612 commented on GitHub (Jul 18, 2025):
Try the latest newt release and Pangolin!
@sandroshu commented on GitHub (Mar 26, 2026):
I have a similar issue. If I loose WAN connectivity or WAN IP changes I need to restart newt manually. After newt restart everything start working instantly.