github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-07-11 10:50:35 -05:00
Code Issues 1.6k Packages Projects Releases 79 Wiki Activity

Unable to Connect to Newt #439

New Issue
Closed
opened 2025-11-13 12:00:32 -06:00 by GiteaMirror · 25 comments
GiteaMirror commented 2025-11-13 12:00:32 -06:00
Owner
Copy Link

Originally created by @Blucose on GitHub (Jun 15, 2025).

I'm unable to create any docker Newt that connects to my pangolin.

I am able to reach the server with netcat, so ports don't seem to be the problem. The logs for Newt show that it is unable to reach my pangolin server at 100.x, after a successful wireguard handshake. I've tried on multiple machines.

Any help appreciated, happy to provide any logs required.

Originally created by @Blucose on GitHub (Jun 15, 2025). I'm unable to create any docker Newt that connects to my pangolin. I am able to reach the server with netcat, so ports don't seem to be the problem. The logs for Newt show that it is unable to reach my pangolin server at 100.x, after a successful wireguard handshake. I've tried on multiple machines. Any help appreciated, happy to provide any logs required.
GiteaMirror commented 2025-11-13 12:00:33 -06:00
Author
Owner
Copy Link

@jackrosenberg commented on GitHub (Jun 15, 2025):

If it's only the ping that is failing, try rebooting the edge server.

@jackrosenberg commented on GitHub (Jun 15, 2025): If it's only the ping that is failing, try rebooting the edge server.
GiteaMirror commented 2025-11-13 12:00:33 -06:00
Author
Owner
Copy Link

@Blucose commented on GitHub (Jun 15, 2025):

I assume the edge server is the server running newt. I've rebooted and no change. Both on NixOS and Truenas.

@Blucose commented on GitHub (Jun 15, 2025): I assume the edge server is the server running newt. I've rebooted and no change. Both on NixOS and Truenas.
GiteaMirror commented 2025-11-13 12:00:33 -06:00
Author
Owner
Copy Link

@jackrosenberg commented on GitHub (Jun 15, 2025):

Ah thats my bad, I meant to say restart the VPS :). What do the logs say?

@jackrosenberg commented on GitHub (Jun 15, 2025): Ah thats my bad, I meant to say restart the VPS :). What do the logs say?
GiteaMirror commented 2025-11-13 12:00:34 -06:00
Author
Owner
Copy Link

@Blucose commented on GitHub (Jun 15, 2025):

the logs for Newt on the Edge (in this case truenas docker compose)

newt  | INFO: 2025/06/15 14:41:13 Received: {Type:newt/wg/connect Data:map[endpoint:justinfrank.co.uk:51820 publicKey:S8oUFaXvH0z4zpFbR2bHvKCurrToi3x4bsDPaU9glhU= serverIP:100.89.128.1 targets:map[tcp:[] udp:[]] tunnelIP:100.89.128.4]}
newt  | INFO: 2025/06/15 14:41:13 WireGuard device created. Lets ping the server now...
newt  | INFO: 2025/06/15 14:41:13 Ping attempt 1
newt  | INFO: 2025/06/15 14:41:13 Pinging 100.89.128.1
newt  | WARN: 2025/06/15 14:41:23 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout
newt  | INFO: 2025/06/15 14:41:23 Starting ping check
newt  | INFO: 2025/06/15 14:41:23 Ping attempt 2
newt  | INFO: 2025/06/15 14:41:23 Pinging 100.89.128.1

The logs for Pangolin on the VPS


Starting migrations from version 1.5.1
Migrations to run: 
All migrations completed successfully
2025-06-15T14:35:13.579Z [warn]: Email SMTP configuration is missing. Emails will not be sent.
2025-06-15T14:35:14.902Z [info]: API server is running on http://localhost:3000
2025-06-15T14:35:14.903Z [info]: Internal server is running on http://localhost:3001
2025-06-15T14:35:15.999Z [info]: Next.js server is running on http://localhost:3002
2025-06-15T14:35:23.280Z [info]: Establishing websocket connection
2025-06-15T14:35:23.280Z [info]: Client added to tracking - Newt ID: is4vra4tg5p2xr9, Total connections: 1
2025-06-15T14:35:23.280Z [info]: WebSocket connection established - Newt ID: is4vra4tg5p2xr9
2025-06-15T14:35:23.302Z [info]: Handling register message!
2025-06-15T14:35:23.331Z [info]: Peer added successfully: {"peer":"Peer added successfully"}
2025-06-15T14:41:13.358Z [info]: Establishing websocket connection
2025-06-15T14:41:13.358Z [info]: Client added to tracking - Newt ID: 1g3m42k654xyegg, Total connections: 1
2025-06-15T14:41:13.358Z [info]: WebSocket connection established - Newt ID: 1g3m42k654xyegg
2025-06-15T14:41:13.378Z [info]: Handling register message!
2025-06-15T14:41:13.381Z [info]: Public key mismatch. Deleting old peer...
2025-06-15T14:41:13.385Z [info]: Peer deleted successfully: {"0":"P","1":"e","2":"e","3":"r","4":" ","5":"r","6":"e","7":"m","8":"o","9":"v","10":"e","11":"d","12":" ","13":"s","14":"u","15":"c","16":"c","17":"e","18":"s","19":"s","20":"f","21":"u","22":"l","23":"l","24":"y"}
2025-06-15T14:41:13.387Z [info]: Peer added successfully: {"peer":"Peer added successfully"}

Gerbil on VPS


INFO: 2025/06/15 14:35:08 Fetching remote config from http://pangolin:3001/api/v1/gerbil/get-config
ERROR: 2025/06/15 14:35:08 Error fetching remote config http://pangolin:3001/api/v1/gerbil/get-config: Post "http://pangolin:3001/api/v1/gerbil/get-config": dial tcp 172.18.0.3:3001: connect: connection refused
ERROR: 2025/06/15 14:35:08 Failed to load configuration: Post "http://pangolin:3001/api/v1/gerbil/get-config": dial tcp 172.18.0.3:3001: connect: connection refused
INFO: 2025/06/15 14:35:13 Fetching remote config from http://pangolin:3001/api/v1/gerbil/get-config
ERROR: 2025/06/15 14:35:13 Error fetching remote config http://pangolin:3001/api/v1/gerbil/get-config: Post "http://pangolin:3001/api/v1/gerbil/get-config": dial tcp 172.18.0.3:3001: connect: connection refused
ERROR: 2025/06/15 14:35:13 Failed to load configuration: Post "http://pangolin:3001/api/v1/gerbil/get-config": dial tcp 172.18.0.3:3001: connect: connection refused
INFO: 2025/06/15 14:35:18 Fetching remote config from http://pangolin:3001/api/v1/gerbil/get-config
INFO: 2025/06/15 14:35:18 Created WireGuard interface wg0
INFO: 2025/06/15 14:35:18 Assigned IP address 100.89.128.1/24 to interface wg0
INFO: 2025/06/15 14:35:18 Attempting to delete existing MSS clamping rule for chain INPUT
INFO: 2025/06/15 14:35:18 Attempting to delete existing MSS clamping rule for chain OUTPUT
INFO: 2025/06/15 14:35:18 Attempting to delete existing MSS clamping rule for chain FORWARD
INFO: 2025/06/15 14:35:18 Adding MSS clamping rule for chain INPUT
INFO: 2025/06/15 14:35:18 Successfully added and verified MSS clamping rule for chain INPUT
INFO: 2025/06/15 14:35:18 Adding MSS clamping rule for chain OUTPUT
INFO: 2025/06/15 14:35:18 Successfully added and verified MSS clamping rule for chain OUTPUT
INFO: 2025/06/15 14:35:18 Adding MSS clamping rule for chain FORWARD
INFO: 2025/06/15 14:35:18 Successfully added and verified MSS clamping rule for chain FORWARD
INFO: 2025/06/15 14:35:18 WireGuard interface wg0 created and configured
INFO: 2025/06/15 14:35:18 Peer cRsYYnH82G6m/G+aNMQ8iZkJ7rZIZmZXcaM0IYnyF2Y= added successfully
INFO: 2025/06/15 14:35:18 Peer 1mR7qAk4EtrdW/B6oA9K5MSxMNAzRjJUj6X4iYr8cz8= added successfully
INFO: 2025/06/15 14:35:18 Starting server on :3003
INFO: 2025/06/15 14:35:23 Peer 9UUTNBciIxYO6X7Y00iiPtPPldsaenzEbqIg2eXZjmQ= added successfully
INFO: 2025/06/15 14:41:13 Peer cRsYYnH82G6m/G+aNMQ8iZkJ7rZIZmZXcaM0IYnyF2Y= removed successfully
INFO: 2025/06/15 14:41:13 Peer vYruG6iES8fYRxsRNwC3E+dPsyahbOzUJEu0RWCRzmM= added successfully
@Blucose commented on GitHub (Jun 15, 2025): the logs for Newt on the Edge (in this case truenas docker compose) ``` newt | INFO: 2025/06/15 14:41:13 Received: {Type:newt/wg/connect Data:map[endpoint:justinfrank.co.uk:51820 publicKey:S8oUFaXvH0z4zpFbR2bHvKCurrToi3x4bsDPaU9glhU= serverIP:100.89.128.1 targets:map[tcp:[] udp:[]] tunnelIP:100.89.128.4]} newt | INFO: 2025/06/15 14:41:13 WireGuard device created. Lets ping the server now... newt | INFO: 2025/06/15 14:41:13 Ping attempt 1 newt | INFO: 2025/06/15 14:41:13 Pinging 100.89.128.1 newt | WARN: 2025/06/15 14:41:23 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout newt | INFO: 2025/06/15 14:41:23 Starting ping check newt | INFO: 2025/06/15 14:41:23 Ping attempt 2 newt | INFO: 2025/06/15 14:41:23 Pinging 100.89.128.1 ``` The logs for Pangolin on the VPS ``` Starting migrations from version 1.5.1 Migrations to run: All migrations completed successfully 2025-06-15T14:35:13.579Z [warn]: Email SMTP configuration is missing. Emails will not be sent. 2025-06-15T14:35:14.902Z [info]: API server is running on http://localhost:3000 2025-06-15T14:35:14.903Z [info]: Internal server is running on http://localhost:3001 2025-06-15T14:35:15.999Z [info]: Next.js server is running on http://localhost:3002 2025-06-15T14:35:23.280Z [info]: Establishing websocket connection 2025-06-15T14:35:23.280Z [info]: Client added to tracking - Newt ID: is4vra4tg5p2xr9, Total connections: 1 2025-06-15T14:35:23.280Z [info]: WebSocket connection established - Newt ID: is4vra4tg5p2xr9 2025-06-15T14:35:23.302Z [info]: Handling register message! 2025-06-15T14:35:23.331Z [info]: Peer added successfully: {"peer":"Peer added successfully"} 2025-06-15T14:41:13.358Z [info]: Establishing websocket connection 2025-06-15T14:41:13.358Z [info]: Client added to tracking - Newt ID: 1g3m42k654xyegg, Total connections: 1 2025-06-15T14:41:13.358Z [info]: WebSocket connection established - Newt ID: 1g3m42k654xyegg 2025-06-15T14:41:13.378Z [info]: Handling register message! 2025-06-15T14:41:13.381Z [info]: Public key mismatch. Deleting old peer... 2025-06-15T14:41:13.385Z [info]: Peer deleted successfully: {"0":"P","1":"e","2":"e","3":"r","4":" ","5":"r","6":"e","7":"m","8":"o","9":"v","10":"e","11":"d","12":" ","13":"s","14":"u","15":"c","16":"c","17":"e","18":"s","19":"s","20":"f","21":"u","22":"l","23":"l","24":"y"} 2025-06-15T14:41:13.387Z [info]: Peer added successfully: {"peer":"Peer added successfully"} ``` Gerbil on VPS ``` INFO: 2025/06/15 14:35:08 Fetching remote config from http://pangolin:3001/api/v1/gerbil/get-config ERROR: 2025/06/15 14:35:08 Error fetching remote config http://pangolin:3001/api/v1/gerbil/get-config: Post "http://pangolin:3001/api/v1/gerbil/get-config": dial tcp 172.18.0.3:3001: connect: connection refused ERROR: 2025/06/15 14:35:08 Failed to load configuration: Post "http://pangolin:3001/api/v1/gerbil/get-config": dial tcp 172.18.0.3:3001: connect: connection refused INFO: 2025/06/15 14:35:13 Fetching remote config from http://pangolin:3001/api/v1/gerbil/get-config ERROR: 2025/06/15 14:35:13 Error fetching remote config http://pangolin:3001/api/v1/gerbil/get-config: Post "http://pangolin:3001/api/v1/gerbil/get-config": dial tcp 172.18.0.3:3001: connect: connection refused ERROR: 2025/06/15 14:35:13 Failed to load configuration: Post "http://pangolin:3001/api/v1/gerbil/get-config": dial tcp 172.18.0.3:3001: connect: connection refused INFO: 2025/06/15 14:35:18 Fetching remote config from http://pangolin:3001/api/v1/gerbil/get-config INFO: 2025/06/15 14:35:18 Created WireGuard interface wg0 INFO: 2025/06/15 14:35:18 Assigned IP address 100.89.128.1/24 to interface wg0 INFO: 2025/06/15 14:35:18 Attempting to delete existing MSS clamping rule for chain INPUT INFO: 2025/06/15 14:35:18 Attempting to delete existing MSS clamping rule for chain OUTPUT INFO: 2025/06/15 14:35:18 Attempting to delete existing MSS clamping rule for chain FORWARD INFO: 2025/06/15 14:35:18 Adding MSS clamping rule for chain INPUT INFO: 2025/06/15 14:35:18 Successfully added and verified MSS clamping rule for chain INPUT INFO: 2025/06/15 14:35:18 Adding MSS clamping rule for chain OUTPUT INFO: 2025/06/15 14:35:18 Successfully added and verified MSS clamping rule for chain OUTPUT INFO: 2025/06/15 14:35:18 Adding MSS clamping rule for chain FORWARD INFO: 2025/06/15 14:35:18 Successfully added and verified MSS clamping rule for chain FORWARD INFO: 2025/06/15 14:35:18 WireGuard interface wg0 created and configured INFO: 2025/06/15 14:35:18 Peer cRsYYnH82G6m/G+aNMQ8iZkJ7rZIZmZXcaM0IYnyF2Y= added successfully INFO: 2025/06/15 14:35:18 Peer 1mR7qAk4EtrdW/B6oA9K5MSxMNAzRjJUj6X4iYr8cz8= added successfully INFO: 2025/06/15 14:35:18 Starting server on :3003 INFO: 2025/06/15 14:35:23 Peer 9UUTNBciIxYO6X7Y00iiPtPPldsaenzEbqIg2eXZjmQ= added successfully INFO: 2025/06/15 14:41:13 Peer cRsYYnH82G6m/G+aNMQ8iZkJ7rZIZmZXcaM0IYnyF2Y= removed successfully INFO: 2025/06/15 14:41:13 Peer vYruG6iES8fYRxsRNwC3E+dPsyahbOzUJEu0RWCRzmM= added successfully ```
GiteaMirror commented 2025-11-13 12:00:34 -06:00
Author
Owner
Copy Link

@jackrosenberg commented on GitHub (Jun 15, 2025):

looks to me like a mismatch between network interfaces:
Internal server is running on http://localhost:3001 and
Error fetching remote config http://pangolin:3001/api/v1/gerbil/get-config.
I believe this is a setting somewhere, though i'm not familiar with how TrueNas does this. If this isn't is im afraid this is about the extent of my expertise :)

@jackrosenberg commented on GitHub (Jun 15, 2025): looks to me like a mismatch between network interfaces: `Internal server is running on http://localhost:3001` and `Error fetching remote config http://pangolin:3001/api/v1/gerbil/get-config`. I believe this is a setting somewhere, though i'm not familiar with how TrueNas does this. If this isn't is im afraid this is about the extent of my expertise :)
GiteaMirror commented 2025-11-13 12:00:34 -06:00
Author
Owner
Copy Link

@Blucose commented on GitHub (Jun 15, 2025):

All of those are on the VPS running Ubuntu no? It's only Newt running on Truenas.

Also those errors seem to eventually go away, I think it's just a delay until pangolin has started fully.

@Blucose commented on GitHub (Jun 15, 2025): All of those are on the VPS running Ubuntu no? It's only Newt running on Truenas. Also those errors seem to eventually go away, I think it's just a delay until pangolin has started fully.
GiteaMirror commented 2025-11-13 12:00:34 -06:00
Author
Owner
Copy Link

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

^^^ yeah I think the get config is fine.

This is almost always a firewall issue when it cant ping. But I know you say you are able to reach the server with netcat. Did you test netcat with UDP port 51820 and get success? Could you triple check port UDP 51820 is open on BOTH the VPS firewall from the provider if there is one and in linux with UFW/iptables/nftables?

You can run a TCP dump when newt connects and look for that 51820 UDP traffic. Let us know if you are getting traffic on that port and it still cant connect.

@oschwartz10612 commented on GitHub (Jun 15, 2025): ^^^ yeah I think the get config is fine. This is almost always a firewall issue when it cant ping. But I know you say you are able to reach the server with netcat. Did you test netcat with UDP port 51820 and get success? Could you triple check port UDP 51820 is open on BOTH the VPS firewall from the provider if there is one and in linux with UFW/iptables/nftables? You can run a TCP dump when newt connects and look for that 51820 UDP traffic. Let us know if you are getting traffic on that port and it still cant connect.
GiteaMirror commented 2025-11-13 12:00:35 -06:00
Author
Owner
Copy Link

@Blucose commented on GitHub (Jun 15, 2025):

When I downed the compose on my VPS and listened to UDP 51820 I was able to see the netcat message sent from the edge server.

How do I run a TCP dump?

Appreciating all your help guys!

@Blucose commented on GitHub (Jun 15, 2025): When I downed the compose on my VPS and listened to UDP 51820 I was able to see the netcat message sent from the edge server. How do I run a TCP dump? Appreciating all your help guys!
GiteaMirror commented 2025-11-13 12:00:35 -06:00
Author
Owner
Copy Link

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

Okay thats a pretty good sign then that the firewall is okay. To tcpdump you can do tcpdump -i any -n udp port 51820

Could you double check your docker compose correctly exposes the udp 51820 port? Did you install from the installer?

@oschwartz10612 commented on GitHub (Jun 15, 2025): Okay thats a pretty good sign then that the firewall is okay. To tcpdump you can do `tcpdump -i any -n udp port 51820` Could you double check your docker compose correctly exposes the udp 51820 port? Did you install from the installer?
GiteaMirror commented 2025-11-13 12:00:35 -06:00
Author
Owner
Copy Link

@Blucose commented on GitHub (Jun 15, 2025):

This is the a snapshot of the output of the TCP dump from the Truenas System while Newt starts up:


$ sudo tcpdump -i any -n udp port 51820
tcpdump: data link type LINUX_SLL2
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on any, link-type LINUX_SLL2 (Linux cooked v2), snapshot length 262144 bytes
19:16:32.065948 vethf7c1526 P   IP 172.28.10.2.45911 > 169.150.196.2.51820: UDP, length 96
19:16:32.065948 br-9427578bc1e4 In  IP 172.28.10.2.45911 > 169.150.196.2.51820: UDP, length 96
19:16:32.065996 enp7s0 Out IP 192.168.1.87.45911 > 169.150.196.2.51820: UDP, length 96

...


19:16:52.233690 br-9427578bc1e4 In  IP 172.28.10.2.45911 > 169.150.196.2.51820: UDP, length 96
19:16:52.233704 enp7s0 Out IP 192.168.1.87.45911 > 169.150.196.2.51820: UDP, length 96
19:16:52.243865 enp7s0 In  IP 169.150.196.2.51820 > 192.168.1.87.45911: UDP, length 96
19:16:52.243909 br-9427578bc1e4 Out IP 169.150.196.2.51820 > 172.28.10.2.45911: UDP, length 96
19:16:52.243915 vethf7c1526 Out IP 169.150.196.2.51820 > 172.28.10.2.45911: UDP, length 96
19:16:52.244245 vethf7c1526 P   IP 172.28.10.2.45911 > 169.150.196.2.51820: UDP, length 96
19:16:52.244245 br-9427578bc1e4 In  IP 172.28.10.2.45911 > 169.150.196.2.51820: UDP, length 96
19:16:52.244292 enp7s0 Out IP 192.168.1.87.45911 > 169.150.196.2.51820: UDP, length 96
19:16:52.423543 veth43b1168 P   IP 172.16.3.2.60714 > 104.21.32.1.51820: UDP, length 148
19:16:52.423543 br-6195d43a8398 In  IP 172.16.3.2.60714 > 104.21.32.1.51820: UDP, length 148
19:16:52.423593 enp7s0 Out IP 192.168.1.87.60714 > 104.21.32.1.51820: UDP, length 148
^C
345 packets captured
347 packets received by filter
0 packets dropped by kernel
@Blucose commented on GitHub (Jun 15, 2025): This is the a snapshot of the output of the TCP dump from the Truenas System while Newt starts up: ``` $ sudo tcpdump -i any -n udp port 51820 tcpdump: data link type LINUX_SLL2 tcpdump: verbose output suppressed, use -v[v]... for full protocol decode listening on any, link-type LINUX_SLL2 (Linux cooked v2), snapshot length 262144 bytes 19:16:32.065948 vethf7c1526 P IP 172.28.10.2.45911 > 169.150.196.2.51820: UDP, length 96 19:16:32.065948 br-9427578bc1e4 In IP 172.28.10.2.45911 > 169.150.196.2.51820: UDP, length 96 19:16:32.065996 enp7s0 Out IP 192.168.1.87.45911 > 169.150.196.2.51820: UDP, length 96 ``` ... ``` 19:16:52.233690 br-9427578bc1e4 In IP 172.28.10.2.45911 > 169.150.196.2.51820: UDP, length 96 19:16:52.233704 enp7s0 Out IP 192.168.1.87.45911 > 169.150.196.2.51820: UDP, length 96 19:16:52.243865 enp7s0 In IP 169.150.196.2.51820 > 192.168.1.87.45911: UDP, length 96 19:16:52.243909 br-9427578bc1e4 Out IP 169.150.196.2.51820 > 172.28.10.2.45911: UDP, length 96 19:16:52.243915 vethf7c1526 Out IP 169.150.196.2.51820 > 172.28.10.2.45911: UDP, length 96 19:16:52.244245 vethf7c1526 P IP 172.28.10.2.45911 > 169.150.196.2.51820: UDP, length 96 19:16:52.244245 br-9427578bc1e4 In IP 172.28.10.2.45911 > 169.150.196.2.51820: UDP, length 96 19:16:52.244292 enp7s0 Out IP 192.168.1.87.45911 > 169.150.196.2.51820: UDP, length 96 19:16:52.423543 veth43b1168 P IP 172.16.3.2.60714 > 104.21.32.1.51820: UDP, length 148 19:16:52.423543 br-6195d43a8398 In IP 172.16.3.2.60714 > 104.21.32.1.51820: UDP, length 148 19:16:52.423593 enp7s0 Out IP 192.168.1.87.60714 > 104.21.32.1.51820: UDP, length 148 ^C 345 packets captured 347 packets received by filter 0 packets dropped by kernel ```
GiteaMirror commented 2025-11-13 12:00:36 -06:00
Author
Owner
Copy Link

@cezarq commented on GitHub (Jun 16, 2025):

Same error here:
newt | WARN: 2025/06/16 01:16:24 Ping attempt 172 failed: failed to read ICMP packet: i/o timeout
newt | WARN: 2025/06/16 01:16:24 Ping attempt 63 failed: failed to read ICMP packet: i/o timeout
newt | WARN: 2025/06/16 01:16:24 Ping attempt 480 failed: failed to read ICMP packet: i/o timeout
newt | WARN: 2025/06/16 01:16:26 Ping attempt 479 failed: failed to read ICMP packet: i/o timeout
newt | INFO: 2025/06/16 01:16:26 Pinging 100.89.128.1

@cezarq commented on GitHub (Jun 16, 2025): Same error here: newt | WARN: 2025/06/16 01:16:24 Ping attempt 172 failed: failed to read ICMP packet: i/o timeout newt | WARN: 2025/06/16 01:16:24 Ping attempt 63 failed: failed to read ICMP packet: i/o timeout newt | WARN: 2025/06/16 01:16:24 Ping attempt 480 failed: failed to read ICMP packet: i/o timeout newt | WARN: 2025/06/16 01:16:26 Ping attempt 479 failed: failed to read ICMP packet: i/o timeout newt | INFO: 2025/06/16 01:16:26 Pinging 100.89.128.1
GiteaMirror commented 2025-11-13 12:00:36 -06:00
Author
Owner
Copy Link

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

@cezarq could you triple check port UDP 51820 is open on BOTH the VPS firewall from the provider if there is one and in linux with UFW/iptables/nftables?

@Blucose sounds like you did the dump on Truenas running newt and not from the VPS? Could you do it from the VPS to make sure the wg traffic is making it there?

@oschwartz10612 commented on GitHub (Jun 16, 2025): @cezarq could you triple check port UDP 51820 is open on BOTH the VPS firewall from the provider if there is one and in linux with UFW/iptables/nftables? @Blucose sounds like you did the dump on Truenas running newt and not from the VPS? Could you do it from the VPS to make sure the wg traffic is making it there?
GiteaMirror commented 2025-11-13 12:00:36 -06:00
Author
Owner
Copy Link

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

Also if you use CF you have CF proxy off because it obscures the IP of the VPS and WG traffic cant get through. If you need to use CF proxy you can set the base_endpoint section of the gerbil config file to have the IP of the VPS and it should work for you.

@oschwartz10612 commented on GitHub (Jun 16, 2025): Also if you use CF you have CF proxy off because it obscures the IP of the VPS and WG traffic cant get through. If you need to use CF proxy you can set the base_endpoint section of the gerbil config file to have the IP of the VPS and it should work for you.
GiteaMirror commented 2025-11-13 12:00:36 -06:00
Author
Owner
Copy Link

@cezarq commented on GitHub (Jun 16, 2025):

@cezarq could you triple check port UDP 51820 is open on BOTH the VPS firewall from the provider if there is one and in linux with UFW/iptables/nftables?

@Blucose sounds like you did the dump on Truenas running newt and not from the VPS? Could you do it from the VPS to make sure the wg traffic is making it there?

# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
ACCEPT     all  --  anywhere             anywhere             state RELATED,ESTABLISHED
ACCEPT     icmp --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     udp  --  anywhere             anywhere             udp spt:ntp
ACCEPT     tcp  --  anywhere             anywhere             state NEW tcp dpt:ssh
ACCEPT     tcp  --  anywhere             anywhere             state NEW tcp dpt:zabbix-agent
REJECT     all  --  anywhere             anywhere             reject-with icmp-host-prohibited
LOG        all  --  anywhere             anywhere             LOG level warning

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         
DOCKER-USER  all  --  anywhere             anywhere            
DOCKER-ISOLATION-STAGE-1  all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            
REJECT     all  --  anywhere             anywhere             reject-with icmp-host-prohibited
LOG        all  --  anywhere             anywhere             LOG level warning prefix "iptables: "

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         
InstanceServices  all  --  anywhere             link-local/16       

Chain DOCKER (4 references)
target     prot opt source               destination         
ACCEPT     tcp  --  anywhere             172.17.0.4           tcp dpt:9001
ACCEPT     tcp  --  anywhere             172.20.0.2           tcp dpt:http
ACCEPT     tcp  --  anywhere             172.18.0.3           tcp dpt:http
ACCEPT     tcp  --  anywhere             172.18.0.3           tcp dpt:https
ACCEPT     udp  --  anywhere             172.18.0.3           udp dpt:51820
ACCEPT     tcp  --  anywhere             172.18.0.4           tcp dpt:5100

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
target     prot opt source               destination         
DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere            
DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere            
DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere            
DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere            
RETURN     all  --  anywhere             anywhere            

Chain DOCKER-ISOLATION-STAGE-2 (4 references)
target     prot opt source               destination         
DROP       all  --  anywhere             anywhere            
DROP       all  --  anywhere             anywhere            
DROP       all  --  anywhere             anywhere            
DROP       all  --  anywhere             anywhere            
RETURN     all  --  anywhere             anywhere            

Chain DOCKER-USER (1 references)
target     prot opt source               destination         
RETURN     all  --  anywhere             anywhere

NEWT Client log:

INFO: 2025/06/16 13:53:27 Newt version 1.2.1
INFO: 2025/06/16 13:53:29 Sent registration message
INFO: 2025/06/16 13:53:29 Received registration message
INFO: 2025/06/16 13:53:29 Received: {Type:newt/wg/connect Data:map[endpoint:pangolin.xxxxx.com.xx:51820 publicKey:qpAF5/aYH/hpSSWJis5CvOWSu/QyDx7hqqXqIaUagxw= serverIP:100.89.128.1 targets:map[tcp:[] udp:[]] tunnelIP:100.89.128.4]}
INFO: 2025/06/16 13:53:29 WireGuard device created. Lets ping the server now...
INFO: 2025/06/16 13:53:29 Ping attempt 1
INFO: 2025/06/16 13:53:29 Pinging 100.89.128.1
WARN: 2025/06/16 13:53:39 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/06/16 13:53:39 Starting ping check
INFO: 2025/06/16 13:53:39 Ping attempt 2
INFO: 2025/06/16 13:53:39 Pinging 100.89.128.1
WARN: 2025/06/16 13:53:49 Ping attempt 2 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/06/16 13:53:51 Ping attempt 3
INFO: 2025/06/16 13:53:51 Pinging 100.89.128.1
@cezarq commented on GitHub (Jun 16, 2025): > [@cezarq](https://github.com/cezarq) could you triple check port UDP 51820 is open on BOTH the VPS firewall from the provider if there is one and in linux with UFW/iptables/nftables? > > [@Blucose](https://github.com/Blucose) sounds like you did the dump on Truenas running newt and not from the VPS? Could you do it from the VPS to make sure the wg traffic is making it there? ``` # iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT icmp -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT udp -- anywhere anywhere udp spt:ntp ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:zabbix-agent REJECT all -- anywhere anywhere reject-with icmp-host-prohibited LOG all -- anywhere anywhere LOG level warning Chain FORWARD (policy ACCEPT) target prot opt source destination DOCKER-USER all -- anywhere anywhere DOCKER-ISOLATION-STAGE-1 all -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED DOCKER all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED DOCKER all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED DOCKER all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED DOCKER all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere REJECT all -- anywhere anywhere reject-with icmp-host-prohibited LOG all -- anywhere anywhere LOG level warning prefix "iptables: " Chain OUTPUT (policy ACCEPT) target prot opt source destination InstanceServices all -- anywhere link-local/16 Chain DOCKER (4 references) target prot opt source destination ACCEPT tcp -- anywhere 172.17.0.4 tcp dpt:9001 ACCEPT tcp -- anywhere 172.20.0.2 tcp dpt:http ACCEPT tcp -- anywhere 172.18.0.3 tcp dpt:http ACCEPT tcp -- anywhere 172.18.0.3 tcp dpt:https ACCEPT udp -- anywhere 172.18.0.3 udp dpt:51820 ACCEPT tcp -- anywhere 172.18.0.4 tcp dpt:5100 Chain DOCKER-ISOLATION-STAGE-1 (1 references) target prot opt source destination DOCKER-ISOLATION-STAGE-2 all -- anywhere anywhere DOCKER-ISOLATION-STAGE-2 all -- anywhere anywhere DOCKER-ISOLATION-STAGE-2 all -- anywhere anywhere DOCKER-ISOLATION-STAGE-2 all -- anywhere anywhere RETURN all -- anywhere anywhere Chain DOCKER-ISOLATION-STAGE-2 (4 references) target prot opt source destination DROP all -- anywhere anywhere DROP all -- anywhere anywhere DROP all -- anywhere anywhere DROP all -- anywhere anywhere RETURN all -- anywhere anywhere Chain DOCKER-USER (1 references) target prot opt source destination RETURN all -- anywhere anywhere ``` NEWT Client log: ``` INFO: 2025/06/16 13:53:27 Newt version 1.2.1 INFO: 2025/06/16 13:53:29 Sent registration message INFO: 2025/06/16 13:53:29 Received registration message INFO: 2025/06/16 13:53:29 Received: {Type:newt/wg/connect Data:map[endpoint:pangolin.xxxxx.com.xx:51820 publicKey:qpAF5/aYH/hpSSWJis5CvOWSu/QyDx7hqqXqIaUagxw= serverIP:100.89.128.1 targets:map[tcp:[] udp:[]] tunnelIP:100.89.128.4]} INFO: 2025/06/16 13:53:29 WireGuard device created. Lets ping the server now... INFO: 2025/06/16 13:53:29 Ping attempt 1 INFO: 2025/06/16 13:53:29 Pinging 100.89.128.1 WARN: 2025/06/16 13:53:39 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout INFO: 2025/06/16 13:53:39 Starting ping check INFO: 2025/06/16 13:53:39 Ping attempt 2 INFO: 2025/06/16 13:53:39 Pinging 100.89.128.1 WARN: 2025/06/16 13:53:49 Ping attempt 2 failed: failed to read ICMP packet: i/o timeout INFO: 2025/06/16 13:53:51 Ping attempt 3 INFO: 2025/06/16 13:53:51 Pinging 100.89.128.1 ```
GiteaMirror commented 2025-11-13 12:00:37 -06:00
Author
Owner
Copy Link

@Blucose commented on GitHub (Jun 16, 2025):

I've got mine working. For me the issue was that the Docker Socket Integration - it wasn't failing gracefully.
When setting up Newt in the UI, if I turn off the toggle for Docker Sock, everything works.
Not sure if there is some bug, or if it is interfering with tailscale or komodo or something..?

@Blucose commented on GitHub (Jun 16, 2025): I've got mine working. For me the issue was that the Docker Socket Integration - it wasn't failing gracefully. When setting up Newt in the UI, if I turn off the toggle for Docker Sock, everything works. Not sure if there is some bug, or if it is interfering with tailscale or komodo or something..?
GiteaMirror commented 2025-11-13 12:00:37 -06:00
Author
Owner
Copy Link

@cezarq commented on GitHub (Jun 16, 2025):

I've got mine working. For me the issue was that the Docker Socket Integration - it wasn't failing gracefully. When setting up Newt in the UI, if I turn off the toggle for Docker Sock, everything works. Not sure if there is some bug, or if it is interfering with tailscale or komodo or something..?

@Blucose did you just disable the Docker Socket?

@cezarq commented on GitHub (Jun 16, 2025): > I've got mine working. For me the issue was that the Docker Socket Integration - it wasn't failing gracefully. When setting up Newt in the UI, if I turn off the toggle for Docker Sock, everything works. Not sure if there is some bug, or if it is interfering with tailscale or komodo or something..? @Blucose did you just disable the Docker Socket?
GiteaMirror commented 2025-11-13 12:00:37 -06:00
Author
Owner
Copy Link

@Blucose commented on GitHub (Jun 16, 2025):

Image

Just did this and it worked. Might investigate later what is causing it to break... but right now just happy it works!

@Blucose commented on GitHub (Jun 16, 2025): ![Image](https://github.com/user-attachments/assets/7c7f3c12-d7a6-4b6e-b217-c54fcd68d48b) Just did this and it worked. Might investigate later what is causing it to break... but right now just happy it works!
GiteaMirror commented 2025-11-13 12:00:37 -06:00
Author
Owner
Copy Link

@cezarq commented on GitHub (Jun 16, 2025):

Didnt work for me :-(
Thanks anyway @Blucose

Image

@cezarq commented on GitHub (Jun 16, 2025): Didnt work for me :-( Thanks anyway @Blucose ![Image](https://github.com/user-attachments/assets/e9cc63d6-9c76-4d72-b105-78f8d2a0de4b)
GiteaMirror commented 2025-11-13 12:00:38 -06:00
Author
Owner
Copy Link

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

@Blucose do you have a firewall on the VPS? Who is your provider? Some VPS providers require you to open ports through their UI.

Also double check gerbil is starting correctly but sounds like it is. You could post some log outputs.

Is it possible the network that newt is on is blocking wireguard traffic?

@oschwartz10612 commented on GitHub (Jun 17, 2025): @Blucose do you have a firewall on the VPS? Who is your provider? Some VPS providers require you to open ports through their UI. Also double check gerbil is starting correctly but sounds like it is. You could post some log outputs. Is it possible the network that newt is on is blocking wireguard traffic?
GiteaMirror commented 2025-11-13 12:00:38 -06:00
Author
Owner
Copy Link

@cezarq commented on GitHub (Jun 17, 2025):

@oschwartz10612, taking advantage of the question, I am using Oracle Cloud (OCI).

@cezarq commented on GitHub (Jun 17, 2025): @oschwartz10612, taking advantage of the question, I am using Oracle Cloud (OCI).
GiteaMirror commented 2025-11-13 12:00:39 -06:00
Author
Owner
Copy Link

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

Oh I know some people have had issues with Oracle in the past. Could you take a look at the bottom comments on these two issues and see if it helps?

https://github.com/fosrl/pangolin/issues/818
https://github.com/fosrl/pangolin/issues/889

@oschwartz10612 commented on GitHub (Jun 17, 2025): Oh I know some people have had issues with Oracle in the past. Could you take a look at the bottom comments on these two issues and see if it helps? https://github.com/fosrl/pangolin/issues/818 https://github.com/fosrl/pangolin/issues/889
GiteaMirror commented 2025-11-13 12:00:39 -06:00
Author
Owner
Copy Link

@cezarq commented on GitHub (Jun 17, 2025):

@oschwartz10612 , no luck! What is weird is that was working 5 days ago perfectly and now I cant go online and I have no idea the reason.

Image

Image

Image

Gerbil log:

INFO: 2025/06/16 14:19:51 Fetching remote config from http://pangolin:3001/api/v1/gerbil/get-config
INFO: 2025/06/16 14:19:51 Created WireGuard interface wg0
INFO: 2025/06/16 14:19:51 Assigned IP address 100.89.128.1/24 to interface wg0
INFO: 2025/06/16 14:19:51 Attempting to delete existing MSS clamping rule for chain INPUT
INFO: 2025/06/16 14:19:51 Attempting to delete existing MSS clamping rule for chain OUTPUT
INFO: 2025/06/16 14:19:51 Attempting to delete existing MSS clamping rule for chain FORWARD
INFO: 2025/06/16 14:19:51 Adding MSS clamping rule for chain INPUT
INFO: 2025/06/16 14:19:51 Successfully added and verified MSS clamping rule for chain INPUT
INFO: 2025/06/16 14:19:51 Adding MSS clamping rule for chain OUTPUT
INFO: 2025/06/16 14:19:51 Successfully added and verified MSS clamping rule for chain OUTPUT
INFO: 2025/06/16 14:19:51 Adding MSS clamping rule for chain FORWARD
INFO: 2025/06/16 14:19:51 Successfully added and verified MSS clamping rule for chain FORWARD
INFO: 2025/06/16 14:19:51 WireGuard interface wg0 created and configured
INFO: 2025/06/16 14:19:51 Peer Wb76KOipL2OhEsLVIb5Pcsnl3R185WvGFRJETVUNxDg= added successfully
INFO: 2025/06/16 14:19:51 Starting server on :3003
INFO: 2025/06/16 14:20:00 Peer Wb76KOipL2OhEsLVIb5Pcsnl3R185WvGFRJETVUNxDg= added successfully
INFO: 2025/06/16 14:23:00 Peer Wb76KOipL2OhEsLVIb5Pcsnl3R185WvGFRJETVUNxDg= removed successfully
INFO: 2025/06/16 14:23:00 Peer 8PQnSQvazPA5KBCeXE9g++6uWQZVayVKFVH6E3nTNXs= added successfully

Pangolin log:

2025-06-17T10:59:28.092Z [info]: Establishing websocket connection
2025-06-17T10:59:28.092Z [info]: Client added to tracking - Newt ID: 4o5xs9h2jrmf9m4, Total connections: 2
2025-06-17T10:59:28.092Z [info]: WebSocket connection established - Newt ID: 4o5xs9h2jrmxxxx
2025-06-17T10:59:28.295Z [info]: Handling register message!
2025-06-17T10:59:28.305Z [info]: Peer added successfully: {"peer":"Peer added successfully"}
2025-06-17T11:00:36.782Z [info]: Connection removed - Newt ID: 4o5xs9h2jrmxxxx, Remaining connections: 1
2025-06-17T11:00:36.782Z [info]: Client disconnected - Newt ID: 4o5xs9h2jrmxxxx

Traefik log:```

2025-06-16T14:19:52Z INF Traefik version 3.4.1 built on 2025-05-27T12:45:13Z version=3.4.1
2025-06-16T14:19:52Z INF
Stats collection is disabled.
Help us improve Traefik by turning this feature on :)
More details on: https://doc.traefik.io/traefik/contributing/data-collection/
2025-06-16T14:19:52Z INF Loading plugins... plugins=["badger"]
2025-06-16T14:19:52Z INF Plugins loaded. plugins=["badger"]
2025-06-16T14:19:52Z INF Starting provider aggregator *aggregator.ProviderAggregator
2025-06-16T14:19:52Z INF Starting provider *file.Provider
2025-06-16T14:19:52Z INF Starting provider *traefik.Provider
2025-06-16T14:19:52Z INF Starting provider *http.Provider
2025-06-16T14:19:52Z INF Starting provider *acme.ChallengeTLSALPN
2025-06-16T14:19:52Z INF Starting provider *acme.Provider
2025-06-16T14:19:52Z INF Testing certificate renew... acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=letsencrypt.acme

@cezarq commented on GitHub (Jun 17, 2025): @oschwartz10612 , no luck! What is weird is that was working 5 days ago perfectly and now I cant go online and I have no idea the reason. ![Image](https://github.com/user-attachments/assets/619871e9-9643-4d14-9a73-af69a9181bf8) ![Image](https://github.com/user-attachments/assets/34158271-ba22-4e01-b755-2e69fdc0ace5) ![Image](https://github.com/user-attachments/assets/8150dbc5-6ef6-48cd-ac73-f9d9f7e1f9e7) Gerbil log: ``` INFO: 2025/06/16 14:19:51 Fetching remote config from http://pangolin:3001/api/v1/gerbil/get-config INFO: 2025/06/16 14:19:51 Created WireGuard interface wg0 INFO: 2025/06/16 14:19:51 Assigned IP address 100.89.128.1/24 to interface wg0 INFO: 2025/06/16 14:19:51 Attempting to delete existing MSS clamping rule for chain INPUT INFO: 2025/06/16 14:19:51 Attempting to delete existing MSS clamping rule for chain OUTPUT INFO: 2025/06/16 14:19:51 Attempting to delete existing MSS clamping rule for chain FORWARD INFO: 2025/06/16 14:19:51 Adding MSS clamping rule for chain INPUT INFO: 2025/06/16 14:19:51 Successfully added and verified MSS clamping rule for chain INPUT INFO: 2025/06/16 14:19:51 Adding MSS clamping rule for chain OUTPUT INFO: 2025/06/16 14:19:51 Successfully added and verified MSS clamping rule for chain OUTPUT INFO: 2025/06/16 14:19:51 Adding MSS clamping rule for chain FORWARD INFO: 2025/06/16 14:19:51 Successfully added and verified MSS clamping rule for chain FORWARD INFO: 2025/06/16 14:19:51 WireGuard interface wg0 created and configured INFO: 2025/06/16 14:19:51 Peer Wb76KOipL2OhEsLVIb5Pcsnl3R185WvGFRJETVUNxDg= added successfully INFO: 2025/06/16 14:19:51 Starting server on :3003 INFO: 2025/06/16 14:20:00 Peer Wb76KOipL2OhEsLVIb5Pcsnl3R185WvGFRJETVUNxDg= added successfully INFO: 2025/06/16 14:23:00 Peer Wb76KOipL2OhEsLVIb5Pcsnl3R185WvGFRJETVUNxDg= removed successfully INFO: 2025/06/16 14:23:00 Peer 8PQnSQvazPA5KBCeXE9g++6uWQZVayVKFVH6E3nTNXs= added successfully ``` Pangolin log: ``` 2025-06-17T10:59:28.092Z [info]: Establishing websocket connection 2025-06-17T10:59:28.092Z [info]: Client added to tracking - Newt ID: 4o5xs9h2jrmf9m4, Total connections: 2 2025-06-17T10:59:28.092Z [info]: WebSocket connection established - Newt ID: 4o5xs9h2jrmxxxx 2025-06-17T10:59:28.295Z [info]: Handling register message! 2025-06-17T10:59:28.305Z [info]: Peer added successfully: {"peer":"Peer added successfully"} 2025-06-17T11:00:36.782Z [info]: Connection removed - Newt ID: 4o5xs9h2jrmxxxx, Remaining connections: 1 2025-06-17T11:00:36.782Z [info]: Client disconnected - Newt ID: 4o5xs9h2jrmxxxx ``` Traefik log:``` 2025-06-16T14:19:52Z INF Traefik version 3.4.1 built on 2025-05-27T12:45:13Z version=3.4.1 2025-06-16T14:19:52Z INF Stats collection is disabled. Help us improve Traefik by turning this feature on :) More details on: https://doc.traefik.io/traefik/contributing/data-collection/ 2025-06-16T14:19:52Z INF Loading plugins... plugins=["badger"] 2025-06-16T14:19:52Z INF Plugins loaded. plugins=["badger"] 2025-06-16T14:19:52Z INF Starting provider aggregator *aggregator.ProviderAggregator 2025-06-16T14:19:52Z INF Starting provider *file.Provider 2025-06-16T14:19:52Z INF Starting provider *traefik.Provider 2025-06-16T14:19:52Z INF Starting provider *http.Provider 2025-06-16T14:19:52Z INF Starting provider *acme.ChallengeTLSALPN 2025-06-16T14:19:52Z INF Starting provider *acme.Provider 2025-06-16T14:19:52Z INF Testing certificate renew... acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=letsencrypt.acme ```
GiteaMirror commented 2025-11-13 12:00:39 -06:00
Author
Owner
Copy Link

@cezarq commented on GitHub (Jun 17, 2025):

Pangolin agent:

INFO: 2025/06/17 14:21:20 Newt version 1.2.1
INFO: 2025/06/17 14:21:21 Sent registration message
INFO: 2025/06/17 14:21:21 Received registration message
INFO: 2025/06/17 14:21:21 Received: {Type:newt/wg/connect Data:map[endpoint:pangolin.XXXXXX.com.xx:51820 publicKey:qpAF5/aYH/hpSSWJis5CvOWSu/QyDx7hqqXqIaXxxxw= serverIP:100.89.128.1 targets:map[tcp:[] udp:[]] tunnelIP:100.89.128.4]}
INFO: 2025/06/17 14:21:21 WireGuard device created. Lets ping the server now...
INFO: 2025/06/17 14:21:21 Ping attempt 1
INFO: 2025/06/17 14:21:21 Pinging 100.89.128.1
WARN: 2025/06/17 14:21:31 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/06/17 14:21:31 Starting ping check
INFO: 2025/06/17 14:21:31 Ping attempt 2
INFO: 2025/06/17 14:21:31 Pinging 100.89.128.1
WARN: 2025/06/17 14:21:41 Ping attempt 2 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/06/17 14:21:43 Ping attempt 3
INFO: 2025/06/17 14:21:43 Pinging 100.89.128.1
@cezarq commented on GitHub (Jun 17, 2025): Pangolin agent: ``` INFO: 2025/06/17 14:21:20 Newt version 1.2.1 INFO: 2025/06/17 14:21:21 Sent registration message INFO: 2025/06/17 14:21:21 Received registration message INFO: 2025/06/17 14:21:21 Received: {Type:newt/wg/connect Data:map[endpoint:pangolin.XXXXXX.com.xx:51820 publicKey:qpAF5/aYH/hpSSWJis5CvOWSu/QyDx7hqqXqIaXxxxw= serverIP:100.89.128.1 targets:map[tcp:[] udp:[]] tunnelIP:100.89.128.4]} INFO: 2025/06/17 14:21:21 WireGuard device created. Lets ping the server now... INFO: 2025/06/17 14:21:21 Ping attempt 1 INFO: 2025/06/17 14:21:21 Pinging 100.89.128.1 WARN: 2025/06/17 14:21:31 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout INFO: 2025/06/17 14:21:31 Starting ping check INFO: 2025/06/17 14:21:31 Ping attempt 2 INFO: 2025/06/17 14:21:31 Pinging 100.89.128.1 WARN: 2025/06/17 14:21:41 Ping attempt 2 failed: failed to read ICMP packet: i/o timeout INFO: 2025/06/17 14:21:43 Ping attempt 3 INFO: 2025/06/17 14:21:43 Pinging 100.89.128.1 ```
GiteaMirror commented 2025-11-13 12:00:39 -06:00
Author
Owner
Copy Link

@cezarq commented on GitHub (Jun 17, 2025):

I dont know if is relevant, but I have a local site configured and is working fine with a service running on the OCI as docker.

Image

@cezarq commented on GitHub (Jun 17, 2025): I dont know if is relevant, but I have a local site configured and is working fine with a service running on the OCI as docker. ![Image](https://github.com/user-attachments/assets/952e30ca-225b-4fba-905a-60a424d97d94)
GiteaMirror commented 2025-11-13 12:00:40 -06:00
Author
Owner
Copy Link

@cezarq commented on GitHub (Jun 17, 2025):

I figured out! It was the Cloudflare DNS Proxy. After disabled this feature, back online again.... thanks guys...

@cezarq commented on GitHub (Jun 17, 2025): I figured out! It was the Cloudflare DNS Proxy. After disabled this feature, back online again.... thanks guys...
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
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/pangolin#439
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?