Skip to content

After rebasing to 80.0b2 moat is broken

While testing the rebased work in tor-browser#40023 (closed) on desktop I encountered

08-17 15:10:06] TorLauncher INFO: The meek client process has been started
[08-17 15:10:06] TorLauncher DBUG: meek client stdout: VERSION 1
CMETHOD meek_lite socks5 127.0.0.1:43279
CMETHODS DONE

[08-17 15:10:06] TorLauncher DBUG: meek client proxy type: socks
[08-17 15:10:06] TorLauncher DBUG: meek client proxy IP: 127.0.0.1
[08-17 15:10:06] TorLauncher DBUG: meek client proxy port: 43279
[08-17 15:10:06] TorLauncher VERB: Moat JSON request:
{"data":[{"version":"0.1.0","type":"client-transports","supported":["obfs4"]}]}
JavaScript error: resource://torlauncher/modules/tl-bridgedb.jsm, line
590: NS_ERROR_FAILURE: Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIChannel.asyncOpen]

when trying to use moat.

Might be a rebase issue or just the normal need for Tor Launcher adjustment, I am not sure.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
OSZAR »