You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the very installation of the worker, I noticed that the mullvad-check request (executed on the wireguard container) at the beginning of the manager failed.
I thought it could be a race condition in the initialization and left it for later.
Having left the worker all week end I realize it failed to process tests and logs are full of
[2024-08-05 07:38:49,088: INFO] Sleeping for 300.0s
[2024-08-05 07:44:01,252: ERROR] docker api error for exec_command (attempt 1): Unable to execute command ['curl', '--interface', 'wg0', '-s', 'https://am.i.mullvad.net/json'] in mirrors-qa-wireguard, result: b'', status: 6
[2024-08-05 07:44:16,682: ERROR] docker api error for exec_command (attempt 2): Unable to execute command ['curl', '--interface', 'wg0', '-s', 'https://am.i.mullvad.net/json'] in mirrors-qa-wireguard, result: b'', status: 6
[2024-08-05 07:44:37,776: ERROR] docker api error for exec_command (attempt 3): Unable to execute command ['curl', '--interface', 'wg0', '-s', 'https://am.i.mullvad.net/json'] in mirrors-qa-wireguard, result: b'', status: 6
[2024-08-05 07:45:06,493: ERROR] error while processing tasks Unable to execute command ['curl', '--interface', 'wg0', '-s', 'https://am.i.mullvad.net/json'] in mirrors-qa-wireguard, result: b'', status: 6
[2024-08-05 07:45:06,493: INFO] Sleeping for 300.0s
[2024-08-05 07:50:18,091: ERROR] docker api error for exec_command (attempt 1): Unable to execute command ['curl', '--interface', 'wg0', '-s', 'https://am.i.mullvad.net/json'] in mirrors-qa-wireguard, result: b'', status: 6
[2024-08-05 07:50:35,415: ERROR] docker api error for exec_command (attempt 2): Unable to execute command ['curl', '--interface', 'wg0', '-s', 'https://am.i.mullvad.net/json'] in mirrors-qa-wireguard, result: b'', status: 6
[2024-08-05 07:50:57,949: ERROR] docker api error for exec_command (attempt 3): Unable to execute command ['curl', '--interface', 'wg0', '-s', 'https://am.i.mullvad.net/json'] in mirrors-qa-wireguard, result: b'', status: 6
[2024-08-05 07:51:23,729: ERROR] error while processing tasks Unable to execute command ['curl', '--interface', 'wg0', '-s', 'https://am.i.mullvad.net/json'] in mirrors-qa-wireguard, result: b'', status: 6
That exit-code 6 error in curl is a resolve error. Executing without -s is explicit: curl: (6) Could not resolve host: am.i.mullvad.net
It's not a DNS-only issue as the following dont work either:
root@d0dc5d0d7006:/# curl --interface wg0 --resolve 'am.i.mullvad.net:443:45.83.223.233' https://am.i.mullvad.net/json
curl: (28) Failed to connect to am.i.mullvad.net port 443 after 129775 ms: Could not connect to server
root@d0dc5d0d7006:/# curl --interface wg0 --connect-to 'am.i.mullvad.net:443:45.83.223.233:443' https://am.i.mullvad.net/json
curl: (28) Failed to connect to 45.83.223.233 port 443 after 130806 ms: Could not connect to server
I can see that at the moment, it's linked to one of the US server but we didn't receive any data
root@d0dc5d0d7006:/# wg show
interface: wg0
public key: ew/S+MT5IX/wKx4ITIWoLCqhrC66mS6jK2cdnMP60Ho=
private key: (hidden)
listening port: 40760
fwmark: 0xca6c
peer: NODBnzBgLO5Itv+HOyQer7jpVn1UdCKfv9uwAAvvMkA=
endpoint: 185.156.46.130:51820
allowed ips: 0.0.0.0/0, ::/0
transfer: 0 B received, 4.80 MiB sent
That endpoint IP is publicly ping-able but it does not work from the container.
The text was updated successfully, but these errors were encountered:
From the very installation of the worker, I noticed that the mullvad-check request (executed on the wireguard container) at the beginning of the manager failed.
I thought it could be a race condition in the initialization and left it for later.
Having left the worker all week end I realize it failed to process tests and logs are full of
That exit-code
6
error in curl is a resolve error. Executing without-s
is explicit:curl: (6) Could not resolve host: am.i.mullvad.net
It's not a DNS-only issue as the following dont work either:
I can see that at the moment, it's linked to one of the US server but we didn't receive any data
That endpoint IP is publicly ping-able but it does not work from the container.
The text was updated successfully, but these errors were encountered: