Opened 6 months ago

Closed 6 months ago

#25807 closed defect (fixed)

Can not request bridges from torproject.org (App Engine is broken for moat)

Reported by: Dbryrtfbcbhgf Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Launcher Version:
Severity: Normal Keywords: GeorgKoppen201804, TorBrowserTeam201804R
Cc: mcs, brade, hiro Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Can not request bridges from torproject.org , Tor gets stuck at Contacting BridgeDB. please wait.
Direct connection to Tor Works.
TorBrowser 8a5

Child Tickets

Change History (7)

comment:1 Changed 6 months ago by cypherpunks

#25804
snowflake and moat stopped working

comment:2 Changed 6 months ago by gk

Resolution: duplicate
Status: newclosed

comment:3 Changed 6 months ago by gk

Cc: mcs brade hiro added
Resolution: duplicate
Status: closedreopened
Summary: Can not request bridges from torproject.orgCan not request bridges from torproject.org (App Engine is broken for moat)

Looking closer dcf seems to have #25804 for snowflake despite the generic title. Let's have that one for moat then.

The problem in #25804 is affecting Moat as well because we are doing something like

./TorBrowser/Tor/PluggableTransports/meek-client" "-url" "https://tor-bridges-hyphae-channel.appspot.com" "-front" "www.google.com" "--helper" "127.0.0.1:44219

I leave this ticket in the Tor Browser component right now even though we can't do anything about it until the issue at the BridgeDB side gets solved (or the App Engine starts to work for us again).

Last edited 6 months ago by gk (previous) (diff)

comment:4 in reply to:  3 Changed 6 months ago by isis

Replying to gk:

Looking closer dcf seems to have #25804 for snowflake despite the generic title. Let's have that one for moat then.

The problem in #25804 is affecting Moat as well because we are doing something like

./TorBrowser/Tor/PluggableTransports/meek-client" "-url" "https://tor-bridges-hyphae-channel.appspot.com" "-front" "www.google.com" "--helper" "127.0.0.1:44219

I leave this ticket in the Tor Browser component right now even though we can't do anything about it until the issue at the BridgeDB side gets solved (or the App Engine starts to work for us again).


Oh, wait… what is the issue on the BridgeDB server-side? (Did you maybe mean fixing/updating the middleware server for the meek-reflector?)

Last edited 6 months ago by gk (previous) (diff)

comment:5 Changed 6 months ago by gk

Component: Applications/Tor BrowserApplications/Tor Launcher
Keywords: GeorgKoppen201804 TorBrowserTeam201804R added
Status: reopenedneeds_review

Let's work around that for now. See bug_25807 (https://gitweb.torproject.org/user/gk/tor-launcher.git/commit/?h=bug_25807&id=add227697f9af12056ca26f6e510572cd9c5faef) in my public tor-launcher repo for a patch that works for me.

comment:6 in reply to:  5 ; Changed 6 months ago by mcs

Replying to gk:

Let's work around that for now. See bug_25807 (https://gitweb.torproject.org/user/gk/tor-launcher.git/commit/?h=bug_25807&id=add227697f9af12056ca26f6e510572cd9c5faef) in my public tor-launcher repo for a patch that works for me.

r=mcs
Your patch looks fine, but won't it be easy to block Moat now?

comment:7 in reply to:  6 Changed 6 months ago by gk

Resolution: fixed
Status: needs_reviewclosed

Replying to mcs:

Replying to gk:

Let's work around that for now. See bug_25807 (https://gitweb.torproject.org/user/gk/tor-launcher.git/commit/?h=bug_25807&id=add227697f9af12056ca26f6e510572cd9c5faef) in my public tor-launcher repo for a patch that works for me.

r=mcs
Your patch looks fine, but won't it be easy to block Moat now?

Yes, it will be much easier now. However, we don't have a setup ready to move away from Google. Thus, we are faced with the option to leave it broken for now or make it working again for users which could help shaking out more Moat related bugs or just give alpha users bridges in areas where the appengine is not blocked. It seems to me the latter is preferable (while we are trying to solve this issue in a more sustainable way).

Thanks for the review, I applied the patch to master (commit add227697f9af12056ca26f6e510572cd9c5faef).

Note: See TracTickets for help on using tickets.