[GH-ISSUE #52] connection issue after ISP reconnect #1692

New Issue

2026-04-27T22:20:02-05:00

GiteaMirror commented

2026-04-27 22:20:02 -05:00

Originally created by @Tuphal on GitHub (Jun 4, 2025).
Original GitHub issue: https://github.com/fosrl/newt/issues/52

Originally assigned to: @oschwartz10612 on GitHub.

we have a 24h reconnect from our ISP with a new IPv4.
After this reconnect, newt is not connecting again.
A container restart solves the issue until the next reconnect happens.

INFO: 2025/06/04 01:00:30 Pinging 100.89.128.1
WARN: 2025/06/04 01:00:40 Connection to server lost. Continuous reconnection attempts will be made.
WARN: 2025/06/04 01:00:40 Please check your internet connection and ensure the Pangolin server is online.
WARN: 2025/06/04 01:00:40 Newt will continue reconnection attempts automatically when connectivity is restored.
INFO: 2025/06/04 01:01:00 Pinging 100.89.128.1
INFO: 2025/06/04 01:01:30 Pinging 100.89.128.1
INFO: 2025/06/04 01:02:00 Pinging 100.89.128.1
INFO: 2025/06/04 01:02:30 Pinging 100.89.128.1
INFO: 2025/06/04 01:03:00 Pinging 100.89.128.1
INFO: 2025/06/04 01:03:30 Pinging 100.89.128.1

Originally created by @Tuphal on GitHub (Jun 4, 2025). Original GitHub issue: https://github.com/fosrl/newt/issues/52 Originally assigned to: @oschwartz10612 on GitHub. we have a 24h reconnect from our ISP with a new IPv4. After this reconnect, newt is not connecting again. A container restart solves the issue until the next reconnect happens. ``` INFO: 2025/06/04 01:00:30 Pinging 100.89.128.1 WARN: 2025/06/04 01:00:40 Connection to server lost. Continuous reconnection attempts will be made. WARN: 2025/06/04 01:00:40 Please check your internet connection and ensure the Pangolin server is online. WARN: 2025/06/04 01:00:40 Newt will continue reconnection attempts automatically when connectivity is restored. INFO: 2025/06/04 01:01:00 Pinging 100.89.128.1 INFO: 2025/06/04 01:01:30 Pinging 100.89.128.1 INFO: 2025/06/04 01:02:00 Pinging 100.89.128.1 INFO: 2025/06/04 01:02:30 Pinging 100.89.128.1 INFO: 2025/06/04 01:03:00 Pinging 100.89.128.1 INFO: 2025/06/04 01:03:30 Pinging 100.89.128.1 ```

GiteaMirror added the bug label 2026-04-27 22:20:02 -05:00

GiteaMirror closed this issue

2026-04-27 22:20:04 -05:00

GiteaMirror commented

2026-04-27 22:20:06 -05:00

@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

2026-04-27 22:20:09 -05:00

@Tuphal commented on GitHub (Jun 8, 2025):

As a temporary workaround I added a restart-part.
Source: https://stackoverflow.com/questions/69309747/schedule-daily-docker-container-restart-reset

  restarter:
    image: docker:cli
    container_name: newt-restarter
    restart: unless-stopped
    volumes: 
      - /var/run/docker.sock:/var/run/docker.sock
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro      
    entrypoint: ["/bin/sh","-c"]
    command:
      - |
        while true; do
          if [ "$$(date +'%H:%M')" = '03:05' ]; then
            docker restart newt
          fi
          sleep 60
        done

@Tuphal commented on GitHub (Jun 8, 2025): As a temporary workaround I added a restart-part. Source: [https://stackoverflow.com/questions/69309747/schedule-daily-docker-container-restart-reset](https://stackoverflow.com/questions/69309747/schedule-daily-docker-container-restart-reset) ``` restarter: image: docker:cli container_name: newt-restarter restart: unless-stopped volumes: - /var/run/docker.sock:/var/run/docker.sock - /etc/timezone:/etc/timezone:ro - /etc/localtime:/etc/localtime:ro entrypoint: ["/bin/sh","-c"] command: - | while true; do if [ "$$(date +'%H:%M')" = '03:05' ]; then docker restart newt fi sleep 60 done ```

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/newt#1692