github-starred/newt
2
0
Fork 0
mirror of https://github.com/fosrl/newt.git synced 2026-03-09 07:12:28 -05:00
Code Issues 21 Packages Projects Releases 25 Wiki Activity

Newt spam #51

New Issue
Closed
opened 2025-11-19 07:12:52 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-19 07:12:52 -06:00
Owner
Copy Link

Originally created by @nixielectra on GitHub (Aug 30, 2025).

Newt: 1.4.2
Pangolin: 1.9.2

Hello, I'm not sure if anyone else experience this but newt keep spamming this over and over:

INFO: 2025/08/30 13:50:08 Received ping message
INFO: 2025/08/30 13:50:08 Received ping message
INFO: 2025/08/30 13:50:08 Received ping message
INFO: 2025/08/30 13:50:08 Received ping message
INFO: 2025/08/30 13:50:09 Received registration message
INFO: 2025/08/30 13:50:09 Stopping ping check
INFO: 2025/08/30 13:50:09 Connecting to endpoint: xxx.xxx.xxx.xxx
INFO: 2025/08/30 13:50:09 Initial connection test successful
INFO: 2025/08/30 13:50:10 Tunnel connection to server established successfully!
INFO: 2025/08/30 13:50:10 Successfully added 0 health check targets
INFO: 2025/08/30 13:50:10 Started tcp proxy to vaultwarden:80
INFO: 2025/08/30 13:50:10 Started tcp proxy to immich:2283
INFO: 2025/08/30 13:50:10 Started tcp proxy to mkdocs:8000
INFO: 2025/08/30 13:50:10 Received registration message
INFO: 2025/08/30 13:50:10 Stopping ping check
INFO: 2025/08/30 13:50:10 Connecting to endpoint: xxx.xxx.xxx.xxx
INFO: 2025/08/30 13:50:10 Initial connection test successful
INFO: 2025/08/30 13:50:10 Tunnel connection to server established successfully!
INFO: 2025/08/30 13:50:10 Successfully added 0 health check targets
INFO: 2025/08/30 13:50:10 Started tcp proxy to immich:2283
INFO: 2025/08/30 13:50:10 Started tcp proxy to mkdocs:8000
INFO: 2025/08/30 13:50:10 Started tcp proxy to vaultwarden:80
INFO: 2025/08/30 13:50:10 Received registration message
INFO: 2025/08/30 13:50:10 Stopping ping check
INFO: 2025/08/30 13:50:10 Connecting to endpoint: xxx.xxx.xxx.xxx
INFO: 2025/08/30 13:50:10 Initial connection test successful
INFO: 2025/08/30 13:50:10 Tunnel connection to server established successfully!
INFO: 2025/08/30 13:50:10 Successfully added 0 health check targets
INFO: 2025/08/30 13:50:10 Started tcp proxy to immich:2283
INFO: 2025/08/30 13:50:10 Started tcp proxy to mkdocs:8000
INFO: 2025/08/30 13:50:10 Started tcp proxy to vaultwarden:80
INFO: 2025/08/30 13:50:10 Received registration message
INFO: 2025/08/30 13:50:10 Stopping ping check
INFO: 2025/08/30 13:50:10 Connecting to endpoint: xxx.xxx.xxx.xxx
INFO: 2025/08/30 13:50:11 Initial connection test successful
INFO: 2025/08/30 13:50:11 Tunnel connection to server established successfully!
INFO: 2025/08/30 13:50:11 Successfully added 0 health check targets
INFO: 2025/08/30 13:50:11 Started tcp proxy to mkdocs:8000
INFO: 2025/08/30 13:50:11 Started tcp proxy to vaultwarden:80
INFO: 2025/08/30 13:50:11 Started tcp proxy to immich:2283
INFO: 2025/08/30 13:50:11 Received registration message
INFO: 2025/08/30 13:50:11 Stopping ping check
INFO: 2025/08/30 13:50:11 Connecting to endpoint: xxx.xxx.xxx.xxx
INFO: 2025/08/30 13:50:11 Initial connection test successful
INFO: 2025/08/30 13:50:11 Tunnel connection to server established successfully!
INFO: 2025/08/30 13:50:11 Successfully added 0 health check targets
INFO: 2025/08/30 13:50:11 Started tcp proxy to immich:2283
INFO: 2025/08/30 13:50:11 Started tcp proxy to mkdocs:8000
INFO: 2025/08/30 13:50:11 Started tcp proxy to vaultwarden:80
INFO: 2025/08/30 13:50:11 Received registration message
INFO: 2025/08/30 13:50:11 Stopping ping check
INFO: 2025/08/30 13:50:11 Connecting to endpoint: xxx.xxx.xxx.xxx
INFO: 2025/08/30 13:50:11 Initial connection test successful
INFO: 2025/08/30 13:50:11 Tunnel connection to server established successfully!
INFO: 2025/08/30 13:50:11 Successfully added 0 health check targets
INFO: 2025/08/30 13:50:11 Started tcp proxy to mkdocs:8000
INFO: 2025/08/30 13:50:11 Started tcp proxy to vaultwarden:80
INFO: 2025/08/30 13:50:11 Started tcp proxy to immich:2283

This is just a fraction of the logs, it can go up to hundreds of lines with same message.

Pangolin logs:

2025-08-30T05:50:08.049Z [info]: Handling ping request newt message!
2025-08-30T05:50:08.051Z [info]: Handling ping request newt message!
2025-08-30T05:50:08.051Z [info]: Handling ping request newt message!
2025-08-30T05:50:08.051Z [info]: Handling ping request newt message!
2025-08-30T05:50:08.051Z [info]: Handling ping request newt message!
2025-08-30T05:50:09.298Z [info]: Adding peer with public key R1hzPasa123SDGHxsqkJ8176wkAET+4+1h1JPGDFAB42DUQ= to exit node 1
2025-08-30T05:50:09.299Z [info]: Adding peer with public key R1hzPasa123SDGHxsqkJ8176wkAET+4+1h1JPGDFAB42DUQ= to exit node 1
2025-08-30T05:50:09.299Z [info]: Adding peer with public key R1hzPasa123SDGHxsqkJ8176wkAET+4+1h1JPGDFAB42DUQ= to exit node 1
2025-08-30T05:50:09.299Z [info]: Adding peer with public key R1hzPasa123SDGHxsqkJ8176wkAET+4+1h1JPGDFAB42DUQ= to exit node 1
2025-08-30T05:50:09.299Z [info]: Adding peer with public key R1hzPasa123SDGHxsqkJ8176wkAET+4+1h1JPGDFAB42DUQ= to exit node 1
2025-08-30T05:50:09.326Z [info]: Exit node request successful: {"method":"POST","url":"http://gerbil:3003/peer","status":"Peer added successfully"}
2025-08-30T05:50:09.331Z [info]: Exit node request successful: {"method":"POST","url":"http://gerbil:3003/peer","status":"Peer added successfully"}
2025-08-30T05:50:09.334Z [info]: Exit node request successful: {"method":"POST","url":"http://gerbil:3003/peer","status":"Peer added successfully"}
2025-08-30T05:50:09.339Z [info]: Exit node request successful: {"method":"POST","url":"http://gerbil:3003/peer","status":"Peer added successfully"}
2025-08-30T05:50:09.345Z [info]: Exit node request successful: {"method":"POST","url":"http://gerbil:3003/peer","status":"Peer added successfully"}
2025-08-30T05:50:09.434Z [info]: Adding peer with public key R1hzPasa123SDGHxsqkJ8176wkAET+4+1h1JPGDFAB42DUQ= to exit node 1
2025-08-30T05:50:09.437Z [info]: Exit node request successful: {"method":"POST","url":"http://gerbil:3003/peer","status":"Peer added successfully"}
Originally created by @nixielectra on GitHub (Aug 30, 2025). Newt: 1.4.2 Pangolin: 1.9.2 Hello, I'm not sure if anyone else experience this but newt keep spamming this over and over: ``` INFO: 2025/08/30 13:50:08 Received ping message INFO: 2025/08/30 13:50:08 Received ping message INFO: 2025/08/30 13:50:08 Received ping message INFO: 2025/08/30 13:50:08 Received ping message INFO: 2025/08/30 13:50:09 Received registration message INFO: 2025/08/30 13:50:09 Stopping ping check INFO: 2025/08/30 13:50:09 Connecting to endpoint: xxx.xxx.xxx.xxx INFO: 2025/08/30 13:50:09 Initial connection test successful INFO: 2025/08/30 13:50:10 Tunnel connection to server established successfully! INFO: 2025/08/30 13:50:10 Successfully added 0 health check targets INFO: 2025/08/30 13:50:10 Started tcp proxy to vaultwarden:80 INFO: 2025/08/30 13:50:10 Started tcp proxy to immich:2283 INFO: 2025/08/30 13:50:10 Started tcp proxy to mkdocs:8000 INFO: 2025/08/30 13:50:10 Received registration message INFO: 2025/08/30 13:50:10 Stopping ping check INFO: 2025/08/30 13:50:10 Connecting to endpoint: xxx.xxx.xxx.xxx INFO: 2025/08/30 13:50:10 Initial connection test successful INFO: 2025/08/30 13:50:10 Tunnel connection to server established successfully! INFO: 2025/08/30 13:50:10 Successfully added 0 health check targets INFO: 2025/08/30 13:50:10 Started tcp proxy to immich:2283 INFO: 2025/08/30 13:50:10 Started tcp proxy to mkdocs:8000 INFO: 2025/08/30 13:50:10 Started tcp proxy to vaultwarden:80 INFO: 2025/08/30 13:50:10 Received registration message INFO: 2025/08/30 13:50:10 Stopping ping check INFO: 2025/08/30 13:50:10 Connecting to endpoint: xxx.xxx.xxx.xxx INFO: 2025/08/30 13:50:10 Initial connection test successful INFO: 2025/08/30 13:50:10 Tunnel connection to server established successfully! INFO: 2025/08/30 13:50:10 Successfully added 0 health check targets INFO: 2025/08/30 13:50:10 Started tcp proxy to immich:2283 INFO: 2025/08/30 13:50:10 Started tcp proxy to mkdocs:8000 INFO: 2025/08/30 13:50:10 Started tcp proxy to vaultwarden:80 INFO: 2025/08/30 13:50:10 Received registration message INFO: 2025/08/30 13:50:10 Stopping ping check INFO: 2025/08/30 13:50:10 Connecting to endpoint: xxx.xxx.xxx.xxx INFO: 2025/08/30 13:50:11 Initial connection test successful INFO: 2025/08/30 13:50:11 Tunnel connection to server established successfully! INFO: 2025/08/30 13:50:11 Successfully added 0 health check targets INFO: 2025/08/30 13:50:11 Started tcp proxy to mkdocs:8000 INFO: 2025/08/30 13:50:11 Started tcp proxy to vaultwarden:80 INFO: 2025/08/30 13:50:11 Started tcp proxy to immich:2283 INFO: 2025/08/30 13:50:11 Received registration message INFO: 2025/08/30 13:50:11 Stopping ping check INFO: 2025/08/30 13:50:11 Connecting to endpoint: xxx.xxx.xxx.xxx INFO: 2025/08/30 13:50:11 Initial connection test successful INFO: 2025/08/30 13:50:11 Tunnel connection to server established successfully! INFO: 2025/08/30 13:50:11 Successfully added 0 health check targets INFO: 2025/08/30 13:50:11 Started tcp proxy to immich:2283 INFO: 2025/08/30 13:50:11 Started tcp proxy to mkdocs:8000 INFO: 2025/08/30 13:50:11 Started tcp proxy to vaultwarden:80 INFO: 2025/08/30 13:50:11 Received registration message INFO: 2025/08/30 13:50:11 Stopping ping check INFO: 2025/08/30 13:50:11 Connecting to endpoint: xxx.xxx.xxx.xxx INFO: 2025/08/30 13:50:11 Initial connection test successful INFO: 2025/08/30 13:50:11 Tunnel connection to server established successfully! INFO: 2025/08/30 13:50:11 Successfully added 0 health check targets INFO: 2025/08/30 13:50:11 Started tcp proxy to mkdocs:8000 INFO: 2025/08/30 13:50:11 Started tcp proxy to vaultwarden:80 INFO: 2025/08/30 13:50:11 Started tcp proxy to immich:2283 ``` This is just a fraction of the logs, it can go up to hundreds of lines with same message. Pangolin logs: ``` 2025-08-30T05:50:08.049Z [info]: Handling ping request newt message! 2025-08-30T05:50:08.051Z [info]: Handling ping request newt message! 2025-08-30T05:50:08.051Z [info]: Handling ping request newt message! 2025-08-30T05:50:08.051Z [info]: Handling ping request newt message! 2025-08-30T05:50:08.051Z [info]: Handling ping request newt message! 2025-08-30T05:50:09.298Z [info]: Adding peer with public key R1hzPasa123SDGHxsqkJ8176wkAET+4+1h1JPGDFAB42DUQ= to exit node 1 2025-08-30T05:50:09.299Z [info]: Adding peer with public key R1hzPasa123SDGHxsqkJ8176wkAET+4+1h1JPGDFAB42DUQ= to exit node 1 2025-08-30T05:50:09.299Z [info]: Adding peer with public key R1hzPasa123SDGHxsqkJ8176wkAET+4+1h1JPGDFAB42DUQ= to exit node 1 2025-08-30T05:50:09.299Z [info]: Adding peer with public key R1hzPasa123SDGHxsqkJ8176wkAET+4+1h1JPGDFAB42DUQ= to exit node 1 2025-08-30T05:50:09.299Z [info]: Adding peer with public key R1hzPasa123SDGHxsqkJ8176wkAET+4+1h1JPGDFAB42DUQ= to exit node 1 2025-08-30T05:50:09.326Z [info]: Exit node request successful: {"method":"POST","url":"http://gerbil:3003/peer","status":"Peer added successfully"} 2025-08-30T05:50:09.331Z [info]: Exit node request successful: {"method":"POST","url":"http://gerbil:3003/peer","status":"Peer added successfully"} 2025-08-30T05:50:09.334Z [info]: Exit node request successful: {"method":"POST","url":"http://gerbil:3003/peer","status":"Peer added successfully"} 2025-08-30T05:50:09.339Z [info]: Exit node request successful: {"method":"POST","url":"http://gerbil:3003/peer","status":"Peer added successfully"} 2025-08-30T05:50:09.345Z [info]: Exit node request successful: {"method":"POST","url":"http://gerbil:3003/peer","status":"Peer added successfully"} 2025-08-30T05:50:09.434Z [info]: Adding peer with public key R1hzPasa123SDGHxsqkJ8176wkAET+4+1h1JPGDFAB42DUQ= to exit node 1 2025-08-30T05:50:09.437Z [info]: Exit node request successful: {"method":"POST","url":"http://gerbil:3003/peer","status":"Peer added successfully"} ```
GiteaMirror commented 2025-11-19 07:12:53 -06:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Aug 31, 2025):

INFO: 2025/08/30 13:50:08 Received ping message
It looks like it does this a couple of times. I was not able to
reproduce so I wonder what is causing this. Does this happen every time
you connect newt?

@oschwartz10612 commented on GitHub (Aug 31, 2025): > INFO: 2025/08/30 13:50:08 Received ping message It looks like it does this a couple of times. I was not able to reproduce so I wonder what is causing this. Does this happen every time you connect newt?
GiteaMirror commented 2025-11-19 07:12:53 -06:00
Author
Owner
Copy Link

@nixielectra commented on GitHub (Aug 31, 2025):

It looks like it does this a couple of times. I was not able to
reproduce so I wonder what is causing this. Does this happen every time
you connect newt?

no, it happens randomly in a day. Firstly I thought maybe my internet connection was down but when I check my reporting services all good, my connection didn't drop.

@nixielectra commented on GitHub (Aug 31, 2025): > It looks like it does this a couple of times. I was not able to > reproduce so I wonder what is causing this. Does this happen every time > you connect newt? no, it happens randomly in a day. Firstly I thought maybe my internet connection was down but when I check my reporting services all good, my connection didn't drop.
GiteaMirror commented 2025-11-19 07:12:53 -06:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Aug 31, 2025):

Ahh okay maybe it gets triggered by bad pings or something. Does it stop
or once it starts going it keeps going?

@oschwartz10612 commented on GitHub (Aug 31, 2025): Ahh okay maybe it gets triggered by bad pings or something. Does it stop or once it starts going it keeps going?
GiteaMirror commented 2025-11-19 07:12:54 -06:00
Author
Owner
Copy Link

@nixielectra commented on GitHub (Aug 31, 2025):

Ahh okay maybe it gets triggered by bad pings or something. Does it stop
or once it starts going it keeps going?

it does stop at some point after idk hundreds of lines in docker logs newt but then sometimes later it will triggered again and repeat itself like that.

@nixielectra commented on GitHub (Aug 31, 2025): > Ahh okay maybe it gets triggered by bad pings or something. Does it stop > or once it starts going it keeps going? it does stop at some point after idk hundreds of lines in `docker logs newt` but then sometimes later it will triggered again and repeat itself like that.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
good first issue
help wanted
Improvement
pull-request
Mirrored from GitHub Pull Request
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/newt#51
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?