uh, one of the connectivity check urls isn’t responding. Does it check for user-agent (java something)? The subdomain 204 is fine. Is that one phased out? cc @arnauvp
Failed to connect to connectivity.ecloud.global port 80 after 134236 ms: Couldn't connect to server
log
~$ for url in connectivity.ecloud.global 204.ecloud.global; do curl "$url" -I -v; done
* Host connectivity.ecloud.global:80 was resolved.
* IPv6: 2001:41d0:304:100::672
* IPv4: 51.91.138.20
* Trying [2001:41d0:304:100::672]:80...
* Trying 51.91.138.20:80...
* connect to 2001:41d0:304:100::672 port 80 from 2001:1a81:5370:a000:b210:4f66:af11:7fb3 port 50018 failed: Die Wartezeit für die Verbindung ist abgelaufen
* connect to 51.91.138.20 port 80 from 192.168.1.101 port 33400 failed: Die Wartezeit für die Verbindung ist abgelaufen
* Failed to connect to connectivity.ecloud.global port 80 after 134236 ms: Couldn't connect to server
* Closing connection
curl: (28) Failed to connect to connectivity.ecloud.global port 80 after 134236 ms: Couldn't connect to server
* Host 204.ecloud.global:80 was resolved.
* IPv6: 2a01:4f8:1c17:4e10:d00b::2
* IPv4: 157.90.154.178
* Trying [2a01:4f8:1c17:4e10:d00b::2]:80...
* Connected to 204.ecloud.global (2a01:4f8:1c17:4e10:d00b::2) port 80
> HEAD / HTTP/1.1
> Host: 204.ecloud.global
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 204 No Content
HTTP/1.1 204 No Content
< cache-control: no-cache
cache-control: no-cache
<
* Connection #0 to host 204.ecloud.global left intact