A small diagnostics release: when bridges are reachable but the transport still can't connect, the log now points at the likely cause.
Fixed
- Clearer log when the transport can't reach reachable bridges. If a bridged connect fails after the reachability scan found bridges reachable but the transport could not connect to any of them, the log now names the likely cause: a firewall or security tool blocking OnionHop's transport helper (lyrebird / webtunnel-client), or bridges that are dead at the protocol layer. Previously this appeared only as an unexplained wall of "general SOCKS server failure" (#74).
Downloads
| Platform | File |
|---|---|
| Windows installer | OnionHop-Setup-v3.exe |
| Windows portable | OnionHopV3-Portable-3.7.3-win-x64.zip |
| Windows CLI | OnionHop-CLI-Setup-3.7.3.exe / OnionHopCLI-Portable-3.7.3-win-x64.zip |
| Linux | OnionHop-x86_64.AppImage |
| Linux CLI | OnionHopCLI-3.7.3-linux-x64.tar.gz |
| macOS (Apple Silicon) | OnionHop-3.7.3-macOS-arm64.dmg |
| macOS (Intel) | OnionHop-3.7.3-macOS-x64.dmg |
| macOS CLI (Apple Silicon) | OnionHopCLI-3.7.3-macos-arm64.tar.gz |
| macOS CLI (Intel) | OnionHopCLI-3.7.3-macos-x64.tar.gz |
SOCIAL SHARE CARD GENERATOR