
Registered server transport 'obfs4' at ':44321' When you start up your bridge, you will see something like this in your logfile Registered server transport 'obfs3' at ':41234' obfs4 is backwards compatible with obfs3. You only need to install obfs4 as mentioned in the post above. To ServerTransportPlugin obfs3,obfs4 exec /usr/bin/obfs4proxy If you want to publish as an obfs3 AND obfs4 bridge relay you can change the line ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy Like to add the following These days I do not see a lot of obfs4 traffic yet. Self-testing indicates your ORPort is reachable from the outside. (this may take up to 20 minutes - look for log messages indicating success) Now checking whether ORPort :9001 is reachable. Looks like client functionality is working. You should see something like this: Registered server transport 'obfs4' at ':46396' Step 5: Check the logs and confirm the ORPort is reachable and the obfs4proxy is working. Step 4: Restart Tor $ sudo service tor restart


ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy Step 3: Edit your torrc config file, usually located at /etc/tor/torrc #Bridge config Step 2: Install obfs4proxy: $ sudo apt-get update & sudo apt-get install obfs4proxy Note: you can skip this step if you're running Debian stable (jessie) or more recent. Step 1: Edit your sources.list to add obfs4proxy repository: Step 0: Follow this guide to setup the official package repository, and install Tor. You can use this scanning tool to make sure that your obfs4 port is publicly reachable. Tor automatically tests its OR port but it currently (as of August 2019) does not test its obfs4 port. Don't forget to make sure that your OR port and your obfs4 port must be publicly reachable.

It has instructions on how to set up an obfs4 bridge for several platforms, including Debian and Ubuntu. The Tor Project's official guide is available here.
