mirror of
https://github.com/fosrl/newt.git
synced 2026-03-08 23:03:03 -05:00
Getting Unsupported message type: newt/ping/request #41
Reference in New Issue
Block a user
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?
Originally created by @dparv on GitHub (Jul 15, 2025).
Testing a simple config I am getting the following error from pangolin:
and newt is reporting
not sure if this is server-side or client-side error thou.
@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 topangolin.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?
@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 connectionpangolin | 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]
`
@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?@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.
@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!