Online check failing

[pettijohn]

Using ER-X, upgraded firmware from 2.0.9-hotfix.6 to .7. After upgrade, Wireguard did not come back online.

2025-01-18/03:09:54.261403219 [wizard] EdgeMAX WireGuard Wizard started - Session=10901
2025-01-18/03:09:54.344844320 [wizard] WireGuard wizard found at /config/wizard/feature/WireGuard/wizard-run
dpkg-query: no packages found matching wireguard
2025-01-18/03:09:54.429664274 [wizard] wireguard package not installed! need to install packages.
2025-01-18/03:09:54.439450873 [installer] Starting installation of WireGuard from /config/user-data/wireguard/ ...
2025-01-18/03:09:54.453880544 [installer] check if we are online (if we can reach github.com) ...
2025-01-18/03:11:22.552354311 [installer] online-check failed ...
2025-01-18/03:11:22.560223905 [installer] Check system where we are running ...
2025-01-18/03:11:22.607027262 [installer] Detected EdgeRouter e50 system ...
2025-01-18/03:11:22.672687022 [installer] Detected EdgeOS version v2 ...
2025-01-18/03:11:22.681761292 [installer] Checking for e50-v2 deb-file in /config/user-data/wireguard ...
2025-01-18/03:11:22.706559035 [installer] WireGuard deb-file not found, need to download from latest release ...
2025-01-18/03:11:22.714567932 [installer] Error: we are not online, can not download. Missing deb-file. Exit.

Further debugging, copying the onlinecheck command but replacing -s with --verbose https://github.com/vchrizz/ER-wizard-WireGuard/blob/main/wizard-run#L94C5-L94C106

$ curl --verbose --retry 12 --retry-max-time 60 --retry-connrefused --connect-timeout 3 https://api.github.com
* Rebuilt URL to: https://api.github.com/
* Resolving timed out after 3548 milliseconds
* Curl_http_done: called premature == 1
* stopped the pause stream!
* Closing connection 0
Warning: Transient problem: timeout Will retry in 1 seconds. 12 retries left.
^C

Resolving timeout. But host api.github.com works

$ host api.github.com
api.github.com. has IPv4 address 140.82.116.6
Host api.github.com. has no AAAA record
Host api.github.com. has no MX record

Increasing or removing --connect-timeout in the curl command fixes the glitch. I'm not sure what is causing curl to take so long to connect or resolve the name. The host command completes in 4ms.