[tor-relays] Webtunnel type bridge Tor Metrics

[Dionysios K.]

Hey Hiro,

The issue was solved for a few hours, it was the first time since I switched to webtunnel I saw my bridge online, but now it's again marked as offline.

It's the same issue again.

----------------------------------------

Apr 24, 2024 8:02:02 PM Hiro <hiro at torproject.org>:

> 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:
>> Hey,
>> 
>> On 4/20/24 17:40, Dionysios K. via tor-relays wrote:
>>> 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.
>> 
>> 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
>> 
>> 
>>> 
>>> _______________________________________________
>>> tor-relays mailing list
>>> tor-relays at lists.torproject.org
>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>> _______________________________________________
>> tor-relays mailing list
>> tor-relays at lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays