Skip to content

Newt won't reconnect after server restart #39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
paltaio-admin opened this issue May 9, 2025 · 10 comments
Open

Newt won't reconnect after server restart #39

paltaio-admin opened this issue May 9, 2025 · 10 comments
Assignees
@oschwartz10612
Labels
bug Something isn't working

Comments

@paltaio-admin
Copy link

I'm using the latest Pangolin and Newt version (Pangolin v1.3.1, Newt v1.1.3) on both of my servers. After restarting the Pangolin VM, Newt reconnected fine, but after the second VM reboot it didn't come back and I had to manually restart the newt container.

INFO: 2025/05/08 23:55:00 Ping latency: 5.016142ms
INFO: 2025/05/08 23:55:30 Pinging 100.89.128.1
INFO: 2025/05/08 23:55:30 Ping latency: 3.178125ms
INFO: 2025/05/08 23:56:00 Pinging 100.89.128.1
INFO: 2025/05/08 23:56:00 Ping latency: 3.272988ms
INFO: 2025/05/08 23:56:30 Pinging 100.89.128.1
INFO: 2025/05/08 23:56:30 Ping latency: 5.639195ms
INFO: 2025/05/08 23:57:00 Pinging 100.89.128.1
INFO: 2025/05/08 23:57:00 Ping latency: 4.697367ms
ERROR: 2025/05/08 23:57:30 Ping failed: use of closed network connection
INFO: 2025/05/08 23:57:30 Pinging 100.89.128.1
WARN: 2025/05/08 23:57:40 Connection to server lost. Continuous reconnection attempts will be made.
WARN: 2025/05/08 23:57:40 Please check your internet connection and ensure the Pangolin server is online.
WARN: 2025/05/08 23:57:40 Newt will continue reconnection attempts automatically when connectivity is restored.
INFO: 2025/05/08 23:57:50 Sent registration message
INFO: 2025/05/08 23:57:50 Received registration message
INFO: 2025/05/08 23:57:50 Already connected! But I will send a ping anyway...
INFO: 2025/05/08 23:57:50 Ping attempt 1
INFO: 2025/05/08 23:57:50 Pinging 100.89.128.1
WARN: 2025/05/08 23:58:00 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/08 23:58:00 Ping attempt 2
INFO: 2025/05/08 23:58:00 Pinging 100.89.128.1
INFO: 2025/05/08 23:58:00 Ping latency: 5.045469ms
INFO: 2025/05/08 23:58:00 Ping succeeded after 2 attempts
INFO: 2025/05/08 23:58:00 Pinging 100.89.128.1
INFO: 2025/05/08 23:58:00 Ping latency: 4.374875ms
INFO: 2025/05/08 23:58:00 Connection to server restored!
INFO: 2025/05/08 23:58:00 Successfully re-registered with server after reconnection
INFO: 2025/05/08 23:58:00 Received registration message
INFO: 2025/05/08 23:58:00 Already connected! But I will send a ping anyway...
INFO: 2025/05/08 23:58:00 Ping attempt 1
INFO: 2025/05/08 23:58:00 Pinging 100.89.128.1
INFO: 2025/05/08 23:58:00 Ping latency: 3.838229ms
INFO: 2025/05/08 23:58:30 Pinging 100.89.128.1
INFO: 2025/05/08 23:58:30 Ping latency: 5.230547ms
ERROR: 2025/05/08 23:58:50 Ping failed: use of closed network connection
INFO: 2025/05/08 23:59:00 Pinging 100.89.128.1
INFO: 2025/05/08 23:59:02 Sent registration message
WARN: 2025/05/08 23:59:10 Connection to server lost. Continuous reconnection attempts will be made.
WARN: 2025/05/08 23:59:10 Please check your internet connection and ensure the Pangolin server is online.
WARN: 2025/05/08 23:59:10 Newt will continue reconnection attempts automatically when connectivity is restored.
INFO: 2025/05/08 23:59:30 Pinging 100.89.128.1
INFO: 2025/05/09 00:00:00 Pinging 100.89.128.1
INFO: 2025/05/09 00:00:30 Pinging 100.89.128.1
INFO: 2025/05/09 00:01:00 Pinging 100.89.128.1
INFO: 2025/05/09 00:01:30 Pinging 100.89.128.1
INFO: 2025/05/09 00:02:00 Pinging 100.89.128.1
INFO: 2025/05/09 00:02:30 Pinging 100.89.128.1
INFO: 2025/05/09 00:03:00 Pinging 100.89.128.1
INFO: 2025/05/09 00:03:30 Pinging 100.89.128.1

... after waiting for a while I had to `docker restart newt`

As a workaround I made a cron checking the url directly and restart newt if it gets a gateway error.
@RomRider
Copy link

RomRider commented May 14, 2025 •
edited
Loading

Same issue, running newt on K8S (happened after a connection switch between Fiber, 4G and back to Fiber):

INFO: 2025/05/14 13:29:03 Ping attempt 618
INFO: 2025/05/14 13:29:03 Pinging 100.89.128.1
WARN: 2025/05/14 13:29:13 Ping attempt 618 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:29:15 Pinging 100.89.128.1
INFO: 2025/05/14 13:29:34 Ping attempt 1053
INFO: 2025/05/14 13:29:34 Pinging 100.89.128.1
WARN: 2025/05/14 13:29:44 Ping attempt 1053 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:29:45 Pinging 100.89.128.1
INFO: 2025/05/14 13:30:13 Ping attempt 619
INFO: 2025/05/14 13:30:13 Pinging 100.89.128.1
INFO: 2025/05/14 13:30:15 Pinging 100.89.128.1
WARN: 2025/05/14 13:30:23 Ping attempt 619 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:30:44 Ping attempt 1054
INFO: 2025/05/14 13:30:44 Pinging 100.89.128.1
INFO: 2025/05/14 13:30:45 Pinging 100.89.128.1
WARN: 2025/05/14 13:30:54 Ping attempt 1054 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:31:15 Pinging 100.89.128.1
INFO: 2025/05/14 13:31:23 Ping attempt 620
INFO: 2025/05/14 13:31:23 Pinging 100.89.128.1
WARN: 2025/05/14 13:31:33 Ping attempt 620 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:31:45 Pinging 100.89.128.1
INFO: 2025/05/14 13:31:54 Ping attempt 1055
INFO: 2025/05/14 13:31:54 Pinging 100.89.128.1
WARN: 2025/05/14 13:32:04 Ping attempt 1055 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:32:15 Pinging 100.89.128.1
INFO: 2025/05/14 13:32:33 Ping attempt 621
INFO: 2025/05/14 13:32:33 Pinging 100.89.128.1
WARN: 2025/05/14 13:32:43 Ping attempt 621 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:32:45 Pinging 100.89.128.1
INFO: 2025/05/14 13:33:04 Ping attempt 1056
INFO: 2025/05/14 13:33:04 Pinging 100.89.128.1
WARN: 2025/05/14 13:33:14 Ping attempt 1056 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:33:15 Pinging 100.89.128.1
INFO: 2025/05/14 13:33:43 Ping attempt 622
INFO: 2025/05/14 13:33:43 Pinging 100.89.128.1
INFO: 2025/05/14 13:33:45 Pinging 100.89.128.1
WARN: 2025/05/14 13:33:53 Ping attempt 622 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:34:14 Ping attempt 1057
INFO: 2025/05/14 13:34:14 Pinging 100.89.128.1
INFO: 2025/05/14 13:34:15 Pinging 100.89.128.1
WARN: 2025/05/14 13:34:24 Ping attempt 1057 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:34:45 Pinging 100.89.128.1
INFO: 2025/05/14 13:34:53 Ping attempt 623
INFO: 2025/05/14 13:34:53 Pinging 100.89.128.1
WARN: 2025/05/14 13:35:03 Ping attempt 623 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:35:15 Pinging 100.89.128.1
INFO: 2025/05/14 13:35:24 Ping attempt 1058
INFO: 2025/05/14 13:35:24 Pinging 100.89.128.1
WARN: 2025/05/14 13:35:34 Ping attempt 1058 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:35:45 Pinging 100.89.128.1
INFO: 2025/05/14 13:36:03 Ping attempt 624
INFO: 2025/05/14 13:36:03 Pinging 100.89.128.1
WARN: 2025/05/14 13:36:13 Ping attempt 624 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:36:15 Pinging 100.89.128.1
INFO: 2025/05/14 13:36:34 Ping attempt 1059
INFO: 2025/05/14 13:36:34 Pinging 100.89.128.1
WARN: 2025/05/14 13:36:44 Ping attempt 1059 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:36:45 Pinging 100.89.128.1
INFO: 2025/05/14 13:37:13 Ping attempt 625
INFO: 2025/05/14 13:37:13 Pinging 100.89.128.1
INFO: 2025/05/14 13:37:15 Pinging 100.89.128.1
WARN: 2025/05/14 13:37:23 Ping attempt 625 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:37:44 Ping attempt 1060
INFO: 2025/05/14 13:37:44 Pinging 100.89.128.1
INFO: 2025/05/14 13:37:45 Pinging 100.89.128.1
WARN: 2025/05/14 13:37:54 Ping attempt 1060 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:38:15 Pinging 100.89.128.1
INFO: 2025/05/14 13:38:23 Ping attempt 626
INFO: 2025/05/14 13:38:23 Pinging 100.89.128.1
WARN: 2025/05/14 13:38:33 Ping attempt 626 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:38:45 Pinging 100.89.128.1
INFO: 2025/05/14 13:38:54 Ping attempt 1061
INFO: 2025/05/14 13:38:54 Pinging 100.89.128.1
WARN: 2025/05/14 13:39:04 Ping attempt 1061 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:39:15 Pinging 100.89.128.1
INFO: 2025/05/14 13:39:33 Ping attempt 627
INFO: 2025/05/14 13:39:33 Pinging 100.89.128.1
WARN: 2025/05/14 13:39:43 Ping attempt 627 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:39:45 Pinging 100.89.128.1
INFO: 2025/05/14 13:40:04 Ping attempt 1062
INFO: 2025/05/14 13:40:04 Pinging 100.89.128.1
WARN: 2025/05/14 13:40:14 Ping attempt 1062 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:40:15 Pinging 100.89.128.1
INFO: 2025/05/14 13:40:43 Ping attempt 628
INFO: 2025/05/14 13:40:43 Pinging 100.89.128.1
INFO: 2025/05/14 13:40:45 Pinging 100.89.128.1
WARN: 2025/05/14 13:40:53 Ping attempt 628 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:41:14 Ping attempt 1063
INFO: 2025/05/14 13:41:14 Pinging 100.89.128.1
INFO: 2025/05/14 13:41:15 Pinging 100.89.128.1
WARN: 2025/05/14 13:41:24 Ping attempt 1063 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:41:45 Pinging 100.89.128.1
INFO: 2025/05/14 13:41:53 Ping attempt 629
INFO: 2025/05/14 13:41:53 Pinging 100.89.128.1
WARN: 2025/05/14 13:42:03 Ping attempt 629 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:42:15 Pinging 100.89.128.1
INFO: 2025/05/14 13:42:24 Ping attempt 1064
INFO: 2025/05/14 13:42:24 Pinging 100.89.128.1
WARN: 2025/05/14 13:42:34 Ping attempt 1064 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/14 13:42:45 Pinging 100.89.128.1

Only solution is killing the pod and let k8s recreate it and then it works directly again (see log timestamps)

INFO: 2025/05/14 13:43:08 Sent registration message
INFO: 2025/05/14 13:43:08 Received registration message
INFO: 2025/05/14 13:43:08 Received: {Type:newt/wg/connect Data:map[endpoint:xxx.example.com:51820 publicKey:xxxxxxxxxxxxxxxxxxxxxx= serverIP:100.89.128.1 targets:map[tcp:[60538:xxxx:yyyy[] udp:]] tunnelIP:100.89.128.8]}
INFO: 2025/05/14 13:43:08 WireGuard device created. Lets ping the server now...
INFO: 2025/05/14 13:43:08 Ping attempt 1
INFO: 2025/05/14 13:43:08 Pinging 100.89.128.1
INFO: 2025/05/14 13:43:08 Ping latency: 10.034158ms
INFO: 2025/05/14 13:43:08 Starting ping check
INFO: 2025/05/14 13:43:08 Started tcp proxy from 100.89.128.8:60538 to traefik:4243
INFO: 2025/05/14 13:43:38 Pinging 100.89.128.1
INFO: 2025/05/14 13:43:38 Ping latency: 4.971728ms
INFO: 2025/05/14 13:44:08 Pinging 100.89.128.1
INFO: 2025/05/14 13:44:08 Ping latency: 4.80853ms
INFO: 2025/05/14 13:44:38 Pinging 100.89.128.1
INFO: 2025/05/14 13:44:38 Ping latency: 4.57071ms
INFO: 2025/05/14 13:45:08 Pinging 100.89.128.1
INFO: 2025/05/14 13:45:08 Ping latency: 4.90791ms

@hendyj
Copy link

hendyj commented May 16, 2025 •
edited
Loading

Same issue.

newt-1   | ERROR: 2025/05/16 22:09:36 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.elevationengine.com/api/v1/auth/newt/get-token": dial tcp 107.172.142.108:443: connect: no route to host. Retrying in 10s...
newt-1   | ERROR: 2025/05/16 22:09:46 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.elevationengine.com/api/v1/auth/newt/get-token": dial tcp 107.172.142.108:443: connect: no route to host. Retrying in 10s...
newt-1   | INFO: 2025/05/16 22:09:55 Pinging 100.89.128.1
newt-1   | INFO: 2025/05/16 22:09:58 Sent registration message
newt-1   | INFO: 2025/05/16 22:09:58 Received registration message
newt-1   | INFO: 2025/05/16 22:09:58 Already connected! But I will send a ping anyway...
newt-1   | INFO: 2025/05/16 22:09:58 Ping attempt 1
newt-1   | INFO: 2025/05/16 22:09:58 Pinging 100.89.128.1
newt-1   | WARN: 2025/05/16 22:10:08 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout
newt-1   | INFO: 2025/05/16 22:10:08 Ping attempt 2
newt-1   | INFO: 2025/05/16 22:10:08 Pinging 100.89.128.1

It thinks it is already connected, but it is not...

@scetu
Copy link

scetu commented May 18, 2025

I am facing this as well! Newt installed as systemd service, some of my tunnells do not connect to pangolin once machine starts.

@mellow65
Copy link

I just figured out this was my issue this morning after my VPS reboot for an update. A simple reboot to the proxmox container that has newt running fixed it. I'm wondering if I could add a health check to the systemd to check if the tunnels are up or not.

@sergiors
Copy link

Some error here

@oschwartz10612 oschwartz10612 self-assigned this May 22, 2025
@oschwartz10612 oschwartz10612 added the bug Something isn't working label May 22, 2025
@bytec77
Copy link

bytec77 commented May 22, 2025

same error here.

@sergiors
Copy link

Here is my logs

INFO: 2025/05/23 22:57:32 Sent registration message
INFO: 2025/05/23 22:57:32 Received registration message
INFO: 2025/05/23 22:57:32 Received: {Type:newt/wg/connect Data:map[endpoint:sergio.run:51820 publicKey:SmAq3az/NlnnOr0aJK+Ni4/6vFRwrQpC9WkLrRU4e2M= serverIP:100.89.128.1 targets:map[tcp:[41998:portainer:9443 63675:ihatemoney:8000 50166:postgres:5432 53223:mariadb:3306 41616:192.168.15.3:22 64629:filebrowser:80 65341:glances:61208 47475:immich-server:2283 51873:n8n:5678 44117:it-tools:80 45284:myspeed:5216 56041:pairdrop:3000 59955:stirling-pdf:8080 42002:pihole:80 50485:plex:32400 45831:valheim:80 54685:redis:6379 55364:adminer:8080 42489:dokku:80 53719:gitea:3000 54009:dokku:22 41223:headscale:8080 40118:mongo:27017 41802:ytdl:17442] udp:[]] tunnelIP:100.89.128.4]}
INFO: 2025/05/23 22:57:32 WireGuard device created. Lets ping the server now...
INFO: 2025/05/23 22:57:32 Ping attempt 1
INFO: 2025/05/23 22:57:32 Pinging 100.89.128.1
WARN: 2025/05/23 22:57:42 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/23 22:57:42 Starting ping check
INFO: 2025/05/23 22:57:42 Ping attempt 2
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:44117 to it-tools:80
INFO: 2025/05/23 22:57:42 Pinging 100.89.128.1
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:56041 to pairdrop:3000
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:54685 to redis:6379
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:53719 to gitea:3000
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:41998 to portainer:9443
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:50166 to postgres:5432
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:41616 to 192.168.15.3:22
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:47475 to immich-server:2283
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:41223 to headscale:8080
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:40118 to mongo:27017
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:53223 to mariadb:3306
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:65341 to glances:61208
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:51873 to n8n:5678
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:42002 to pihole:80
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:45831 to valheim:80
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:55364 to adminer:8080
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:54009 to dokku:22
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:64629 to filebrowser:80
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:45284 to myspeed:5216
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:59955 to stirling-pdf:8080
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:50485 to plex:32400
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:63675 to ihatemoney:8000
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:42489 to dokku:80
INFO: 2025/05/23 22:57:42 Started tcp proxy from 100.89.128.4:41802 to ytdl:17442
WARN: 2025/05/23 22:57:52 Ping attempt 2 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/23 22:57:54 Ping attempt 3
INFO: 2025/05/23 22:57:54 Pinging 100.89.128.1
WARN: 2025/05/23 22:58:04 Ping attempt 3 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/23 22:58:06 Ping attempt 4
INFO: 2025/05/23 22:58:06 Pinging 100.89.128.1
INFO: 2025/05/23 22:58:12 Pinging 100.89.128.1
WARN: 2025/05/23 22:58:16 Ping attempt 4 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/23 22:58:18 Ping attempt 5
INFO: 2025/05/23 22:58:18 Pinging 100.89.128.1
WARN: 2025/05/23 22:58:22 Connection to server lost. Continuous reconnection attempts will be made.
WARN: 2025/05/23 22:58:22 Please check your internet connection and ensure the Pangolin server is online.
WARN: 2025/05/23 22:58:22 Newt will continue reconnection attempts automatically when connectivity is restored.
WARN: 2025/05/23 22:58:28 Ping attempt 5 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/23 22:58:28 Increasing ping retry delay to 3s
INFO: 2025/05/23 22:58:31 Ping attempt 6
INFO: 2025/05/23 22:58:31 Pinging 100.89.128.1
WARN: 2025/05/23 22:58:41 Ping attempt 6 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/23 22:58:42 Pinging 100.89.128.1
INFO: 2025/05/23 22:58:44 Ping attempt 7
INFO: 2025/05/23 22:58:44 Pinging 100.89.128.1
WARN: 2025/05/23 22:58:54 Ping attempt 7 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/23 22:58:57 Ping attempt 8
INFO: 2025/05/23 22:58:57 Pinging 100.89.128.1
WARN: 2025/05/23 22:59:07 Ping attempt 8 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/23 22:59:10 Ping attempt 9
INFO: 2025/05/23 22:59:10 Pinging 100.89.128.1
INFO: 2025/05/23 22:59:12 Pinging 100.89.128.1
WARN: 2025/05/23 22:59:20 Ping attempt 9 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/23 22:59:23 Ping attempt 10
INFO: 2025/05/23 22:59:23 Pinging 100.89.128.1
WARN: 2025/05/23 22:59:33 Ping attempt 10 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/23 22:59:33 Increasing ping retry delay to 4.5s

@oschwartz10612
Copy link
Member

Ill try to reproduce ASAP. Not seeing a ton in the logs that explain why the time out is happening. Could be Pangolin side with gerbil.

@sergiors
Copy link

Ill try to reproduce ASAP. Not seeing a ton in the logs that explain why the time out is happening. Could be Pangolin side with gerbil.

I don't why, but everything was working, out of the blue, it's happen, I tried to check if as some block from VPS (racknerd), but it didn't make any sense

@mellow65
Copy link

Misery loves company I guess. This morning my VPS rebooted for an update and newt stayed connected. 🤷‍♀️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@oschwartz10612 oschwartz10612

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@sergiors @oschwartz10612 @hendyj @RomRider @scetu @bytec77 @mellow65 @paltaio-admin