I'm trying to resolve an intermittent newt connectivity issue on one newt endpoint, which I am unable to determine the cause of. For context, I have 2 other newt endpoints (one Home Assistant, one Raspberry Pi 3) and they are able to connect and resolve without any issues. The endpoint having the issue is on the same server that is hosting Pangolin which is being used for reverse proxy duties.
I have attempted to recreate the docker container several times as well as generate new secrets and client IDs, no change to the outcome.
Logs from newt on the Unraid server (omitted the FQDN and WAN IP):-
INFO: 2025/12/02 00:03:32 Starting metrics server on 127.0.0.1:2112
INFO: 2025/12/02 00:03:32 Newt version 1.6.0
INFO: 2025/12/02 00:03:32 Config file does not exist at /root/.config/newt-client/config.json, will create it
ERROR: 2025/12/02 00:04:02 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": dial tcp <WAN IP>:443: i/o timeout. Retrying in 3s...
ERROR: 2025/12/02 00:04:10 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:04:10 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:04:35 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": context deadline exceeded. Retrying in 3s...
ERROR: 2025/12/02 00:05:09 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": context deadline exceeded. Retrying in 3s...
ERROR: 2025/12/02 00:05:13 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:05:13 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:05:42 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": dial tcp <WAN IP>:443: i/o timeout. Retrying in 3s...
ERROR: 2025/12/02 00:06:15 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": context deadline exceeded. Retrying in 3s...
ERROR: 2025/12/02 00:06:15 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:06:15 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:06:48 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": context deadline exceeded. Retrying in 3s...
ERROR: 2025/12/02 00:07:17 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:07:17 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:07:21 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": context deadline exceeded. Retrying in 3s...
ERROR: 2025/12/02 00:07:54 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": context deadline exceeded. Retrying in 3s...
ERROR: 2025/12/02 00:08:19 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:08:19 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:08:27 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": dial tcp <WAN IP>:443: i/o timeout. Retrying in 3s...
ERROR: 2025/12/02 00:09:00 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": dial tcp <WAN IP>:443: i/o timeout. Retrying in 3s...
ERROR: 2025/12/02 00:09:22 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:09:22 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:09:33 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": dial tcp <WAN IP>:443: i/o timeout. Retrying in 3s...
ERROR: 2025/12/02 00:10:06 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": context deadline exceeded. Retrying in 3s...
ERROR: 2025/12/02 00:10:24 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:10:24 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:10:39 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": dial tcp <WAN IP>:443: i/o timeout. Retrying in 3s...
ERROR: 2025/12/02 00:11:12 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": dial tcp <WAN IP>:443: i/o timeout. Retrying in 3s...
ERROR: 2025/12/02 00:11:26 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:11:26 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:11:45 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": dial tcp <WAN IP>:443: i/o timeout. Retrying in 3s...
ERROR: 2025/12/02 00:12:18 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": dial tcp <WAN IP>:443: i/o timeout. Retrying in 3s...
This has been working flawlessly for the last 3 months, however I rebooted my Unraid server yesterday and newt on the server has failed to connect ever since. No changes have been made to the underlying network infrastructure, and Pangolin/Gerbil/Traefik are working exactly as expected on the other two newt endpoints configured for this instance.
I have noticed that INFO: 2025/12/02 00:03:32 Config file does not exist at /root/.config/newt-client/config.json, will create it was a recent entry in the newt logs, and even though the config has been defined correctly in the Unraid template, even manually connecting to the docker container and creating the file with the same values in JSON did not resolve the issue.
Unraid template for newt (same as what is in the CA store, PII removed):
Environment
OS Type & Version: Unraid 7.2.2
Pangolin Version: 1.12.2
Gerbil Version: 1.2.2
Traefik Version: 3.6.2
Newt Version: 1.6.0
Olm Version: (if applicable) N/A
To Reproduce
Unable to provide exact steps, as a simple hardware reboot caused this mess. I would like to reiterate though that other newt endpoints ARE working as expected, it is only the Unraid server newt endpoint that is being a pain.
Expected Behavior
Work consistently?
Originally created by @evakq8r on GitHub (Dec 1, 2025).
Original GitHub issue: https://github.com/fosrl/newt/issues/183
### Describe the Bug
Hi,
I'm trying to resolve an intermittent newt connectivity issue on one newt endpoint, which I am unable to determine the cause of. For context, I have 2 other newt endpoints (one Home Assistant, one Raspberry Pi 3) and they are able to connect and resolve without any issues. The endpoint having the issue is on the same server that is hosting Pangolin which is being used for reverse proxy duties.
I have attempted to recreate the docker container several times as well as generate new secrets and client IDs, no change to the outcome.
Logs from newt on the Unraid server (omitted the FQDN and WAN IP):-
```
INFO: 2025/12/02 00:03:32 Starting metrics server on 127.0.0.1:2112
INFO: 2025/12/02 00:03:32 Newt version 1.6.0
INFO: 2025/12/02 00:03:32 Config file does not exist at /root/.config/newt-client/config.json, will create it
ERROR: 2025/12/02 00:04:02 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": dial tcp <WAN IP>:443: i/o timeout. Retrying in 3s...
ERROR: 2025/12/02 00:04:10 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:04:10 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:04:35 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": context deadline exceeded. Retrying in 3s...
ERROR: 2025/12/02 00:05:09 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": context deadline exceeded. Retrying in 3s...
ERROR: 2025/12/02 00:05:13 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:05:13 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:05:42 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": dial tcp <WAN IP>:443: i/o timeout. Retrying in 3s...
ERROR: 2025/12/02 00:06:15 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": context deadline exceeded. Retrying in 3s...
ERROR: 2025/12/02 00:06:15 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:06:15 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:06:48 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": context deadline exceeded. Retrying in 3s...
ERROR: 2025/12/02 00:07:17 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:07:17 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:07:21 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": context deadline exceeded. Retrying in 3s...
ERROR: 2025/12/02 00:07:54 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": context deadline exceeded. Retrying in 3s...
ERROR: 2025/12/02 00:08:19 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:08:19 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:08:27 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": dial tcp <WAN IP>:443: i/o timeout. Retrying in 3s...
ERROR: 2025/12/02 00:09:00 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": dial tcp <WAN IP>:443: i/o timeout. Retrying in 3s...
ERROR: 2025/12/02 00:09:22 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:09:22 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:09:33 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": dial tcp <WAN IP>:443: i/o timeout. Retrying in 3s...
ERROR: 2025/12/02 00:10:06 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": context deadline exceeded. Retrying in 3s...
ERROR: 2025/12/02 00:10:24 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:10:24 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:10:39 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": dial tcp <WAN IP>:443: i/o timeout. Retrying in 3s...
ERROR: 2025/12/02 00:11:12 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": dial tcp <WAN IP>:443: i/o timeout. Retrying in 3s...
ERROR: 2025/12/02 00:11:26 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:11:26 Failed to send updated container list after Docker event: not connected
ERROR: 2025/12/02 00:11:45 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": dial tcp <WAN IP>:443: i/o timeout. Retrying in 3s...
ERROR: 2025/12/02 00:12:18 Failed to connect: failed to get token: failed to request new token: Post "https://pangolin.<mydomain>/api/v1/auth/newt/get-token": dial tcp <WAN IP>:443: i/o timeout. Retrying in 3s...
```
This has been working flawlessly for the last 3 months, however I rebooted my Unraid server yesterday and newt on the server has failed to connect ever since. No changes have been made to the underlying network infrastructure, and Pangolin/Gerbil/Traefik are working exactly as expected on the other two newt endpoints configured for this instance.
I have noticed that `INFO: 2025/12/02 00:03:32 Config file does not exist at /root/.config/newt-client/config.json, will create it` was a recent entry in the newt logs, and even though the config has been defined correctly in the Unraid template, even manually connecting to the docker container and creating the file with the same values in JSON did not resolve the issue.
Unraid template for newt (same as what is in the CA store, PII removed):
<img width="883" height="460" alt="Image" src="https://github.com/user-attachments/assets/cf318b04-5d2d-48aa-83e6-1651507ccf23" />
### Environment
- OS Type & Version: Unraid 7.2.2
- Pangolin Version: 1.12.2
- Gerbil Version: 1.2.2
- Traefik Version: 3.6.2
- Newt Version: 1.6.0
- Olm Version: (if applicable) N/A
### To Reproduce
Unable to provide exact steps, as a simple hardware reboot caused this mess. I would like to reiterate though that other newt endpoints ARE working as expected, it is only the Unraid server newt endpoint that is being a pain.
### Expected Behavior
Work consistently?
Self-inflicted issue; after going through the Pangolin discord, I've realised I added a Newt config when I should have just used local. Swapping the Pangolin entries to local now works as expected.
<!-- gh-comment-id:3602813541 -->
@evakq8r commented on GitHub (Dec 2, 2025):
Self-inflicted issue; after going through the Pangolin discord, I've realised I added a Newt config when I should have just used local. Swapping the Pangolin entries to local now works as expected.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @evakq8r on GitHub (Dec 1, 2025).
Original GitHub issue: https://github.com/fosrl/newt/issues/183
Describe the Bug
Hi,
I'm trying to resolve an intermittent newt connectivity issue on one newt endpoint, which I am unable to determine the cause of. For context, I have 2 other newt endpoints (one Home Assistant, one Raspberry Pi 3) and they are able to connect and resolve without any issues. The endpoint having the issue is on the same server that is hosting Pangolin which is being used for reverse proxy duties.
I have attempted to recreate the docker container several times as well as generate new secrets and client IDs, no change to the outcome.
Logs from newt on the Unraid server (omitted the FQDN and WAN IP):-
This has been working flawlessly for the last 3 months, however I rebooted my Unraid server yesterday and newt on the server has failed to connect ever since. No changes have been made to the underlying network infrastructure, and Pangolin/Gerbil/Traefik are working exactly as expected on the other two newt endpoints configured for this instance.
I have noticed that
INFO: 2025/12/02 00:03:32 Config file does not exist at /root/.config/newt-client/config.json, will create itwas a recent entry in the newt logs, and even though the config has been defined correctly in the Unraid template, even manually connecting to the docker container and creating the file with the same values in JSON did not resolve the issue.Unraid template for newt (same as what is in the CA store, PII removed):
Environment
To Reproduce
Unable to provide exact steps, as a simple hardware reboot caused this mess. I would like to reiterate though that other newt endpoints ARE working as expected, it is only the Unraid server newt endpoint that is being a pain.
Expected Behavior
Work consistently?
@evakq8r commented on GitHub (Dec 2, 2025):
Self-inflicted issue; after going through the Pangolin discord, I've realised I added a Newt config when I should have just used local. Swapping the Pangolin entries to local now works as expected.