github-starred/newt
2
0
Fork 0
mirror of https://github.com/fosrl/newt.git synced 2026-11-11 16:33:24 -06:00
Code Issues 713 Packages Projects Releases 47 Wiki Activity

Newt intermittently loses connection to Pangolin server and reconnects automatically #28

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

Originally created by @ApfelQrown on GitHub (May 28, 2025).

Setup

  • Pangolin is running on a VPS with static IPv4 and IPv6 addresses.
  • Domain mydomain.tld is managed via Cloudflare, with pangolin.mydomain.tld pointing to the VPS.
  • Newt runs at home inside a Proxmox VM (Ubuntu Server 24.04) as a Docker container.

In the logs, Newt periodically disconnects from the Pangolin server. It does automatically reconnect shortly after. Here's a sample from the logs showing this behavior.

Is this expected? Could this indicate a network or configuration issue on my end?

Newt Docker Compose file:

name: "newt"

networks:
  newt:
    external: true

services:
  newt:
    container_name: "newt"
    image: "docker.io/fosrl/newt:1.1.3"
    restart: unless-stopped
    env_file:
      - ".env"
    networks:
      newt: {}

Newt Logs:

INFO: 2025/05/27 23:42:24 Pinging 100.89.128.1
INFO: 2025/05/27 23:42:24 Ping latency: 21.969615ms
INFO: 2025/05/27 23:42:54 Pinging 100.89.128.1
WARN: 2025/05/27 23:43:04 Connection to server lost. Continuous reconnection attempts will be made.
WARN: 2025/05/27 23:43:04 Please check your internet connection and ensure the Pangolin server is online.
WARN: 2025/05/27 23:43:04 Newt will continue reconnection attempts automatically when connectivity is restored.
INFO: 2025/05/27 23:43:24 Pinging 100.89.128.1
INFO: 2025/05/27 23:43:24 Ping latency: 17.998683ms
INFO: 2025/05/27 23:43:24 Connection to server restored!
INFO: 2025/05/27 23:43:24 Successfully re-registered with server after reconnection
INFO: 2025/05/27 23:43:24 Received registration message
INFO: 2025/05/27 23:43:24 Already connected! But I will send a ping anyway...
INFO: 2025/05/27 23:43:24 Ping attempt 1
INFO: 2025/05/27 23:43:24 Pinging 100.89.128.1
INFO: 2025/05/27 23:43:24 Ping latency: 17.679649ms
INFO: 2025/05/27 23:43:54 Pinging 100.89.128.1
INFO: 2025/05/27 23:43:54 Ping latency: 18.940741ms
INFO: 2025/05/27 23:44:24 Pinging 100.89.128.1
INFO: 2025/05/27 23:44:24 Ping latency: 18.442843ms
INFO: 2025/05/27 23:44:54 Pinging 100.89.128.1
INFO: 2025/05/27 23:44:54 Ping latency: 19.043123ms
INFO: 2025/05/27 23:45:24 Pinging 100.89.128.1
INFO: 2025/05/27 23:45:24 Ping latency: 18.027703ms
INFO: 2025/05/27 23:45:54 Pinging 100.89.128.1
WARN: 2025/05/27 23:46:04 Connection to server lost. Continuous reconnection attempts will be made.
WARN: 2025/05/27 23:46:04 Please check your internet connection and ensure the Pangolin server is online.
WARN: 2025/05/27 23:46:04 Newt will continue reconnection attempts automatically when connectivity is restored.
INFO: 2025/05/27 23:46:24 Pinging 100.89.128.1
INFO: 2025/05/27 23:46:24 Ping latency: 18.590735ms
INFO: 2025/05/27 23:46:24 Connection to server restored!
INFO: 2025/05/27 23:46:24 Successfully re-registered with server after reconnection
INFO: 2025/05/27 23:46:24 Received registration message
INFO: 2025/05/27 23:46:24 Already connected! But I will send a ping anyway...
INFO: 2025/05/27 23:46:24 Ping attempt 1
INFO: 2025/05/27 23:46:24 Pinging 100.89.128.1
INFO: 2025/05/27 23:46:24 Ping latency: 18.264285ms
Originally created by @ApfelQrown on GitHub (May 28, 2025). # Setup - Pangolin is running on a VPS with static IPv4 and IPv6 addresses. - Domain mydomain.tld is managed via Cloudflare, with pangolin.mydomain.tld pointing to the VPS. - Newt runs at home inside a Proxmox VM (Ubuntu Server 24.04) as a Docker container. In the logs, Newt periodically disconnects from the Pangolin server. It does automatically reconnect shortly after. Here's a sample from the logs showing this behavior. Is this expected? Could this indicate a network or configuration issue on my end? **Newt Docker Compose file:** ```yaml name: "newt" networks: newt: external: true services: newt: container_name: "newt" image: "docker.io/fosrl/newt:1.1.3" restart: unless-stopped env_file: - ".env" networks: newt: {} ``` **Newt Logs:** ``` INFO: 2025/05/27 23:42:24 Pinging 100.89.128.1 INFO: 2025/05/27 23:42:24 Ping latency: 21.969615ms INFO: 2025/05/27 23:42:54 Pinging 100.89.128.1 WARN: 2025/05/27 23:43:04 Connection to server lost. Continuous reconnection attempts will be made. WARN: 2025/05/27 23:43:04 Please check your internet connection and ensure the Pangolin server is online. WARN: 2025/05/27 23:43:04 Newt will continue reconnection attempts automatically when connectivity is restored. INFO: 2025/05/27 23:43:24 Pinging 100.89.128.1 INFO: 2025/05/27 23:43:24 Ping latency: 17.998683ms INFO: 2025/05/27 23:43:24 Connection to server restored! INFO: 2025/05/27 23:43:24 Successfully re-registered with server after reconnection INFO: 2025/05/27 23:43:24 Received registration message INFO: 2025/05/27 23:43:24 Already connected! But I will send a ping anyway... INFO: 2025/05/27 23:43:24 Ping attempt 1 INFO: 2025/05/27 23:43:24 Pinging 100.89.128.1 INFO: 2025/05/27 23:43:24 Ping latency: 17.679649ms INFO: 2025/05/27 23:43:54 Pinging 100.89.128.1 INFO: 2025/05/27 23:43:54 Ping latency: 18.940741ms INFO: 2025/05/27 23:44:24 Pinging 100.89.128.1 INFO: 2025/05/27 23:44:24 Ping latency: 18.442843ms INFO: 2025/05/27 23:44:54 Pinging 100.89.128.1 INFO: 2025/05/27 23:44:54 Ping latency: 19.043123ms INFO: 2025/05/27 23:45:24 Pinging 100.89.128.1 INFO: 2025/05/27 23:45:24 Ping latency: 18.027703ms INFO: 2025/05/27 23:45:54 Pinging 100.89.128.1 WARN: 2025/05/27 23:46:04 Connection to server lost. Continuous reconnection attempts will be made. WARN: 2025/05/27 23:46:04 Please check your internet connection and ensure the Pangolin server is online. WARN: 2025/05/27 23:46:04 Newt will continue reconnection attempts automatically when connectivity is restored. INFO: 2025/05/27 23:46:24 Pinging 100.89.128.1 INFO: 2025/05/27 23:46:24 Ping latency: 18.590735ms INFO: 2025/05/27 23:46:24 Connection to server restored! INFO: 2025/05/27 23:46:24 Successfully re-registered with server after reconnection INFO: 2025/05/27 23:46:24 Received registration message INFO: 2025/05/27 23:46:24 Already connected! But I will send a ping anyway... INFO: 2025/05/27 23:46:24 Ping attempt 1 INFO: 2025/05/27 23:46:24 Pinging 100.89.128.1 INFO: 2025/05/27 23:46:24 Ping latency: 18.264285ms ```
GiteaMirror commented 2025-11-19 07:12:22 -06:00
Author
Owner
Copy Link
Copy Source

@oschwartz10612 commented on GitHub (May 29, 2025):

Hi!

While it always could be the code I have not see existing reports of this unless something external happens like the VPS goes down or something. I would be thinking about your network and the connectivity to the VPS or the VPS itself. Maybe you could set up a ping test or something manually to ping the VPS and see if connectivity lapses during these outage events? If not, let me know!

@oschwartz10612 commented on GitHub (May 29, 2025): Hi! While it always could be the code I have not see existing reports of this unless something external happens like the VPS goes down or something. I would be thinking about your network and the connectivity to the VPS or the VPS itself. Maybe you could set up a ping test or something manually to ping the VPS and see if connectivity lapses during these outage events? If not, let me know!
GiteaMirror commented 2025-11-19 07:12:22 -06:00
Author
Owner
Copy Link
Copy Source

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

Hi,
Thank you for the reply.
I found my problem. I have pretty severe packet loss within my home network. Atleast the ping command has arround 10% - 20% packet loss. When I use speed tests like this: https://speed.cloudflare.com/ I have a reported packet loss of 0%...
I have a WLAN bridge between the server and my router. With a temporary Ethernet Cable I do not have the packet loss problem.
I will investigate it further, but that has nothing to do with newt.

Sorry for the "false" report.

@ApfelQrown commented on GitHub (Jun 3, 2025): Hi, Thank you for the reply. I found my problem. I have pretty severe packet loss within my home network. Atleast the ping command has arround 10% - 20% packet loss. When I use speed tests like this: https://speed.cloudflare.com/ I have a reported packet loss of 0%... I have a WLAN bridge between the server and my router. With a temporary Ethernet Cable I do not have the packet loss problem. I will investigate it further, but that has nothing to do with newt. Sorry for the "false" report.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
dependencies
docker
enhancement
go
good first issue
help wanted
Improvement
needs investigating
pull-request
Mirrored from GitHub Pull Request
 stale
wontfix
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/newt#28