AWS VPS stuck at pinging attempt n+ #1508

Closed
opened 2026-04-05 19:31:31 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @dannymk on 5/10/2025

Pangolin: v1.2.0 running at: https://myproxyhost.com

Connecting using newt:

newt --id ajdfklajkad12l12 --secret pquiopuqeiouquuqruqpruqryqp --endpoint https://myproxyhost.com

I get this error:

...
2025-05-10T02:02:30Z INF Testing certificate renew... acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=letsencrypt.acme
2025-05-10T02:02:30Z ERR Provider error, retrying in 742.941798ms error="cannot fetch configuration data: do fetch request: Get "http://pangolin:3001/api/v1/traefik-config": dial tcp 172.18.0.3:3001: connect: connection refused" providerName=http
2025-05-10T02:02:31Z ERR Provider error, retrying in 1.006729189s error="cannot fetch configuration data: do fetch request: Get "http://pangolin:3001/api/v1/traefik-config": dial tcp 172.18.0.3:3001: connect: connection refused" providerName=http
2025-05-10T02:02:32Z ERR Provider error, retrying in 611.320033ms error="cannot fetch configuration data: do fetch request: Get "http://pangolin:3001/api/v1/traefik-config": dial tcp 172.18.0.3:3001: connect: connection refused" providerName=http
....

Then get stuck at:
...
INFO: 2025/05/10 02:17:13 Ping attempt 39
INFO: 2025/05/10 02:17:13 Pinging 100.89.128.1
WARN: 2025/05/10 02:17:23 Ping attempt 39 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/05/10 02:17:28 Pinging 100.89.128.1

I create the certificates and do not use the wildcard automatic certificate by let's encrypt that comes with Pangolin.

It seems it is "mostly" working but I just need that little bit to get the system to work properly.

Are there any guides that do not use the automatic lets encrypt certificates and we can just create the certificates manually and configure every site?

*Originally created by @dannymk on 5/10/2025* Pangolin: v1.2.0 running at: https://myproxyhost.com Connecting using newt: newt --id ajdfklajkad12l12 --secret pquiopuqeiouquuqruqpruqryqp --endpoint https://myproxyhost.com I get this error: ... 2025-05-10T02:02:30Z INF Testing certificate renew... acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=letsencrypt.acme 2025-05-10T02:02:30Z ERR Provider error, retrying in 742.941798ms error="cannot fetch configuration data: do fetch request: Get \"http://pangolin:3001/api/v1/traefik-config\": dial tcp 172.18.0.3:3001: connect: connection refused" providerName=http 2025-05-10T02:02:31Z ERR Provider error, retrying in 1.006729189s error="cannot fetch configuration data: do fetch request: Get \"http://pangolin:3001/api/v1/traefik-config\": dial tcp 172.18.0.3:3001: connect: connection refused" providerName=http 2025-05-10T02:02:32Z ERR Provider error, retrying in 611.320033ms error="cannot fetch configuration data: do fetch request: Get \"http://pangolin:3001/api/v1/traefik-config\": dial tcp 172.18.0.3:3001: connect: connection refused" providerName=http .... Then get stuck at: ... INFO: 2025/05/10 02:17:13 Ping attempt 39 INFO: 2025/05/10 02:17:13 Pinging 100.89.128.1 WARN: 2025/05/10 02:17:23 Ping attempt 39 failed: failed to read ICMP packet: i/o timeout INFO: 2025/05/10 02:17:28 Pinging 100.89.128.1 I create the certificates and do not use the wildcard automatic certificate by let's encrypt that comes with Pangolin. It seems it is "mostly" working but I just need that little bit to get the system to work properly. Are there any guides that do not use the automatic lets encrypt certificates and we can just create the certificates manually and configure every site?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#1508