wechall command failing with Connection refused on Bandit

Hi!

I'm trying to register my Bandit progress on WeChall, but the wechall command on the Bandit warbox is failing. My WECHALLUSER and WECHALLTOKEN are set correctly (I'm not getting an "Invalid Token" or "unknown user!" message — it never reaches the service). When I run wechall, I get:

Traceback (most recent call last):
File "/usr/local/bin/wechall", line 37, in <module>
ssl_sock.connect((host, port))
File "/usr/lib/python3.14/ssl.py", line 1405, in connect
self._real_connect(addr, False)
File "/usr/lib/python3.14/ssl.py", line 1392, in _real_connect
super().connect(addr)
ConnectionRefusedError: [Errno 111] Connection refused

It looks like the script can't establish an SSL connection to the WeChall server (connection refused), which seems to be on the server/service side rather than my configuration. This has been happening consistently over several hours.

Is the WeChall endpoint that the Bandit wechall script connects to currently down, or is there an IP/port mapping issue on the WeChall side? Any help would be appreciated.

Thanks!

Same Connection refused error here (Errno 111, SSL connect fails before reaching the service). A few others in the OTW Discord are reporting the exact same thing over the last day. The likely cause came up there: OverTheWire did a redeployment over the weekend, and per an OTW staff member the warbox's IP address probably changed — so WeChall's servers may still be pointing at the old IP, which is why the connection is refused before it ever reaches the service. Looks like it needs WeChall's side to update the new IP. Anyone able to confirm / push that update?

It seems the problem has been resolved!