Opened 2 years ago

Closed 22 months ago

#15523 closed defect (user disappeared)

Meek with google is much slower in TBB 4.0.5 than in TBB 4.0.3

Reported by: cypherpunks Owned by: dcf
Priority: Medium Milestone:
Component: Obfuscation/meek Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Using Meek - Google in TBB 4.0.5 is much slower than normal tor speed received in TBB 4.0.3 with Meek - Google.So I had gone back to 4.0.3 until this is fixed.
I know speed of internet is not a simple problem, but I have tested this again and again, no effect. 4.0.5 meek-google is much slow and unusable while meek-google in 4.0.3 is at normal expected tor speed.
I guess this sounds like bad report without extra info, but if you tell how, I can give more info on it.
I have not tested with TBB 4.0.4.

I posted above as comment in a blog post, but I reposted here to bring it to attention of good meek developers, apology! Thanks.

Child Tickets

Change History (2)

comment:1 Changed 2 years ago by dcf

Try enabling logging in meek-client.

Edit the file Browser/TorBrowser/Data/Tor/torrc-defaults. Change the lines

## meek configuration
ClientTransportPlugin meek exec ./TorBrowser/Tor/PluggableTransports/meek-client-torbrowser -- ./TorBrowser/Tor/PluggableTransports/meek-client


## meek configuration
ClientTransportPlugin meek exec ./TorBrowser/Tor/PluggableTransports/meek-client-torbrowser --log meek-client-torbrowser.txt -- ./TorBrowser/Tor/PluggableTransports/meek-client --log meek-client.txt

Then restart Tor Browser and try browsing. It will create two files, Browser/meek-client.txt and Browser/meek-client-torbrowser.txt. What you might see is some log messages that look like this. If you have many log messages like this, it probably explains the slowness:

status code was 500, not 200; trying again after 30 seconds (9)

Not much changed in meek between 4.0.3 and 4.0.5. I think it was only #14203 and #15428. Perhaps it was only a temporary network problem. The log files will help determine whether that was the case.

comment:2 Changed 22 months ago by dcf

  • Resolution set to user disappeared
  • Status changed from new to closed

I haven't seen any other reports like this. It might have been a transient failure of App Engine or something.

Note: See TracTickets for help on using tickets.