Bridge reported bandwidth plumeted

Did my somewhat-weekly checkin on my bridge and was surprised to see the stats had plummeted.

Logged into the server and noticed Tor wasn’t using its usual resources so restarted it, which happened cleanly. I haven’t modified my torrc since September 23rd, 2023.

User tor
PIDFile /run/tor/
Log notice syslog
DataDirectory /var/lib/tor/data

ExitRelay 0
RunAsDaemon 1
BridgeRelay 1
ControlPort 9051
CookieAuthentication 1
ORPort IPv4Only
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
ServerTransportListenAddr obfs4 IPV4Only iat_mode=2
ExtORPort auto
<Address line present but removed>
Nickname SpinnerDolphinBr2
BandwidthRate 256 MBits
RelayBandwidthRate 256 MBits
BandwidthBurst 512 MBits
RelayBandwidthBurst 512 MBits
MaxAdvertisedBandwidth 384 MBits
ContactInfo Random Person <thoughts AT carpenter DASH farms DOT us>
TruncateLogFile 1

Any thoughts on what might have happened or suggestions for a better torrc? Kills me to see my Advertised Bandwidth in the KiB/s from the 100s of MiB/s it once was.

1 Like

on metrics.tpo I see:

Transport protocols: none

but you seem to have configured an obfs4 PT, if everything was working properly, it should show obfs4 instead of none. Did you maybe do an upgrade or something and obfs4 isn’t working properly anymore?

1 Like

Your… right! I did some system maintenance around the time the problem started. I went and checked and /usr/bin/obfs4proxy was missing. Apparently, at least in my Gentoo based world, the functionality of obfs4proxy is now being provided by a package called “lyrebird”. In any case, I created a symbolic link and restarted tor for good measure.

Hopefully the issue is now resolved.

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.