Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Tor Browser
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,004
    • Issues 1,004
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • Tor Browser
  • Issues
  • #40804
Closed
Open
Created Feb 11, 2022 by atari@atari

Tor Browser's new obfs4proxy client has compatibility issues with old obfs4proxy bridges

Summary

When starting TB 11.0.6 on Linux with self-defined bridges at bootstrapping following messages show up in log multiple times:

[WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with [omitted] ID=[omitted] RSA_ID=[omitted] (“general SOCKS server failure”)

Bridges work after bootstrapping. Warnings irritate anyhow.

Steps to reproduce:

Set some bridge-lines in TB config and restart the browser

What is the current bug behavior?

Tor Logs show these warnings multiple times:

[WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with [omitted] ID=[omitted] RSA_ID=[omitted] (“general SOCKS server failure”)

What is the expected behavior?

No warning like in the builds before

Environment

Tor Browser 11.0.6 downloaded via auto-update | Linux Debian Started with ~/tor-browser_en-US/Browser/start-tor-browser

Relevant logs and/or screenshots

Multiple times: [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with [omitted] ID=[omitted] RSA_ID=[omitted] (“general SOCKS server failure”)

Edited Feb 24, 2022 by Roger Dingledine
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking