Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #24432
Closed (moved) (moved)
Open
Issue created Nov 27, 2017 by Isis Lovecruft@isis

The meek<->moat tunneling isn't set up correctly

The apache config has:

ProxyPass /meek/ http://127.0.0.1:2000/                                                                                                                                                                                       
ProxyPass /moat/ http://127.0.0.1:3881/moat/                                                                                                                                                                                  
ProxyPass / http://127.0.0.1:3880/ retry=10                                                                                                                                                                                 
ProxyPassReverse / http://127.0.0.1:3880/                                                                                                                                                                                     

(BridgeDB's HTTPS distributor is a Python process listening on port 3880, and the moat distributor is listening on 3881.)

The moat-server is run with the following:

∃!isisⒶwintermute:(master $>)~/code/torproject/bridgedb-admin ∴ cat bin/run-meek                                                                                                                                                                                                 
#!/usr/bin/env bash                                                                                                                                                                                                           
                                                                                                                                                                                                                              
export TOR_PT_MANAGED_TRANSPORT_VER=1                                                                                                                                                                                       
export TOR_PT_SERVER_BINDADDR=meek-0.0.0.0:2000                                                                                                                                                                             
#export TOR_PT_SERVER_BINDADDR=meek-78.47.38.229:2000                                                                                                                                                                       
export TOR_PT_SERVER_TRANSPORTS=meek                                                                                                                                                                                        
export TOR_PT_ORPORT=127.0.0.1:443
                                                                                                                                                                                                                              
/srv/bridges.torproject.org/bin/meek-server --disable-tls & disown

The moat distributor has two pages, /moat/fetch and /moat/check. In my Tor Browser, if I go to https://4-dot-tor-bridges-hyphae-channel.appspot.com/meek/moat/fetch I get a "301 Permanent Redirect" from the Apache server telling me to go to https://bridges.torproject.org/meek/meek/moat/fetch.

Probably I've just configured all the URIs wrong?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking