On Tue, Sep 30, 2025 at 01:25:27PM -0500, Eritque arcus via tor-relays wrote:
I don't know why but my bridge relay marked as down but I can connect to it with my Tor browser.[...]
the status is right here: <https://bridges.torproject.org/status?id=A69AD85C2E175BD0F753E1CCBE5D4BA371149685> and <https://metrics.torproject.org/rs.html#details/A69AD85C2E175BD0F753E1CCBE5D4BA371149685>.
For me the bridge status page says "Bridge A69AD85C2E175BD0F753E1CCBE5D4BA371149685 advertises: * obfs4 IPv6: dysfunctional Error: timed out waiting for bridge descriptor Last tested: 2025-10-01 15:12:26.831787229 +0000 UTC (1h58m7.473805368s ago) * obfs4 IPv4: dysfunctional Error: timed out waiting for bridge descriptor Last tested: 2025-10-01 15:12:26.831787229 +0000 UTC (1h58m7.473813933s ago)"
Do I need to allow some extra ports? right now I only accept the ORPort and block any others.
Yes: you are running an obfs4 bridge, so you need to allow incoming connections to your obfs4 port too. (In the future we would like to make it easier for you to firewall connections to your ORPort, since clients don't normally use it directly, but we're not quite there yet. There are some hacky workarounds, but for simplicity you should keep allowing connections to your ORPort too, so your bridge will pass its self-reachability tests.) Thanks for running a bridge! --Roger