A little more technically advanced people familiar with the Puppet configuration management engine might appreciate this Puppet code snippet that will deploy a bridge on port 443 for you:
Awesome, sent the email. Looks like I am too new to send DMs right now.
One note, I installed via Docker. And on the docker install page (Tor Project | Docker) for step 3, it talks about a command to get the bridge line:
docker exec CONTAINER_ID get-bridge-line
Unfortunately, when I ran that I get the following:
user@dockerhost:~$ docker exec torbridge_obfs4-bridge_1 get-bridge-line
Could not create bridge line. Tor's log format may have changed. This is a bug.
I ended up just grabbing the file you suggested, but wanted to give the heads up that it looks like the docs might need an update.
Ok was planning on deploying five nodes, but I really need two shirts AND a hoodie (AND stickers). So later today I will up my setup from six working bridges now to ten later on.
Hi! I’m new on this forum. Been running tor relays on and off for twenty years now I think
Got some shirts years ago, this time I really want a hoodie…
When I get 10 bridges up (added 4 so far) I’ll share the ‘Bridge obfs4’ lines with Gus, as I understand is a way to be eligible.
Hi all! I just had troubles (ip blacklisted) running my relay, so I decided to run a bridge. This campaign is just perfect for me!
Some questions: I set up the torrc as shown in the instruction but I have a doubt, should also DirPort be set-up on torrc and opened on firewall?
My hashed fingerprint url is
as shown in the tor log, but at the moment it is not showing up anything (“no resources for the given id” message) and the tor log states:
Your server has not managed to confirm reachability for its
│ ORPort(s) at :443. Relays do not publish descriptors until
│ their ORPort and DirPort are reachable. Please check your firewalls, ports,
│ address, /etc/hosts file, etc.
So I ask you if you can confirm DirPort must be set up too.
When everything is working sould I post there the metrics url and send an email with full line to frontdesk@torproject.org to partecipate am I right?
Thanks a lot!
Brian
No, you need to open your ORPort and you will see message saying that the port is reachable in your Tor logs. After ~3 hours you will be able to find your bridge on Metrics portal.
Hi @gus thanks a lot for the fast answer!
I am running on raspbian (Debian Stretch) but I cannot find the file obfs4_bridgeline.txt in the entire filesystem. Any help?
Bridge 33ADB77CD707E0EDF1711DBE7BEC63C6C876E480 advertises:
* obfs4: functional
Last tested: 2021-11-21 12:37:49.893505938 +0000 UTC (18m2.992117131s ago)
But no file /var/lib/tor/pt_state/obfs4_bridgeline.txt is present, command find / -name obfs* has no useful result (finds binary and docs but no bridgeline). I installed tor from sources (latest version, 0.4.6.8), don’t know if this can help… any suggestion?
Thank you!
If you try that Tor will complain in the logs and ignore the Dirport setting. It is mutual exclusive apparently. Maybe to prevent bridges to be identified as such too easily?
I really like hoodies!
if Tor will get support for IPv6 only, i can create a second bridge (or relay / exit node…)
would love to create 10 more bridges but currently i don’t have the resources…
for now i going to keep this one running and hope i don’t lose the keys…