github-starred/newt
2
0
Fork 0
mirror of https://github.com/fosrl/newt.git synced 2026-03-09 07:12:28 -05:00
Code Issues 21 Packages Projects Releases 25 Wiki Activity

newt loses the connection #31

New Issue
Closed
opened 2025-11-19 07:12:26 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-19 07:12:26 -06:00
Owner
Copy Link

Originally created by @johanngrobe on GitHub (Jun 3, 2025).

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). 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 2025-11-19 07:12:26 -06:00
GiteaMirror commented 2025-11-19 07:12:27 -06:00
Author
Owner
Copy Link

@tomatomonster69 commented on GitHub (Jun 3, 2025):

Same thing.
Linux loses connection after reboot

@tomatomonster69 commented on GitHub (Jun 3, 2025): Same thing. Linux loses connection after reboot
GiteaMirror commented 2025-11-19 07:12:27 -06:00
Author
Owner
Copy Link

@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.

@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.
GiteaMirror commented 2025-11-19 07:12:28 -06:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Jun 6, 2025):

I will look into it.

@oschwartz10612 commented on GitHub (Jun 6, 2025): I will look into it.
GiteaMirror commented 2025-11-19 07:12:28 -06:00
Author
Owner
Copy Link

@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

@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
GiteaMirror commented 2025-11-19 07:12:28 -06:00
Author
Owner
Copy Link

@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!

@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!
GiteaMirror commented 2025-11-19 07:12:28 -06:00
Author
Owner
Copy Link

@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.

@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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
good first issue
help wanted
Improvement
pull-request
Mirrored from GitHub Pull Request
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/newt#31
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?