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

[GH-ISSUE #87] Getting Unsupported message type: newt/ping/request #497

New Issue
Closed
opened 2026-04-16 03:28:15 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-16 03:28:15 -05:00
Owner
Copy Link
Copy Source

Originally created by @dparv on GitHub (Jul 15, 2025).
Original GitHub issue: https://github.com/fosrl/newt/issues/87

Testing a simple config I am getting the following error from pangolin:

2025-07-15T11:36:44.880Z [info]: Public key mismatch. Deleting old peer...
2025-07-15T11:36:44.895Z [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-07-15T11:36:44.903Z [info]: Peer added successfully: {"peer":"Peer added successfully"}
asd2025-07-15T11:36:51.641Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:37:01.647Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:37:11.651Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:37:21.640Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:37:31.647Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:37:41.644Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:37:51.648Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:38:01.643Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:38:11.645Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:38:21.656Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:38:31.643Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:38:41.646Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:38:51.651Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:39:01.652Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:39:06.252Z [error]: Message handling error: Unsupported message type: newt/ping/request
Stack: Error: Unsupported message type: newt/ping/request
    at WebSocket.<anonymous> (file:///app/dist/server.mjs:21:40731)
    at WebSocket.emit (node:events:524:28)
    at Receiver.receiverOnMessage (/app/node_modules/ws/lib/websocket.js:1220:20)
    at Receiver.emit (node:events:524:28)
    at Receiver.dataMessage (/app/node_modules/ws/lib/receiver.js:596:14)
    at Receiver.getData (/app/node_modules/ws/lib/receiver.js:496:10)
    at Receiver.startLoop (/app/node_modules/ws/lib/receiver.js:167:16)
    at Receiver._write (/app/node_modules/ws/lib/receiver.js:94:10)
    at writeOrBuffer (node:internal/streams/writable:572:12)
    at _write (node:internal/streams/writable:501:10)
2025-07-15T11:39:06.255Z [info]: Handling register message!
2025-07-15T11:39:06.292Z [info]: Peer added successfully: {"peer":"Peer added successfully"}
2025-07-15T11:39:11.647Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:39:21.646Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:39:31.645Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:39:41.665Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:39:51.644Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:40:01.650Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:40:11.652Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=
2025-07-15T11:40:21.642Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g=

and newt is reporting

INFO: 2025/07/15 14:36:44 Newt version 1.3.2
INFO: 2025/07/15 14:36:44 Websocket connected
INFO: 2025/07/15 14:36:44 Requesting exit nodes from server
INFO: 2025/07/15 14:36:44 Received registration message
INFO: 2025/07/15 14:36:44 Connecting to endpoint: pangolin.my.domain.com
WARN: 2025/07/15 14:37:15 Initial reliable ping failed, but continuing: all 5 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:37:20 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:37:25 Ping attempt 2 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:37:32 Ping attempt 3 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:37:39 Ping attempt 4 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:37:46 Ping attempt 5 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/07/15 14:37:46 Increasing ping retry delay to 3s
WARN: 2025/07/15 14:37:54 Ping attempt 6 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:38:02 Ping attempt 7 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:38:04 Periodic ping failed (2 consecutive failures): all 2 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:38:10 Ping attempt 8 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:38:18 Ping attempt 9 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:38:26 Ping attempt 10 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/07/15 14:38:26 Increasing ping retry delay to 4.5s
WARN: 2025/07/15 14:38:35 Periodic ping failed (3 consecutive failures): all 2 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:38:36 Ping attempt 11 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:38:45 Ping attempt 12 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:38:55 Ping attempt 13 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:39:04 Ping attempt 14 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:39:06 Periodic ping failed (4 consecutive failures): all 2 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:39:06 Connection to server lost after 4 failures. Continuous reconnection attempts will be made.
INFO: 2025/07/15 14:39:06 Received registration message
INFO: 2025/07/15 14:39:06 Stopping ping check
INFO: 2025/07/15 14:39:06 Connecting to endpoint: pangolin.my.domain.com
WARN: 2025/07/15 14:39:37 Initial reliable ping failed, but continuing: all 5 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:39:42 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:39:47 Ping attempt 2 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:39:54 Ping attempt 3 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:40:01 Ping attempt 4 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:40:08 Ping attempt 5 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/07/15 14:40:08 Increasing ping retry delay to 3s
WARN: 2025/07/15 14:40:16 Ping attempt 6 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:40:24 Ping attempt 7 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:40:26 Periodic ping failed (2 consecutive failures): all 2 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
WARN: 2025/07/15 14:40:32 Ping attempt 8 failed: failed to read ICMP packet: i/o timeout

not sure if this is server-side or client-side error thou.

Originally created by @dparv on GitHub (Jul 15, 2025). Original GitHub issue: https://github.com/fosrl/newt/issues/87 Testing a simple config I am getting the following error from pangolin: ``` 2025-07-15T11:36:44.880Z [info]: Public key mismatch. Deleting old peer... 2025-07-15T11:36:44.895Z [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-07-15T11:36:44.903Z [info]: Peer added successfully: {"peer":"Peer added successfully"} asd2025-07-15T11:36:51.641Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:37:01.647Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:37:11.651Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:37:21.640Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:37:31.647Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:37:41.644Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:37:51.648Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:38:01.643Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:38:11.645Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:38:21.656Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:38:31.643Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:38:41.646Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:38:51.651Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:39:01.652Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:39:06.252Z [error]: Message handling error: Unsupported message type: newt/ping/request Stack: Error: Unsupported message type: newt/ping/request at WebSocket.<anonymous> (file:///app/dist/server.mjs:21:40731) at WebSocket.emit (node:events:524:28) at Receiver.receiverOnMessage (/app/node_modules/ws/lib/websocket.js:1220:20) at Receiver.emit (node:events:524:28) at Receiver.dataMessage (/app/node_modules/ws/lib/receiver.js:596:14) at Receiver.getData (/app/node_modules/ws/lib/receiver.js:496:10) at Receiver.startLoop (/app/node_modules/ws/lib/receiver.js:167:16) at Receiver._write (/app/node_modules/ws/lib/receiver.js:94:10) at writeOrBuffer (node:internal/streams/writable:572:12) at _write (node:internal/streams/writable:501:10) 2025-07-15T11:39:06.255Z [info]: Handling register message! 2025-07-15T11:39:06.292Z [info]: Peer added successfully: {"peer":"Peer added successfully"} 2025-07-15T11:39:11.647Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:39:21.646Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:39:31.645Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:39:41.665Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:39:51.644Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:40:01.650Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:40:11.652Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= 2025-07-15T11:40:21.642Z [warn]: Site not found for public key: b6ATRdsYOs14UXVrOCX6llhEcj/pLf/+WH1LIXxt/0g= ``` and newt is reporting ``` INFO: 2025/07/15 14:36:44 Newt version 1.3.2 INFO: 2025/07/15 14:36:44 Websocket connected INFO: 2025/07/15 14:36:44 Requesting exit nodes from server INFO: 2025/07/15 14:36:44 Received registration message INFO: 2025/07/15 14:36:44 Connecting to endpoint: pangolin.my.domain.com WARN: 2025/07/15 14:37:15 Initial reliable ping failed, but continuing: all 5 ping attempts failed, last error: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:37:20 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:37:25 Ping attempt 2 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:37:32 Ping attempt 3 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:37:39 Ping attempt 4 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:37:46 Ping attempt 5 failed: failed to read ICMP packet: i/o timeout INFO: 2025/07/15 14:37:46 Increasing ping retry delay to 3s WARN: 2025/07/15 14:37:54 Ping attempt 6 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:38:02 Ping attempt 7 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:38:04 Periodic ping failed (2 consecutive failures): all 2 ping attempts failed, last error: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:38:10 Ping attempt 8 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:38:18 Ping attempt 9 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:38:26 Ping attempt 10 failed: failed to read ICMP packet: i/o timeout INFO: 2025/07/15 14:38:26 Increasing ping retry delay to 4.5s WARN: 2025/07/15 14:38:35 Periodic ping failed (3 consecutive failures): all 2 ping attempts failed, last error: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:38:36 Ping attempt 11 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:38:45 Ping attempt 12 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:38:55 Ping attempt 13 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:39:04 Ping attempt 14 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:39:06 Periodic ping failed (4 consecutive failures): all 2 ping attempts failed, last error: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:39:06 Connection to server lost after 4 failures. Continuous reconnection attempts will be made. INFO: 2025/07/15 14:39:06 Received registration message INFO: 2025/07/15 14:39:06 Stopping ping check INFO: 2025/07/15 14:39:06 Connecting to endpoint: pangolin.my.domain.com WARN: 2025/07/15 14:39:37 Initial reliable ping failed, but continuing: all 5 ping attempts failed, last error: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:39:42 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:39:47 Ping attempt 2 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:39:54 Ping attempt 3 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:40:01 Ping attempt 4 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:40:08 Ping attempt 5 failed: failed to read ICMP packet: i/o timeout INFO: 2025/07/15 14:40:08 Increasing ping retry delay to 3s WARN: 2025/07/15 14:40:16 Ping attempt 6 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:40:24 Ping attempt 7 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:40:26 Periodic ping failed (2 consecutive failures): all 2 ping attempts failed, last error: failed to read ICMP packet: i/o timeout WARN: 2025/07/15 14:40:32 Ping attempt 8 failed: failed to read ICMP packet: i/o timeout ``` not sure if this is server-side or client-side error thou.
GiteaMirror commented 2026-04-16 03:28:17 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi! Newt is a little ahead of pangolin right now but I think that Unsupported message type: error should not be breaking things (hopefully) because it does look like you are connected at the end of the day to pangolin.my.domain.com. Did you have this working before and the new version broke things or is this a new install?

This is almost always caused by UDP port 51820 not being accessible on the VPS. Could you check your VPS provider's settings and make sure the port is open and the port is not being blocked on linux at all?

<!-- gh-comment-id:3079614961 --> @oschwartz10612 commented on GitHub (Jul 16, 2025): Hi! Newt is a little ahead of pangolin right now but I think that `Unsupported message type:` error should not be breaking things (hopefully) because it does look like you are connected at the end of the day to `pangolin.my.domain.com`. Did you have this working before and the new version broke things or is this a new install? This is almost always caused by UDP port 51820 not being accessible on the VPS. Could you check your VPS provider's settings and make sure the port is open and the port is not being blocked on linux at all?
GiteaMirror commented 2026-04-16 03:28:18 -05:00
Author
Owner
Copy Link
Copy Source

@stalli01 commented on GitHub (Jul 17, 2025):

Almost similar to my experience (UDP Port ist definitly reachable..):
Newt-Client:
`INFO: 2025/07/17 14:00:53 Newt version 1.3.2

INFO: 2025/07/17 14:00:53 Websocket connected

INFO: 2025/07/17 14:00:53 Requesting exit nodes from server

INFO: 2025/07/17 14:00:53 Received registration message

INFO: 2025/07/17 14:00:53 Connecting to endpoint: pangolin.DOMAIN.org

INFO: 2025/07/17 14:00:53 Initial connection test successful!

INFO: 2025/07/17 14:00:53 Tunnel connection to server established successfully!
pangolin (1.6.2):pangolin | 2025-07-17T12:03:38.331Z [info]: Establishing websocket connection

pangolin | 2025-07-17T12:03:38.331Z [info]: Client added to tracking - Newt ID: [blablub], Total connections: 1

pangolin | 2025-07-17T12:03:38.331Z [info]: WebSocket connection established - Newt ID: [blablub]

pangolin | 2025-07-17T12:03:38.355Z [info]: Handling register message!

pangolin | 2025-07-17T12:03:38.356Z [error]: Message handling error: Unsupported message type: newt/ping/request

pangolin | Stack: Error: Unsupported message type: newt/ping/request

pangolin | at WebSocket. (file:///app/dist/server.mjs:21:40731)

pangolin | at WebSocket.emit (node:events:524:28)

pangolin | at Receiver.receiverOnMessage (/app/node_modules/ws/lib/websocket.js:1220:20)

pangolin | at Receiver.emit (node:events:524:28)

pangolin | at Receiver.dataMessage (/app/node_modules/ws/lib/receiver.js:596:14)

pangolin | at Receiver.getData (/app/node_modules/ws/lib/receiver.js:496:10)

pangolin | at Receiver.startLoop (/app/node_modules/ws/lib/receiver.js:167:16)

pangolin | at Receiver._write (/app/node_modules/ws/lib/receiver.js:94:10)

pangolin | at writeOrBuffer (node:internal/streams/writable:572:12)

pangolin | at _write (node:internal/streams/writable:501:10)

pangolin | 2025-07-17T12:03:38.378Z [info]: Peer added successfully: {"peer":"Peer added successfully"}

pangolin | 2025-07-17T12:03:43.016Z [warn]: Site not found for public key: [NOTPUBLIC]
`

<!-- gh-comment-id:3083834398 --> @stalli01 commented on GitHub (Jul 17, 2025): Almost similar to my experience (UDP Port ist definitly reachable..): Newt-Client: `INFO: 2025/07/17 14:00:53 Newt version 1.3.2 INFO: 2025/07/17 14:00:53 Websocket connected INFO: 2025/07/17 14:00:53 Requesting exit nodes from server INFO: 2025/07/17 14:00:53 Received registration message INFO: 2025/07/17 14:00:53 Connecting to endpoint: pangolin.DOMAIN.org INFO: 2025/07/17 14:00:53 Initial connection test successful! INFO: 2025/07/17 14:00:53 Tunnel connection to server established successfully! ` pangolin (1.6.2): `pangolin | 2025-07-17T12:03:38.331Z [info]: Establishing websocket connection pangolin | 2025-07-17T12:03:38.331Z [info]: Client added to tracking - Newt ID: [blablub], Total connections: 1 pangolin | 2025-07-17T12:03:38.331Z [info]: WebSocket connection established - Newt ID: [blablub] pangolin | 2025-07-17T12:03:38.355Z [info]: Handling register message! pangolin | 2025-07-17T12:03:38.356Z [error]: Message handling error: Unsupported message type: newt/ping/request pangolin | Stack: Error: Unsupported message type: newt/ping/request pangolin | at WebSocket.<anonymous> (file:///app/dist/server.mjs:21:40731) pangolin | at WebSocket.emit (node:events:524:28) pangolin | at Receiver.receiverOnMessage (/app/node_modules/ws/lib/websocket.js:1220:20) pangolin | at Receiver.emit (node:events:524:28) pangolin | at Receiver.dataMessage (/app/node_modules/ws/lib/receiver.js:596:14) pangolin | at Receiver.getData (/app/node_modules/ws/lib/receiver.js:496:10) pangolin | at Receiver.startLoop (/app/node_modules/ws/lib/receiver.js:167:16) pangolin | at Receiver._write (/app/node_modules/ws/lib/receiver.js:94:10) pangolin | at writeOrBuffer (node:internal/streams/writable:572:12) pangolin | at _write (node:internal/streams/writable:501:10) pangolin | 2025-07-17T12:03:38.378Z [info]: Peer added successfully: {"peer":"Peer added successfully"} pangolin | 2025-07-17T12:03:43.016Z [warn]: Site not found for public key: [NOTPUBLIC] `
GiteaMirror commented 2026-04-16 03:28:18 -05:00
Author
Owner
Copy Link
Copy Source

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

@stalli01 It looks to me like your newt is connecting to Pangolin INFO: 2025/07/17 14:00:53 Tunnel connection to server established successfully! and the error from Pangolin about the missing message type is benign. Is that correct?

<!-- gh-comment-id:3084823410 --> @oschwartz10612 commented on GitHub (Jul 17, 2025): @stalli01 It looks to me like your newt is connecting to Pangolin `INFO: 2025/07/17 14:00:53 Tunnel connection to server established successfully!` and the error from Pangolin about the missing message type is benign. Is that correct?
GiteaMirror commented 2026-04-16 03:28:20 -05:00
Author
Owner
Copy Link
Copy Source

@stalli01 commented on GitHub (Jul 18, 2025):

You are right but I though it could be the reason for not finding the site to that pub-key (last line). It even tells: Newt 57g80flpj8czmou does not have Docker socket access...
The tunnel works but i tried to understand...
Thank you for supporting me.

<!-- gh-comment-id:3086779501 --> @stalli01 commented on GitHub (Jul 18, 2025): You are right but I though it could be the reason for not finding the site to that pub-key (last line). It even tells: Newt 57g80flpj8czmou does not have Docker socket access... The tunnel works but i tried to understand... Thank you for supporting me.
GiteaMirror commented 2026-04-16 03:28:21 -05:00
Author
Owner
Copy Link
Copy Source

@oschwartz10612 commented on GitHub (Jul 18, 2025):

Oh that's no problem that's just it noticing there is no docker socket to connect to on Newt to pull in the data!

Glad its working. Feel free to reopen if there is anything else!

<!-- gh-comment-id:3090409160 --> @oschwartz10612 commented on GitHub (Jul 18, 2025): Oh that's no problem that's just it noticing there is no docker socket to connect to on Newt to pull in the data! Glad its working. Feel free to reopen if there is anything else!
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#497