meek-azure and moat are down
We received multiple reports that on frontdesk and social media that meek-azure and Moat are down. Below an email with more details.
Both meek-azure and moat (used for fetching new obfs4 bridges from a censored location) are down. obfs4 works normally. Current location is the United States.
Unlike previous outages I've noticed, this one fails quickly and early into the connection attempt with a TLS error (instead of e.g. eventually timing out), suggesting a type of issue that hasn't occurred before.
Issue occurs on a fresh install of the latest version of Tor Browser for win32, win64, and Android (as well as Orbot). Windows (64-bit) log reproduced below, though it looks similar on all devices I've tried.
It doesn't look like this issue has been reported on GitLab yet. I've requested an account; currently awaiting approval.
12/5/20, 19:54:42.301 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
12/5/20, 19:54:42.301 [NOTICE] Opening Socks listener on 127.0.0.1:9150
12/5/20, 19:54:42.301 [NOTICE] Opened Socks listener on 127.0.0.1:9150
12/5/20, 19:54:45.298 [NOTICE] Bootstrapped 1% (conn_pt): Connecting to pluggable transport
12/5/20, 19:54:45.301 [NOTICE] Bootstrapped 2% (conn_done_pt): Connected to pluggable transport
12/5/20, 19:54:45.306 [NOTICE] Bootstrapped 10% (conn_done): Connected to a relay
12/5/20, 19:54:45.646 [WARN] Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (TLS_ERROR; TLS_ERROR; count 1; recommendation warn; host 97700DFE9F483596DDA6264C4D7DF7641E1E39CE at 0.0.2.0:2)
12/5/20, 19:54:45.647 [WARN] 1 connections have failed:
12/5/20, 19:54:45.647 [WARN] 1 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE
12/5/20, 19:54:45.673 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
12/5/20, 19:54:45.674 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
12/5/20, 19:54:46.242 [WARN] Pluggable Transport process terminated with status code 0