Error while handling UDP stream #1780

Closed
opened 2026-04-05 19:41:42 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @Lokowitz on 2/15/2025

I have pangolin on a vps and newt on a proxmox machine in my homelab and in my fathers homelab.
I don't have any issues with my fathers connection but from time to time the connection to my homelab is broken.
I can not reproduce this scenario... :(

  1. Newt lost the connection
  2. docker compose down and up did not solved the connection problem, so i rebooted the newt machine (LXC)
  3. connection was succesfull but with "invalid target format null:null" so my UDP stream and HTTPS still not worked.
  4. disabled and enabled the targets in pangolin to resync with newt and then it worked again.

It is the secound time i have this problem.

Newt Log

INFO: 2025/02/14 23:34:35 Already connected! But I will send a ping anyway...
INFO: 2025/02/14 23:34:35 Ping attempt 1 of 5
INFO: 2025/02/14 23:34:35 Pinging 100.89.128.1
WARN: 2025/02/14 23:34:45 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/02/14 23:34:47 Ping attempt 2 of 5
INFO: 2025/02/14 23:34:47 Pinging 100.89.128.1
WARN: 2025/02/14 23:34:57 Ping attempt 2 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/02/14 23:34:59 Ping attempt 3 of 5
INFO: 2025/02/14 23:34:59 Pinging 100.89.128.1
WARN: 2025/02/14 23:35:09 Ping attempt 3 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/02/14 23:35:11 Ping attempt 4 of 5
INFO: 2025/02/14 23:35:11 Pinging 100.89.128.1
WARN: 2025/02/14 23:35:21 Ping attempt 4 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/02/14 23:35:23 Ping attempt 5 of 5
INFO: 2025/02/14 23:35:23 Pinging 100.89.128.1
WARN: 2025/02/14 23:35:33 Ping attempt 5 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/02/14 23:35:33 Failed to ping 100.89.128.1: all ping attempts failed after 5 tries, last error: failed to read ICMP packet: i/o timeout
WARN: 2025/02/14 23:35:33 HINT: Do you have UDP port 51280 (or the port in config.yml) open on your Pangolin server?
INFO: 2025/02/15 07:56:34 Sent registration message
INFO: 2025/02/15 07:56:34 Received registration message
INFO: 2025/02/15 07:56:34 Received: {Type:newt/wg/connect Data:map[endpoint:my.domain:44400 publicKey:---key---- serverIP:100.89.128.1 targets:map[tcp:[null:null] udp:[null:null 45964:192.168.10.32:10090]] tunnelIP:100.89.128.4]}
INFO: 2025/02/15 07:56:34 WireGuard device created. Lets ping the server now...
INFO: 2025/02/15 07:56:34 Ping attempt 1 of 5
INFO: 2025/02/15 07:56:34 Pinging 100.89.128.1
INFO: 2025/02/15 07:56:34 Ping latency: 57.496664ms
INFO: 2025/02/15 07:56:34 Starting ping check
INFO: 2025/02/15 07:56:34 Invalid target format: null:null
INFO: 2025/02/15 07:56:34 Invalid target format: null:null
INFO: 2025/02/15 07:56:34 Not adding target because not running
INFO: 2025/02/15 07:56:34 Started udp proxy from 100.89.128.4:45964 to 192.168.10.32:10090
INFO: 2025/02/15 08:00:29 Received: {Type:newt/udp/add Data:map[targets:[55851:192.168.10.5:10091]]}
INFO: 2025/02/15 08:00:29 Started udp proxy from 100.89.128.4:55851 to 192.168.10.5:10091
INFO: 2025/02/15 08:00:46 Received: {Type:newt/udp/add Data:map[targets:[54486:192.168.10.5:10091]]}

Traefik Log

traefik   | 2025-02-15T09:00:11+01:00 ERR Error while handling UDP stream error="read udp 100.89.128.1:56889->100.89.128.4:46533: read: connection refused"
traefik   | 2025-02-15T09:00:17+01:00 ERR Error while handling UDP stream error="read udp 100.89.128.1:38761->100.89.128.4:46533: read: connection refused"
traefik   | 2025-02-15T09:00:23+01:00 ERR Error while handling UDP stream error="read udp 100.89.128.1:45171->100.89.128.4:46533: read: connection refused"
traefik   | 2025-02-15T09:00:28+01:00 ERR Error while handling UDP stream error="read udp 100.89.128.1:59707->100.89.128.4:46533: read: connection refused"
traefik   | 2025-02-15T09:00:33+01:00 ERR Error while handling UDP stream error="read udp 100.89.128.1:52478->100.89.128.4:46533: read: connection refused"
*Originally created by @Lokowitz on 2/15/2025* I have pangolin on a vps and newt on a proxmox machine in my homelab and in my fathers homelab. I don't have any issues with my fathers connection but from time to time the connection to my homelab is broken. I can not reproduce this scenario... :( 1. Newt lost the connection 2. docker compose down and up did not solved the connection problem, so i rebooted the newt machine (LXC) 3. connection was succesfull but with "invalid target format null:null" so my UDP stream and HTTPS still not worked. 4. disabled and enabled the targets in pangolin to resync with newt and then it worked again. It is the secound time i have this problem. ## Newt Log ``` INFO: 2025/02/14 23:34:35 Already connected! But I will send a ping anyway... INFO: 2025/02/14 23:34:35 Ping attempt 1 of 5 INFO: 2025/02/14 23:34:35 Pinging 100.89.128.1 WARN: 2025/02/14 23:34:45 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout INFO: 2025/02/14 23:34:47 Ping attempt 2 of 5 INFO: 2025/02/14 23:34:47 Pinging 100.89.128.1 WARN: 2025/02/14 23:34:57 Ping attempt 2 failed: failed to read ICMP packet: i/o timeout INFO: 2025/02/14 23:34:59 Ping attempt 3 of 5 INFO: 2025/02/14 23:34:59 Pinging 100.89.128.1 WARN: 2025/02/14 23:35:09 Ping attempt 3 failed: failed to read ICMP packet: i/o timeout INFO: 2025/02/14 23:35:11 Ping attempt 4 of 5 INFO: 2025/02/14 23:35:11 Pinging 100.89.128.1 WARN: 2025/02/14 23:35:21 Ping attempt 4 failed: failed to read ICMP packet: i/o timeout INFO: 2025/02/14 23:35:23 Ping attempt 5 of 5 INFO: 2025/02/14 23:35:23 Pinging 100.89.128.1 WARN: 2025/02/14 23:35:33 Ping attempt 5 failed: failed to read ICMP packet: i/o timeout WARN: 2025/02/14 23:35:33 Failed to ping 100.89.128.1: all ping attempts failed after 5 tries, last error: failed to read ICMP packet: i/o timeout WARN: 2025/02/14 23:35:33 HINT: Do you have UDP port 51280 (or the port in config.yml) open on your Pangolin server? INFO: 2025/02/15 07:56:34 Sent registration message INFO: 2025/02/15 07:56:34 Received registration message INFO: 2025/02/15 07:56:34 Received: {Type:newt/wg/connect Data:map[endpoint:my.domain:44400 publicKey:---key---- serverIP:100.89.128.1 targets:map[tcp:[null:null] udp:[null:null 45964:192.168.10.32:10090]] tunnelIP:100.89.128.4]} INFO: 2025/02/15 07:56:34 WireGuard device created. Lets ping the server now... INFO: 2025/02/15 07:56:34 Ping attempt 1 of 5 INFO: 2025/02/15 07:56:34 Pinging 100.89.128.1 INFO: 2025/02/15 07:56:34 Ping latency: 57.496664ms INFO: 2025/02/15 07:56:34 Starting ping check INFO: 2025/02/15 07:56:34 Invalid target format: null:null INFO: 2025/02/15 07:56:34 Invalid target format: null:null INFO: 2025/02/15 07:56:34 Not adding target because not running INFO: 2025/02/15 07:56:34 Started udp proxy from 100.89.128.4:45964 to 192.168.10.32:10090 INFO: 2025/02/15 08:00:29 Received: {Type:newt/udp/add Data:map[targets:[55851:192.168.10.5:10091]]} INFO: 2025/02/15 08:00:29 Started udp proxy from 100.89.128.4:55851 to 192.168.10.5:10091 INFO: 2025/02/15 08:00:46 Received: {Type:newt/udp/add Data:map[targets:[54486:192.168.10.5:10091]]} ``` ## Traefik Log ``` traefik | 2025-02-15T09:00:11+01:00 ERR Error while handling UDP stream error="read udp 100.89.128.1:56889->100.89.128.4:46533: read: connection refused" traefik | 2025-02-15T09:00:17+01:00 ERR Error while handling UDP stream error="read udp 100.89.128.1:38761->100.89.128.4:46533: read: connection refused" traefik | 2025-02-15T09:00:23+01:00 ERR Error while handling UDP stream error="read udp 100.89.128.1:45171->100.89.128.4:46533: read: connection refused" traefik | 2025-02-15T09:00:28+01:00 ERR Error while handling UDP stream error="read udp 100.89.128.1:59707->100.89.128.4:46533: read: connection refused" traefik | 2025-02-15T09:00:33+01:00 ERR Error while handling UDP stream error="read udp 100.89.128.1:52478->100.89.128.4:46533: read: connection refused" ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#1780