Why does Newt keep requesting tokens/reconnecting continuously?

[wouldntyouknow]

I am using the latest images as of writing this.
In earlier versions, Newt connected to the Pangolin host and just kept pinging in certain intervals for health check and reconnected when necessary (which happened quite rarely).
Now, I just noticed that it keeps reconnecting very frequently. Here is an example, just for the past hour, taken from newt's docker log:

`
newt | 2025-08-05T11:44:21.498578348Z INFO: 2025/08/05 11:44:21 Websocket connected
newt | 2025-08-05T11:44:21.539828344Z INFO: 2025/08/05 11:44:21 Websocket connected
newt | 2025-08-05T11:46:02.198107490Z INFO: 2025/08/05 11:46:02 Websocket connected
newt | 2025-08-05T11:46:02.228358567Z INFO: 2025/08/05 11:46:02 Websocket connected
newt | 2025-08-05T11:47:42.749197223Z INFO: 2025/08/05 11:47:42 Websocket connected
newt | 2025-08-05T11:47:42.839003734Z INFO: 2025/08/05 11:47:42 Websocket connected
newt | 2025-08-05T11:49:24.138818670Z INFO: 2025/08/05 11:49:24 Websocket connected
newt | 2025-08-05T11:49:24.155289059Z INFO: 2025/08/05 11:49:24 Websocket connected
newt | 2025-08-05T11:51:05.831262650Z INFO: 2025/08/05 11:51:05 Websocket connected
newt | 2025-08-05T11:51:05.834351219Z INFO: 2025/08/05 11:51:05 Websocket connected
newt | 2025-08-05T11:52:46.591207053Z INFO: 2025/08/05 11:52:46 Websocket connected
newt | 2025-08-05T11:52:46.620303210Z INFO: 2025/08/05 11:52:46 Websocket connected
newt | 2025-08-05T11:54:27.192626528Z INFO: 2025/08/05 11:54:27 Websocket connected
newt | 2025-08-05T11:54:27.311843809Z INFO: 2025/08/05 11:54:27 Websocket connected
newt | 2025-08-05T11:56:07.836815494Z INFO: 2025/08/05 11:56:07 Websocket connected
newt | 2025-08-05T11:56:07.918655428Z INFO: 2025/08/05 11:56:07 Websocket connected
newt | 2025-08-05T11:57:48.416000814Z INFO: 2025/08/05 11:57:48 Websocket connected
newt | 2025-08-05T11:57:48.475379299Z INFO: 2025/08/05 11:57:48 Websocket connected
newt | 2025-08-05T11:59:29.032416386Z INFO: 2025/08/05 11:59:29 Websocket connected
newt | 2025-08-05T11:59:29.078374352Z INFO: 2025/08/05 11:59:29 Websocket connected
newt | 2025-08-05T12:01:10.752280032Z INFO: 2025/08/05 12:01:10 Websocket connected
newt | 2025-08-05T12:01:10.785748270Z INFO: 2025/08/05 12:01:10 Websocket connected
newt | 2025-08-05T12:02:51.440910057Z INFO: 2025/08/05 12:02:51 Websocket connected
newt | 2025-08-05T12:02:51.526430381Z INFO: 2025/08/05 12:02:51 Websocket connected
newt | 2025-08-05T12:04:32.219589699Z INFO: 2025/08/05 12:04:32 Websocket connected
newt | 2025-08-05T12:04:32.254717987Z INFO: 2025/08/05 12:04:32 Websocket connected
newt | 2025-08-05T12:06:13.000518645Z INFO: 2025/08/05 12:06:13 Websocket connected
newt | 2025-08-05T12:06:13.047148822Z INFO: 2025/08/05 12:06:13 Websocket connected
newt | 2025-08-05T12:07:53.660544119Z INFO: 2025/08/05 12:07:53 Websocket connected
newt | 2025-08-05T12:07:53.700291783Z INFO: 2025/08/05 12:07:53 Websocket connected
newt | 2025-08-05T12:09:34.275426192Z INFO: 2025/08/05 12:09:34 Websocket connected
newt | 2025-08-05T12:09:34.313520456Z INFO: 2025/08/05 12:09:34 Websocket connected
newt | 2025-08-05T12:11:14.971030503Z INFO: 2025/08/05 12:11:14 Websocket connected
newt | 2025-08-05T12:11:15.070230648Z INFO: 2025/08/05 12:11:15 Websocket connected
newt | 2025-08-05T12:12:55.698347711Z INFO: 2025/08/05 12:12:55 Websocket connected
newt | 2025-08-05T12:12:55.758444259Z INFO: 2025/08/05 12:12:55 Websocket connected
newt | 2025-08-05T12:14:36.359736390Z INFO: 2025/08/05 12:14:36 Websocket connected
newt | 2025-08-05T12:14:36.429307047Z INFO: 2025/08/05 12:14:36 Websocket connected
newt | 2025-08-05T12:16:18.112056039Z INFO: 2025/08/05 12:16:18 Websocket connected
newt | 2025-08-05T12:16:19.000983176Z INFO: 2025/08/05 12:16:19 Websocket connected
newt | 2025-08-05T12:17:59.639769571Z INFO: 2025/08/05 12:17:59 Websocket connected
newt | 2025-08-05T12:17:59.647379315Z INFO: 2025/08/05 12:17:59 Websocket connected
newt | 2025-08-05T12:19:40.750816801Z INFO: 2025/08/05 12:19:40 Websocket connected
newt | 2025-08-05T12:19:40.757739644Z INFO: 2025/08/05 12:19:40 Websocket connected
newt | 2025-08-05T12:21:21.761087976Z INFO: 2025/08/05 12:21:21 Websocket connected
newt | 2025-08-05T12:21:21.829817842Z INFO: 2025/08/05 12:21:21 Websocket connected
newt | 2025-08-05T12:23:02.472443007Z INFO: 2025/08/05 12:23:02 Websocket connected
newt | 2025-08-05T12:23:02.502599687Z INFO: 2025/08/05 12:23:02 Websocket connected
newt | 2025-08-05T12:24:43.123186117Z INFO: 2025/08/05 12:24:43 Websocket connected
newt | 2025-08-05T12:24:43.163851229Z INFO: 2025/08/05 12:24:43 Websocket connected
newt | 2025-08-05T12:26:23.719372604Z INFO: 2025/08/05 12:26:23 Websocket connected
newt | 2025-08-05T12:26:23.744229030Z INFO: 2025/08/05 12:26:23 Websocket connected
newt | 2025-08-05T12:28:04.430788678Z INFO: 2025/08/05 12:28:04 Websocket connected
newt | 2025-08-05T12:28:04.446134141Z INFO: 2025/08/05 12:28:04 Websocket connected
newt | 2025-08-05T12:29:45.108279958Z INFO: 2025/08/05 12:29:45 Websocket connected
newt | 2025-08-05T12:29:45.130950213Z INFO: 2025/08/05 12:29:45 Websocket connected
newt | 2025-08-05T12:31:25.722935011Z INFO: 2025/08/05 12:31:25 Websocket connected
newt | 2025-08-05T12:31:25.754004138Z INFO: 2025/08/05 12:31:25 Websocket connected
newt | 2025-08-05T12:33:06.472586504Z INFO: 2025/08/05 12:33:06 Websocket connected
newt | 2025-08-05T12:33:06.511384611Z INFO: 2025/08/05 12:33:06 Websocket connected
newt | 2025-08-05T12:34:47.189061737Z INFO: 2025/08/05 12:34:47 Websocket connected
newt | 2025-08-05T12:34:47.286308884Z INFO: 2025/08/05 12:34:47 Websocket connected
newt | 2025-08-05T12:36:27.844626306Z INFO: 2025/08/05 12:36:27 Websocket connected
newt | 2025-08-05T12:36:27.901175805Z INFO: 2025/08/05 12:36:27 Websocket connected
newt | 2025-08-05T12:38:08.516208489Z INFO: 2025/08/05 12:38:08 Websocket connected
newt | 2025-08-05T12:38:08.541668783Z INFO: 2025/08/05 12:38:08 Websocket connected
newt | 2025-08-05T12:39:50.137863442Z INFO: 2025/08/05 12:39:50 Websocket connected
newt | 2025-08-05T12:39:51.665008693Z INFO: 2025/08/05 12:39:51 Websocket connected
newt | 2025-08-05T12:41:32.067749836Z INFO: 2025/08/05 12:41:32 Websocket connected
newt | 2025-08-05T12:41:32.074504918Z INFO: 2025/08/05 12:41:32 Websocket connected
newt | 2025-08-05T12:43:13.406647201Z INFO: 2025/08/05 12:43:13 Websocket connected
newt | 2025-08-05T12:43:13.418001223Z INFO: 2025/08/05 12:43:13 Websocket connected
newt | 2025-08-05T12:44:54.547017529Z INFO: 2025/08/05 12:44:54 Websocket connected
newt | 2025-08-05T12:44:54.763785745Z INFO: 2025/08/05 12:44:54 Websocket connected

`

All the entries have their corresponding entries on Pangolin's (traefik) end, I am referring to these:
POST requestpath:/api/v1/auth/newt/get-token
GET /api/v1/ws?clientType=newt&token=(tokenredacted)

Why is this happening now, any ideas? Some wrong setting?

[oschwartz10612]

I made the websocket and wg ping much more aggressive in later versions. Perhaps you have some flapping on your network connection or something like that? Maybe you could run a test on your local network pinging your VPS and see if it drops at all?

But you can control the intervals with these flags:

ping-interval (optional): Interval for pinging the server. Default: 3s

ping-timeout (optional): Timeout for each ping. Default: 5s

[wouldntyouknow]

I did not notice any network anomalies, pings are consistent (I liked in newt 1.0 that it was visible) and no dropped packets.
How exactly should I set the intervals? Also can I make it visible in the logs, a la old school newt?

[vadim0872]

@wouldntyouknow I have the same problem. How do you run newt?

[wouldntyouknow]

@wouldntyouknow I have the same problem. How do you run newt?

Just a regular docker compose, nothing special....

services:
  newt:
    image: fosrl/newt:latest
    container_name: newt
    restart: unless-stopped
    environment:
      - PANGOLIN_ENDPOINT=https://[My Endpoint]
      - NEWT_ID=[My ID]
      - NEWT_SECRET=[My Secret]

Btw I checked and it's happening again today. I am not even sure what kind of impact this has. Does this indicate momentary connection break - like it had to connect again? Or just an info entry about it being connected (as in: remaining connected)?
No idea. If it's the latter then I can live with it, it's fine.

[oschwartz10612]

It just means that the command and control websocket connects and disconnects. This should not effect connectivity.

You can see the ping stuff if you turn on debug logs. Maybe it would be good to see that if that is also occurring? You could turn it on and post your logs.

To change the ping settings you can use the flags or env vars shown in the readme!