Bug: timeout gathering ipv4 #356

New Issue

saavagebueno · 2025-11-20T04:23:06-05:00

saavagebueno commented

2025-11-20 04:23:06 -05:00

Originally created by @teeesss on GitHub (Jan 30, 2024).

2024-01-30T15:41:13.008288086Z 2024-01-30T09:41:13-06:00 WARN obtaining ipv4 address: try 1 of 3: Get "https://api.ipify.org": context deadline exceeded
2024-01-30T15:41:16.010218167Z 2024-01-30T09:41:16-06:00 WARN obtaining ipv4 address: try 2 of 3: dial tcp4 1.1.1.1:853: i/o timeout
2024-01-30T15:41:16.123456475Z 2024-01-30T09:41:16-06:00 INFO obtaining ipv4 address: succeeded after 3 tries

I'm unable to curl https://api.ipify.org but I can curl https://api64.ipify.org successfully
Also timeouts showing up for 1.1.1.1:853

Running docker-compose on Synology NAS, DSM 7.2
DNS: 9.9.9.9/1.1.1.1

Originally created by @teeesss on GitHub (Jan 30, 2024). ``` 2024-01-30T15:41:13.008288086Z 2024-01-30T09:41:13-06:00 WARN obtaining ipv4 address: try 1 of 3: Get "https://api.ipify.org": context deadline exceeded 2024-01-30T15:41:16.010218167Z 2024-01-30T09:41:16-06:00 WARN obtaining ipv4 address: try 2 of 3: dial tcp4 1.1.1.1:853: i/o timeout 2024-01-30T15:41:16.123456475Z 2024-01-30T09:41:16-06:00 INFO obtaining ipv4 address: succeeded after 3 tries ``` I'm unable to curl `https://api.ipify.org` but I can curl `https://api64.ipify.org` successfully Also timeouts showing up for `1.1.1.1:853` Running docker-compose on Synology NAS, DSM 7.2 DNS: 9.9.9.9/1.1.1.1

saavagebueno added the Priority: 💤 Low priority Category: IP fetching 📥Closed: ⚰️ Inactive labels 2025-11-20 04:23:06 -05:00

saavagebueno closed this issue

2025-11-20 04:23:06 -05:00

saavagebueno commented

2025-11-20 04:23:06 -05:00

@qdm12 commented on GitHub (Jan 31, 2024):

Both https://api.ipify.org/ and https://api64.ipify.org work for me, are you sure this happens often?
I've added the api64 variant in 5f15edde5188167e5f30fa4da191c8bfaca687e3 although it's only for "ipv4 or ipv6" since it would return one of the two depending on your setup.
For tcp4 1.1.1.1:853 this can happen from time to time I guess, make sure your firewall/router isn't blocking it 🤔
As long as it manages to succeed after N tries, that's what matters 😉

@qdm12 commented on GitHub (Jan 31, 2024): Both https://api.ipify.org/ and https://api64.ipify.org work for me, are you sure this happens often? I've added the api64 variant in 5f15edde5188167e5f30fa4da191c8bfaca687e3 although it's only for "ipv4 or ipv6" since it would return one of the two depending on your setup. For `tcp4 1.1.1.1:853` this can happen from time to time I guess, make sure your firewall/router isn't blocking it 🤔 As long as it manages to succeed after N tries, that's what matters 😉

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ddns-updater#356