I've created an issue on the lyrebird repository [1]. Maybe they can help debug this.
So far we know that the browser (client) on OpenBSD isn't working as expected with a bridge, so I wanted to find out what happens when the bridge itself (server) is running on OpenBSD. For this, I used Tor Browser for Android to connect to my own bridges running on -stable (obfs4proxy) and -current (lyrebird). The phone was connected to mobile internet (4G). And both worked just fine, without warnings. So, whatever this is, it only seems to fail when you try to use it with the Tor Browser on OpenBSD (the client side). [1] https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyrebird/-/issues/40032 On Wednesday, January 28th, 2026 at 17:20, Caspar Schutijser <[email protected]> wrote: > > > > > Hi, > > On Mon, Jan 26, 2026 at 10:49:51AM +0000, Douglas Silva wrote: > > > I see that you have already committed this patch, but I just did some > > testing. > > > > Although the built-in obfs4 bridges seem to connect, I'm often getting > > timeouts, especially when loading onion sites. > > > > [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) > > with 85.31.186.98:443 ID=<none> > > RSA_ID=011F2599C0E9B27EE74B353155E244813763C3E5 ("general SOCKS server > > failure") > > > > This is the warning that keeps repeating endlessly on the logs. If I don't > > enable any bridge, the warning is gone and everything loads fast. > > > > Some observations: > > - My PF rules allow all outgoing traffic by default. > > - I use a dual-stack IPv4/IPv6. > > - I don't get any of these warnings when I connect (with an obfs4 bridge) > > from the Android app. > > > > But then I didn't test the older versions, when obfs4proxy was used; so I > > wouldn't know if it's got anything to do with lyrebird. > > > I just did some tests with obfs4proxy; it also happens then. > So it's doesn't look new. I don't immediately have a clue why this > happens, that will need some more digging. > > Caspar
