Webtunnel type bridge Tor Metrics
Hello everyone, I recently switched from using obfs4 to Webtunnel from my bridge. Since the configuration change, the metrics website shows it as offline. The downtime displayed on the website is also odd as it shows a random time each time I visit, such as "1 hour 14 minutes and 10 seconds" or "2 hours 23 minutes and 30 seconds." However, the bridge is online. I am wondering if this is the correct behavior for the Webtunnel protocol.
Hey, On 4/20/24 17:40, Dionysios K. via tor-relays wrote:
The way the metrics website "decides" if a bridge is online is based on both the results of tests from the bridge authority and bridgestrap. If the bridge is working and receiving traffic, the reason why I can think it is marked as offline is that some of those tests is failing or we are failing to process the data correctly. It could also be that something is a bit off with the bridge configuration since you changed from obfs4 to webtunnel. You could start your investigation by looking at the logs on the machine, then you could check what the bridgestrap stats say about your bridge (https://collector.torproject.org/recent/bridgestrap/) and finally check the latest status (https://collector.torproject.org/recent/bridge-descriptors/statuses/). Let me know if this helps you. I could also check the bridge myself, you could open an issue on gitlab under the relay-search project (https://gitlab.torproject.org/tpo/network-health/metrics/relay-search), or you can send me a private message (email or irc) with the hashed fingerprint and logs. Cheers, -hiro
Dionysios, all, This was an issue with rdsys and documents that weren't being synced to the vm where collector.torproject.org lives. For details: https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/199 It should be solved now. Talk soon, -hiro On 4/22/24 22:13, Hiro wrote:
Maybe not directly related, but I've seen the same. The webtunnel bridge shows as functional on the bridges website and offline on the metrics website. It's been that way since I started running a webtunnel bridge last year. Could it be related to these settings? AssumeReachable 1 ORPort 127.0.0.1:auto On Wed, Apr 24, 2024 at 10:01 AM Hiro <hiro@torproject.org> wrote:
On 24.04.24 19:31, tor-home at encryptfirst.com wrote:
Yes that's the reason. There is an issue that this should be documented https://gitlab.torproject.org/tpo/web/community/-/issues/329
Hey, On 4/25/24 09:02, Bauruine wrote:
The bridgestrap test was not completely fixed it seems: https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/199#note_30... Cheers, -hiro
participants (4)
-
Bauruine -
Dionysios K. -
Hiro -
tor-home at encryptfirst.com