Originally assigned to: @oschwartz10612 on GitHub.
Newt keeps losing the connection to my VPS. I run newt as a binary and systemd service. It appears to happen quite randomly maybe once a day. It's not always at the same time. As soon as I run systemctl restart newt.service it works again.
Here are logs of newt.service:
Jun 03 22:17:02 newt newt[145]: INFO: 2025/06/03 22:17:02 Ping latency: 21.506204ms
Jun 03 22:17:32 newt newt[145]: INFO: 2025/06/03 22:17:32 Pinging 100.xx.xx.x
Jun 03 22:17:42 newt newt[145]: WARN: 2025/06/03 22:17:42 Connection to server lost. Continuous reconnection attempts will be made.
Jun 03 22:17:42 newt newt[145]: WARN: 2025/06/03 22:17:42 Please check your internet connection and ensure the Pangolin server is online.
Jun 03 22:17:42 newt newt[145]: WARN: 2025/06/03 22:17:42 Newt will continue reconnection attempts automatically when connectivity is restored.
Jun 03 22:18:02 newt newt[145]: INFO: 2025/06/03 22:18:02 Pinging 100.xx.xxx.x
Jun 03 22:18:32 newt newt[145]: INFO: 2025/06/03 22:18:32 Pinging 100.xx.xxx.x
Jun 03 22:19:02 newt newt[145]: INFO: 2025/06/03 22:19:02 Pinging 100.xx.xxx.x
Jun 03 22:32:19 newt systemd[1]: Stopping newt.service - Newt VPN Client...
Jun 03 22:32:19 newt systemd[1]: newt.service: Deactivated successfully.
Jun 03 22:32:19 newt systemd[1]: Stopped newt.service - Newt VPN Client.
Jun 03 22:32:19 newt systemd[1]: newt.service: Consumed 34.187s CPU time.
Jun 03 22:32:19 newt systemd[1]: Started newt.service - Newt VPN Client.
Jun 03 22:32:20 newt newt[756]: INFO: 2025/06/03 22:32:20 Sent registration message
Jun 03 22:32:20 newt newt[756]: INFO: 2025/06/03 22:32:20 Received registration message
Jun 03 22:32:20 newt newt[756]: INFO: 2025/06/03 22:32:20 Received: {Type:newt/wg/connect Data:map[endpoint:pangolin.example.com:51820 publicKey:xxxxx>
Jun 03 22:32:20 newt newt[756]: INFO: 2025/06/03 22:32:20 WireGuard device created. Lets ping the server now...
Jun 03 22:32:20 newt newt[756]: INFO: 2025/06/03 22:32:20 Ping attempt 1
Jun 03 22:32:20 newt newt[756]: INFO: 2025/06/03 22:32:20 Pinging 100.xx.xxx.x
Jun 03 22:32:20 newt newt[756]: INFO: 2025/06/03 22:32:20 Ping latency: 32.849913ms
Jun 03 22:32:20 newt newt[756]: INFO: 2025/06/03 22:32:20 Starting ping check
Jun 03 22:32:20 newt newt[756]: INFO: 2025/06/03 22:32:20 Started tcp proxy from 100.xx.xxx.x:xxxxx to 192.168.178.114:xxxx
Originally created by @johanngrobe on GitHub (Jun 3, 2025).
Original GitHub issue: https://github.com/fosrl/newt/issues/51
Originally assigned to: @oschwartz10612 on GitHub.
Newt keeps losing the connection to my VPS. I run newt as a binary and systemd service. It appears to happen quite randomly maybe once a day. It's not always at the same time. As soon as I run `systemctl restart newt.service` it works again.
Here are logs of `newt.service`:
```
Jun 03 22:17:02 newt newt[145]: INFO: 2025/06/03 22:17:02 Ping latency: 21.506204ms
Jun 03 22:17:32 newt newt[145]: INFO: 2025/06/03 22:17:32 Pinging 100.xx.xx.x
Jun 03 22:17:42 newt newt[145]: WARN: 2025/06/03 22:17:42 Connection to server lost. Continuous reconnection attempts will be made.
Jun 03 22:17:42 newt newt[145]: WARN: 2025/06/03 22:17:42 Please check your internet connection and ensure the Pangolin server is online.
Jun 03 22:17:42 newt newt[145]: WARN: 2025/06/03 22:17:42 Newt will continue reconnection attempts automatically when connectivity is restored.
Jun 03 22:18:02 newt newt[145]: INFO: 2025/06/03 22:18:02 Pinging 100.xx.xxx.x
Jun 03 22:18:32 newt newt[145]: INFO: 2025/06/03 22:18:32 Pinging 100.xx.xxx.x
Jun 03 22:19:02 newt newt[145]: INFO: 2025/06/03 22:19:02 Pinging 100.xx.xxx.x
Jun 03 22:32:19 newt systemd[1]: Stopping newt.service - Newt VPN Client...
Jun 03 22:32:19 newt systemd[1]: newt.service: Deactivated successfully.
Jun 03 22:32:19 newt systemd[1]: Stopped newt.service - Newt VPN Client.
Jun 03 22:32:19 newt systemd[1]: newt.service: Consumed 34.187s CPU time.
Jun 03 22:32:19 newt systemd[1]: Started newt.service - Newt VPN Client.
Jun 03 22:32:20 newt newt[756]: INFO: 2025/06/03 22:32:20 Sent registration message
Jun 03 22:32:20 newt newt[756]: INFO: 2025/06/03 22:32:20 Received registration message
Jun 03 22:32:20 newt newt[756]: INFO: 2025/06/03 22:32:20 Received: {Type:newt/wg/connect Data:map[endpoint:pangolin.example.com:51820 publicKey:xxxxx>
Jun 03 22:32:20 newt newt[756]: INFO: 2025/06/03 22:32:20 WireGuard device created. Lets ping the server now...
Jun 03 22:32:20 newt newt[756]: INFO: 2025/06/03 22:32:20 Ping attempt 1
Jun 03 22:32:20 newt newt[756]: INFO: 2025/06/03 22:32:20 Pinging 100.xx.xxx.x
Jun 03 22:32:20 newt newt[756]: INFO: 2025/06/03 22:32:20 Ping latency: 32.849913ms
Jun 03 22:32:20 newt newt[756]: INFO: 2025/06/03 22:32:20 Starting ping check
Jun 03 22:32:20 newt newt[756]: INFO: 2025/06/03 22:32:20 Started tcp proxy from 100.xx.xxx.x:xxxxx to 192.168.178.114:xxxx
```
GiteaMirror
added the bug label 2026-04-12 06:35:32 -05:00
As a temporary fix I have set up a newt monitor script. It monitors newt's logs and restarts newt whenever it loses the connection.
<!-- gh-comment-id:2944253726 -->
@johanngrobe commented on GitHub (Jun 5, 2025):
As a temporary fix I have set up a newt monitor script. It monitors newt's logs and restarts newt whenever it loses the connection.
I have the same issue. Sadly I restarted the systemd service before discovering this issue.
Since this happens every once in a while I will try to get you some more logs, which might help
<!-- gh-comment-id:3004220207 -->
@elmoritz commented on GitHub (Jun 25, 2025):
I have the same issue. Sadly I restarted the systemd service before discovering this issue.
Since this happens every once in a while I will try to get you some more logs, which might help
@oschwartz10612 commented on GitHub (Jun 25, 2025):
Thanks! Been doing some improvements and the next newt release should have some better down detection and recovery!
<!-- gh-comment-id:3005118542 -->
@oschwartz10612 commented on GitHub (Jun 25, 2025):
Thanks! Been doing some improvements and the next newt release should have some better down detection and recovery!
Thank you very much.
Could not manage to get the logs, since it did not happen again.
But updating all my machines now.
<!-- gh-comment-id:3068066276 -->
@elmoritz commented on GitHub (Jul 14, 2025):
Thank you very much.
Could not manage to get the logs, since it did not happen again.
But updating all my machines now.
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 @johanngrobe on GitHub (Jun 3, 2025).
Original GitHub issue: https://github.com/fosrl/newt/issues/51
Originally assigned to: @oschwartz10612 on GitHub.
Newt keeps losing the connection to my VPS. I run newt as a binary and systemd service. It appears to happen quite randomly maybe once a day. It's not always at the same time. As soon as I run
systemctl restart newt.serviceit works again.Here are logs of
newt.service:@ghost commented on GitHub (Jun 3, 2025):
Same thing.
Linux loses connection after reboot
@johanngrobe commented on GitHub (Jun 5, 2025):
As a temporary fix I have set up a newt monitor script. It monitors newt's logs and restarts newt whenever it loses the connection.
@oschwartz10612 commented on GitHub (Jun 6, 2025):
I will look into it.
@elmoritz commented on GitHub (Jun 25, 2025):
I have the same issue. Sadly I restarted the systemd service before discovering this issue.
Since this happens every once in a while I will try to get you some more logs, which might help
@oschwartz10612 commented on GitHub (Jun 25, 2025):
Thanks! Been doing some improvements and the next newt release should have some better down detection and recovery!
@elmoritz commented on GitHub (Jul 14, 2025):
Thank you very much.
Could not manage to get the logs, since it did not happen again.
But updating all my machines now.