Originally created by @Ejmathewp on GitHub (Jul 3, 2025).
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).
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.
@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.
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).
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!