meek Survival Guide

Did meek-azure or moat break? Are you feeling panicky and frustrated? You have come to the right place. Here's how you can diagnose the issue:

1. Test if you can reach our meek server (which runs on polyanthum) through the Azure infrastructure:

   $ wget -q -O - https://ajax.aspnetcdn.com/ --header 'Host: meek.azureedge.net'              
   I’m just a happy little web server.

   If you don't see this message, the problem is likely somewhere in Azure.

2. Take a look at our Azure CDN configuration in portal.azure.com.

3. Our meek bridge's client numbers can tell you if clients can reach our bridge.

4. Use an up-to-date version of obfs4proxy to test meek-azure and moat. Note that whatever Debian stable currently ships is likely to be outdated. Consider starting obfs4proxy with the following flags:

   ClientTransportPlugin meek_lite,obfs2,obfs3,obfs4,scramblesuit exec /path/to/obfs4proxy -enableLogging -unsafeLogging -logLevel DEBUG

   You can then find obfs4proxy's log file in TOR_DATADIR/pt_state/obfs4proxy.log