Toolforge is failing to access through https web.archive.org, tried v4 and v6:
```
tools.wm-lol@tools-bastion-15:~$ toolforge jobs run --image trixie --command 'curl -4 https://web.archive.org' testcurl
tools.wm-lol@tools-bastion-15:~$ cat testcurl*
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 145k 0 145k 0 0 355k 0 --:--:-- --:--:-- --:--:-- 356k
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to web.archive.org port 443 after 71 ms: Could not connect to server
```
```
tools.wm-lol@tools-bastion-15:~$ toolforge jobs run --command 'curl -6 https://web.archive.org/' testcurl --image trixie
tools.wm-lol@tools-bastion-15:~$ cat testcurl.*
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: web.archive.org
```
Now it's working for me though, might be a specific worker or a subset, looking.
This was noticed by a user when running the job/bot:
```
tools.pid-bangladesh-uploadbot2@tools-bastion-15:~$ tail -f ~/pid-bot.out
```
looking
Workers found with the issue so far:
* tools-k8s-worker-nfs-80
* tools-k8s-worker-nfs-57
Snippet to test in a node:
```
dcaro@tools-bastion-15:~$ kubectl-sudo run test-pod --image=docker-registry.svc.toolforge.org/toolforge-trixie-web-sssd:latest --restart=Never --overrides='{
"spec": {
"nodeName": "tools-k8s-worker-nfs-57"
}
}' --rm -it -- /bin/bash
If you don't see a command prompt, try pressing enter.
root@test-pod:/# curl https://web.archive.org
curl: (7) Failed to connect to web.archive.org port 443 after 74 ms: Could not connect to server
```