Opened 5 weeks ago

Last modified 2 weeks ago

#29871 needs_information defect

Meek-Azure Pluggable Transport Not working

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

Description

Meek-Azure pluggable transport is not working. Results in error- Establishing an encrypted directory connection failed. The problem has been replicated across several devices and several separate implementations of Tor across several ISPs within the Untied States. Tor log file has been attached to this ticket.

Child Tickets

Attachments (1)

tor_log.txt (1.5 KB) - added by bakertaylor28 5 weeks ago.
Tor Log File

Download all attachments as: .zip

Change History (7)

Changed 5 weeks ago by bakertaylor28

Attachment: tor_log.txt added

Tor Log File

comment:1 Changed 5 weeks ago by cypherpunks

Keywords: Tor Pluggable Transport Bridge bridge down Meek meek Azure azure removed
Version: Tor: unspecified

comment:2 Changed 4 weeks ago by gk

Component: Applications/Tor BrowserObfuscation/meek
Owner: changed from tbb-team to dcf

Interesting. That#s not a Tor Browser issue, though, as I can get it to work in my environment.

comment:3 Changed 3 weeks ago by dcf

Severity: CriticalNormal
Status: newneeds_information

It looks like it is still working for most people:
https://metrics.torproject.org/userstats-bridge-transport.html?start=2019-01-02&end=2019-04-02&transport=meek

Did it work for you before, and only stop working recently? Or did it never work for you? How far back did you try?

I suspect there is a problem with your local Tor Browser installation. Try downloading a fresh copy of Tor Browser and see if that one works. https://www.torproject.org/download/

comment:4 Changed 2 weeks ago by bakertaylor28

It has worked previously, and I managed to get it to work inside an oracle VM based on Ubuntu14 (Where the problem originally surfaced on the Windows 10 Platform) and was able to replicate the problem by turning off the VM's virtual network card and then attempting to launch Torbrowser with extremely similar log errors. So whatever is going on would have to do with some stunt that Microsoft is pulling on the azure platform.

Last edited 2 weeks ago by bakertaylor28 (previous) (diff)

comment:5 Changed 2 weeks ago by bakertaylor28

Status: needs_informationnew

comment:6 in reply to:  4 Changed 2 weeks ago by dcf

Status: newneeds_information

Replying to bakertaylor28:

It has worked previously, and I managed to get it to work inside an oracle VM based on Ubuntu14 (Where the problem originally surfaced on the Windows 10 Platform) and was able to replicate the problem by turning off the VM's virtual network card and then attempting to launch Torbrowser with extremely similar log errors. So whatever is going on would have to do with some stunt that Microsoft is pulling on the azure platform.

Thanks for doing this test. I don't understand the conclusion that it has something to do with the Azure CDN side--the fact that it works in an Ubuntu VM but not in your Windows 10 rather indicates that it is a problem with your Windows 10. You say you've experienced the problem on several devices, versions of tor, and ISPs--can you be more specific? Were these all computers of yours, all running Windows 10? What were the multiple versions of tor, can you give version numbers or dates? Did you try downloading a new copy of Tor Browser and installing it in a separate folder? Does the obfs4 transport work for you? What about running with no pluggable transport?

Note: See TracTickets for help on using tickets.