Pangolin (ECONNRESET, ECONNABORTED) and traefik (cannot fetch configuration data) error messages on fresh install #623

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

Hum something is definitely causing the Pangolin container to not
respond to api calls.

Did you install from the installer?

Is there any more context from the logs you might be able to share?

@oschwartz10612 commented on GitHub (Aug 31, 2025): Hum something is definitely causing the Pangolin container to not respond to api calls. Did you install from the installer? Is there any more context from the logs you might be able to share?

GiteaMirror commented

@krod1408 commented on GitHub (Sep 7, 2025):

This is a problem i have everything set up correct on my vps and was working fine...out of the blue cant connect ...suspect dns but not sure its not the settings its what somehow has changed because everything was working fine until its not and that is a problem.

@krod1408 commented on GitHub (Sep 7, 2025): This is a problem i have everything set up correct on my vps and was working fine...out of the blue cant connect ...suspect dns but not sure its not the settings its what somehow has changed because everything was working fine until its not and that is a problem.

GiteaMirror commented

@clunky944 commented on GitHub (Sep 8, 2025):

I installed it fresh from the installer. But couldn't get it to work no matter what. I reset the whole VPS and did a fresh install of the OS, which seemed to have fixed this. But I have no idea why it did not work the first time in near identical conditions.

@clunky944 commented on GitHub (Sep 8, 2025): I installed it fresh from the installer. But couldn't get it to work no matter what. I reset the whole VPS and did a fresh install of the OS, which seemed to have fixed this. But I have no idea why it did not work the first time in near identical conditions.

GiteaMirror commented

@krod1408 commented on GitHub (Sep 8, 2025):

Yeah, this is bullshit...everything works and all of a sudden it does not major problem....needs to be looked at this is a disaster.

@krod1408 commented on GitHub (Sep 8, 2025): Yeah, this is bullshit...everything works and all of a sudden it does not major problem....needs to be looked at this is a disaster.

GiteaMirror commented

@krod1408 commented on GitHub (Sep 8, 2025):

I am not a 100% but dns and something have a play in this along with the domain name and this will fuck all of us up.

@krod1408 commented on GitHub (Sep 8, 2025): I am not a 100% but dns and something have a play in this along with the domain name and this will fuck all of us up.

GiteaMirror commented

@krod1408 commented on GitHub (Sep 8, 2025):

I could only imagine what would happen if you install this and everything is working fine and you put it in production and out of the blu this happens and no one has a answer for it no wayyyyy

@krod1408 commented on GitHub (Sep 8, 2025): I could only imagine what would happen if you install this and everything is working fine and you put it in production and out of the blu this happens and no one has a answer for it no wayyyyy

GiteaMirror commented

@oschwartz10612 commented on GitHub (Sep 8, 2025):

Hi @krod1408 could you share any logs from your instance? Maybe we can troubleshoot.

@oschwartz10612 commented on GitHub (Sep 8, 2025): Hi @krod1408 could you share any logs from your instance? Maybe we can troubleshoot.

GiteaMirror commented

@krod1408 commented on GitHub (Sep 15, 2025):

I have removed pangolin and reinstalled traefik and everything is now working fine. Like i said it ran fine and then just stopped forwarding....tunneling sites...i read one person said the same and he removed is instance and it was fine after creating a new vps I did not feel like removing my vps and just went back with traefik and other things that i know just work.

@krod1408 commented on GitHub (Sep 15, 2025): I have removed pangolin and reinstalled traefik and everything is now working fine. Like i said it ran fine and then just stopped forwarding....tunneling sites...i read one person said the same and he removed is instance and it was fine after creating a new vps I did not feel like removing my vps and just went back with traefik and other things that i know just work.

GiteaMirror commented

@mjarms commented on GitHub (Sep 25, 2025):

@oschwartz10612
I have the same problem since this morning : everything was working fine then it has stopped working suddenly. I made a slight change on DNS before that shouldn't impact the server as far as I know (but maybe @krod1408 did the same so could be related somehow ??). It's still the same DNS provider with the same entries though.

I first rebooted my VPS then tried restarting all containers, same issue. Local IP is still accessible (giving 404 not found but still) but with domain name it returns 403.

Traefik container logs shows this after restart :

{"level":"info","time":"2025-09-25T10:53:53Z","message":"I have to go..."}
{"level":"info","time":"2025-09-25T10:53:53Z","message":"Stopping server gracefully"}
{"level":"info","time":"2025-09-25T10:54:03Z","message":"Server stopped"}
{"level":"info","time":"2025-09-25T10:54:03Z","message":"Shutting down"}
{"level":"info","version":"3.5.2","time":"2025-09-25T10:54:04Z","message":"Traefik version 3.5.2 built on 2025-09-09T10:17:00Z"}
{"level":"info","time":"2025-09-25T10:54:04Z","message":"\nStats collection is disabled.\nHelp us improve Traefik by turning this feature on :)\nMore details on: https://doc.traefik.io/traefik/contributing/data-collection/\n"}
{"level":"info","plugins":["badger","crowdsec"],"time":"2025-09-25T10:54:04Z","message":"Loading plugins..."}
{"level":"info","plugins":["badger","crowdsec"],"time":"2025-09-25T10:54:05Z","message":"Plugins loaded."}
{"level":"info","time":"2025-09-25T10:54:05Z","message":"Starting provider aggregator *aggregator.ProviderAggregator"}
{"level":"info","time":"2025-09-25T10:54:05Z","message":"Starting provider *file.Provider"}
{"level":"info","time":"2025-09-25T10:54:05Z","message":"Starting provider *traefik.Provider"}
{"level":"info","time":"2025-09-25T10:54:05Z","message":"Starting provider *http.Provider"}
{"level":"info","time":"2025-09-25T10:54:05Z","message":"Starting provider *acme.ChallengeTLSALPN"}
{"level":"info","time":"2025-09-25T10:54:05Z","message":"Starting provider *acme.Provider"}
{"level":"info","providerName":"letsencrypt.acme","acmeCA":"https://acme-v02.api.letsencrypt.org/directory","time":"2025-09-25T10:54:05Z","message":"Testing certificate renew..."}
{"level":"error","providerName":"http","error":"cannot fetch configuration data: do fetch request: Get \"http://pangolin:3001/api/v1/traefik-config\": dial tcp 172.18.0.4:3001: connect: connection refused","time":"2025-09-25T10:57:05Z","message":"Provider error, retrying in 506.800349ms"}
{"level":"error","providerName":"http","error":"cannot fetch configuration data: do fetch request: Get \"http://pangolin:3001/api/v1/traefik-config\": dial tcp 172.18.0.4:3001: connect: connection refused","time":"2025-09-25T10:57:05Z","message":"Provider error, retrying in 885.195965ms"}

Gerbil container :

ERROR: 2025/09/25 11:03:58 Error reading UDP packet: read udp [::]:21820: use of closed network connection
ERROR: 2025/09/25 11:03:58 Error reading UDP packet: read udp [::]:21820: use of closed network connection
... (like 100 times)
ERROR: 2025/09/25 11:03:58 Error reading UDP packet: read udp [::]:21820: use of closed network connection
INFO: 2025/09/25 11:04:00 Fetching remote config from http://pangolin:3001/api/v1/gerbil/get-config
INFO: 2025/09/25 11:04:00 Created WireGuard interface wg0
INFO: 2025/09/25 11:04:00 Assigned IP address 100.89.128.1/24 to interface wg0
INFO: 2025/09/25 11:04:00 Attempting to delete existing MSS clamping rule for chain INPUT
INFO: 2025/09/25 11:04:00 Attempting to delete existing MSS clamping rule for chain OUTPUT
INFO: 2025/09/25 11:04:00 Attempting to delete existing MSS clamping rule for chain FORWARD
INFO: 2025/09/25 11:04:00 Adding MSS clamping rule for chain `INPUT`
INFO: 2025/09/25 11:04:00 Successfully added and verified MSS clamping rule for chain INPUT
INFO: 2025/09/25 11:04:00 Adding MSS clamping rule for chain OUTPUT
INFO: 2025/09/25 11:04:00 Successfully added and verified MSS clamping rule for chain OUTPUT
INFO: 2025/09/25 11:04:00 Adding MSS clamping rule for chain FORWARD
INFO: 2025/09/25 11:04:00 Successfully added and verified MSS clamping rule for chain FORWARD
INFO: 2025/09/25 11:04:00 WireGuard interface wg0 created and configured
INFO: 2025/09/25 11:04:00 Peer [ANONYMIZED]+[ANONYMIZED]= added successfully
INFO: 2025/09/25 11:04:00 Peer [ANONYMIZED]+[ANONYMIZED]= added successfully
INFO: 2025/09/25 11:04:00 Received initial mappings: {"mappings":{"[ANONYMIZED]:56303":{"destinations":[{"destinationIP":"100.89.128.8","destinationPort":55527}]},"[ANONYMIZED]:55527":{"destinations":[{"destinationIP":"100.89.128.4","destinationPort":56303}]}}}
INFO: 2025/09/25 11:04:00 Loaded 2 initial proxy mappings
INFO: 2025/09/25 11:04:00 UDP server listening on :21820
INFO: 2025/09/25 11:04:00 Starting HTTP server on :3003

Pangolin container :

> @fosrl/pangolin@0.0.0 start
> ENVIRONMENT=prod node dist/migrations.mjs && ENVIRONMENT=prod NODE_ENV=development node --enable-source-maps dist/server.mjs

Starting migrations from version 1.10.1
Migrations to run:
All migrations completed successfully
2025-09-25T10:57:05.655Z [info]: Started offline checker interval
2025-09-25T10:57:05.671Z [warn]: Email SMTP configuration is missing. Emails will not be sent.
2025-09-25T10:57:05.894Z [warn]: Server admin exists. Setup token generation skipped.
2025-09-25T10:57:05.895Z [info]: Pangolin now gathers anonymous usage data to help us better understand how the software is used and guide future improvements and feature development. You can find more details, including instructions for opting out of this anonymous data collection, at: https://docs.digpangolin.com/telemetry
2025-09-25T10:57:06.491Z [info]: API server is running on http://localhost:3000
2025-09-25T10:57:06.491Z [info]: Internal server is running on http://localhost:3001
2025-09-25T10:57:08.100Z [info]: Next.js server is running on http://localhost:3002
2025-09-25T10:57:08.352Z [info]: Establishing websocket connection
2025-09-25T10:57:08.352Z [info]: Client added to tracking - NEWT ID: [ANONYMIZED], Connection ID: [ANONYMIZED], Total connections: 1
2025-09-25T10:57:08.353Z [info]: WebSocket connection established - NEWT ID: [ANONYMIZED]
2025-09-25T10:57:08.424Z [info]: Establishing websocket connection
2025-09-25T10:57:08.425Z [info]: Client added to tracking - NEWT ID: [ANONYMIZED], Connection ID: [ANONYMIZED], Total connections: 1
2025-09-25T10:57:08.425Z [info]: WebSocket connection established - NEWT ID: [ANONYMIZED]
2025-09-25T11:04:00.158Z [info]: Updated exit node

If there's a solution that could solve this without having to re-install Pangolin and configure everything again, that would be nice !

@mjarms commented on GitHub (Sep 25, 2025): @oschwartz10612 I have the same problem since this morning : everything was working fine then it has stopped working suddenly. I made a slight change on DNS before that shouldn't impact the server as far as I know (but maybe @krod1408 did the same so could be related somehow ??). It's still the same DNS provider with the same entries though. I first rebooted my VPS then tried restarting all containers, same issue. Local IP is still accessible (giving 404 not found but still) but with domain name it returns 403. Traefik container logs shows this after restart : ``` {"level":"info","time":"2025-09-25T10:53:53Z","message":"I have to go..."} {"level":"info","time":"2025-09-25T10:53:53Z","message":"Stopping server gracefully"} {"level":"info","time":"2025-09-25T10:54:03Z","message":"Server stopped"} {"level":"info","time":"2025-09-25T10:54:03Z","message":"Shutting down"} {"level":"info","version":"3.5.2","time":"2025-09-25T10:54:04Z","message":"Traefik version 3.5.2 built on 2025-09-09T10:17:00Z"} {"level":"info","time":"2025-09-25T10:54:04Z","message":"\nStats collection is disabled.\nHelp us improve Traefik by turning this feature on :)\nMore details on: https://doc.traefik.io/traefik/contributing/data-collection/\n"} {"level":"info","plugins":["badger","crowdsec"],"time":"2025-09-25T10:54:04Z","message":"Loading plugins..."} {"level":"info","plugins":["badger","crowdsec"],"time":"2025-09-25T10:54:05Z","message":"Plugins loaded."} {"level":"info","time":"2025-09-25T10:54:05Z","message":"Starting provider aggregator *aggregator.ProviderAggregator"} {"level":"info","time":"2025-09-25T10:54:05Z","message":"Starting provider *file.Provider"} {"level":"info","time":"2025-09-25T10:54:05Z","message":"Starting provider *traefik.Provider"} {"level":"info","time":"2025-09-25T10:54:05Z","message":"Starting provider *http.Provider"} {"level":"info","time":"2025-09-25T10:54:05Z","message":"Starting provider *acme.ChallengeTLSALPN"} {"level":"info","time":"2025-09-25T10:54:05Z","message":"Starting provider *acme.Provider"} {"level":"info","providerName":"letsencrypt.acme","acmeCA":"https://acme-v02.api.letsencrypt.org/directory","time":"2025-09-25T10:54:05Z","message":"Testing certificate renew..."} {"level":"error","providerName":"http","error":"cannot fetch configuration data: do fetch request: Get \"http://pangolin:3001/api/v1/traefik-config\": dial tcp 172.18.0.4:3001: connect: connection refused","time":"2025-09-25T10:57:05Z","message":"Provider error, retrying in 506.800349ms"} {"level":"error","providerName":"http","error":"cannot fetch configuration data: do fetch request: Get \"http://pangolin:3001/api/v1/traefik-config\": dial tcp 172.18.0.4:3001: connect: connection refused","time":"2025-09-25T10:57:05Z","message":"Provider error, retrying in 885.195965ms"} ``` Gerbil container : ``` ERROR: 2025/09/25 11:03:58 Error reading UDP packet: read udp [::]:21820: use of closed network connection ERROR: 2025/09/25 11:03:58 Error reading UDP packet: read udp [::]:21820: use of closed network connection ... (like 100 times) ERROR: 2025/09/25 11:03:58 Error reading UDP packet: read udp [::]:21820: use of closed network connection INFO: 2025/09/25 11:04:00 Fetching remote config from http://pangolin:3001/api/v1/gerbil/get-config INFO: 2025/09/25 11:04:00 Created WireGuard interface wg0 INFO: 2025/09/25 11:04:00 Assigned IP address 100.89.128.1/24 to interface wg0 INFO: 2025/09/25 11:04:00 Attempting to delete existing MSS clamping rule for chain INPUT INFO: 2025/09/25 11:04:00 Attempting to delete existing MSS clamping rule for chain OUTPUT INFO: 2025/09/25 11:04:00 Attempting to delete existing MSS clamping rule for chain FORWARD INFO: 2025/09/25 11:04:00 Adding MSS clamping rule for chain `INPUT` INFO: 2025/09/25 11:04:00 Successfully added and verified MSS clamping rule for chain INPUT INFO: 2025/09/25 11:04:00 Adding MSS clamping rule for chain OUTPUT INFO: 2025/09/25 11:04:00 Successfully added and verified MSS clamping rule for chain OUTPUT INFO: 2025/09/25 11:04:00 Adding MSS clamping rule for chain FORWARD INFO: 2025/09/25 11:04:00 Successfully added and verified MSS clamping rule for chain FORWARD INFO: 2025/09/25 11:04:00 WireGuard interface wg0 created and configured INFO: 2025/09/25 11:04:00 Peer [ANONYMIZED]+[ANONYMIZED]= added successfully INFO: 2025/09/25 11:04:00 Peer [ANONYMIZED]+[ANONYMIZED]= added successfully INFO: 2025/09/25 11:04:00 Received initial mappings: {"mappings":{"[ANONYMIZED]:56303":{"destinations":[{"destinationIP":"100.89.128.8","destinationPort":55527}]},"[ANONYMIZED]:55527":{"destinations":[{"destinationIP":"100.89.128.4","destinationPort":56303}]}}} INFO: 2025/09/25 11:04:00 Loaded 2 initial proxy mappings INFO: 2025/09/25 11:04:00 UDP server listening on :21820 INFO: 2025/09/25 11:04:00 Starting HTTP server on :3003 ``` Pangolin container : ``` > @fosrl/pangolin@0.0.0 start > ENVIRONMENT=prod node dist/migrations.mjs && ENVIRONMENT=prod NODE_ENV=development node --enable-source-maps dist/server.mjs Starting migrations from version 1.10.1 Migrations to run: All migrations completed successfully 2025-09-25T10:57:05.655Z [info]: Started offline checker interval 2025-09-25T10:57:05.671Z [warn]: Email SMTP configuration is missing. Emails will not be sent. 2025-09-25T10:57:05.894Z [warn]: Server admin exists. Setup token generation skipped. 2025-09-25T10:57:05.895Z [info]: Pangolin now gathers anonymous usage data to help us better understand how the software is used and guide future improvements and feature development. You can find more details, including instructions for opting out of this anonymous data collection, at: https://docs.digpangolin.com/telemetry 2025-09-25T10:57:06.491Z [info]: API server is running on http://localhost:3000 2025-09-25T10:57:06.491Z [info]: Internal server is running on http://localhost:3001 2025-09-25T10:57:08.100Z [info]: Next.js server is running on http://localhost:3002 2025-09-25T10:57:08.352Z [info]: Establishing websocket connection 2025-09-25T10:57:08.352Z [info]: Client added to tracking - NEWT ID: [ANONYMIZED], Connection ID: [ANONYMIZED], Total connections: 1 2025-09-25T10:57:08.353Z [info]: WebSocket connection established - NEWT ID: [ANONYMIZED] 2025-09-25T10:57:08.424Z [info]: Establishing websocket connection 2025-09-25T10:57:08.425Z [info]: Client added to tracking - NEWT ID: [ANONYMIZED], Connection ID: [ANONYMIZED], Total connections: 1 2025-09-25T10:57:08.425Z [info]: WebSocket connection established - NEWT ID: [ANONYMIZED] 2025-09-25T11:04:00.158Z [info]: Updated exit node ``` If there's a solution that could solve this without having to re-install Pangolin and configure everything again, that would be nice !

GiteaMirror commented

@keonramses commented on GitHub (Sep 27, 2025):

This happened to me today, and the only way I could get it back up was to delete any related data and run the installer again. But that it failed without any warning whatsoever is weird, considering that gerbil and pangolin report no errors. Either I am grateful for this software and hope we continue to grow as a platform (very stable platform). Also, a way to back up and restore whatever we have configured would be a nice addition for cases like this, when you have no choice but to nuke your install.

Thank you.

@keonramses commented on GitHub (Sep 27, 2025): This happened to me today, and the only way I could get it back up was to delete any related data and run the installer again. But that it failed without any warning whatsoever is weird, considering that gerbil and pangolin report no errors. Either I am grateful for this software and hope we continue to grow as a platform (very stable platform). Also, a way to back up and restore whatever we have configured would be a nice addition for cases like this, when you have no choice but to nuke your install. Thank you.

GiteaMirror commented

@clunky944 commented on GitHub (Sep 27, 2025):

I am the OP of this issue. I have not faced this issue again after that one time, but I’m still being cautious.

For backups, I now run rsync on the pangolin folder from the VPS to my local machine weekly. If I ever need to nuke the installation, all I need to restore is to copy the pangolin folder back to the VPS and run “docker compose up”.

But we do need to get a fix for this since it appears so randomly and cannot be fixed easily.

@clunky944 commented on GitHub (Sep 27, 2025): I am the OP of this issue. I have not faced this issue again after that one time, but I’m still being cautious. For backups, I now run rsync on the pangolin folder from the VPS to my local machine weekly. If I ever need to nuke the installation, all I need to restore is to copy the pangolin folder back to the VPS and run “docker compose up”. But we do need to get a fix for this since it appears so randomly and cannot be fixed easily.

GiteaMirror commented

@miloschwartz commented on GitHub (Sep 27, 2025):

Mmm this is odd, not sure how to reproduce, but glad it's not happening any more. I'll leave this open in case it pops up again

@miloschwartz commented on GitHub (Sep 27, 2025): Mmm this is odd, not sure how to reproduce, but glad it's not happening any more. I'll leave this open in case it pops up again

GiteaMirror commented