Skip to content

Some Samsung users receiving "proxy refused" error when visiting websites

We we got two reports from Samsung users encountering problems while using TBA. I will describe incidents, and will add to this topic when there is more information.

  1. Samsung A047F/Android 13 The logs show tor successfully bootstrapped:
---------------Initializing Tor Log---------------
[NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
[NOTICE] Opening Socks listener on /data/user/0/org.torproject.torbrowser/cache/tor-private/socks-ipc
[NOTICE] Opened Socks listener connection (ready) on /data/user/0/org.torproject.torbrowser/cache/tor-private/socks-ipc
[NOTICE] Bootstrapped 5% (conn): Connecting to a relay
[NOTICE] Bootstrapped 10% (conn_done): Connected to a relay
[NOTICE] Bootstrapped 14% (handshake): Handshaking with a relay
[NOTICE] Bootstrapped 15% (handshake_done): Handshake with a relay done
[NOTICE] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
[NOTICE] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
[NOTICE] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
[NOTICE] Bootstrapped 100% (done): Done

However, when the user tries to open any website (directly in TB, to by opening links from another app) they get "Proxy server refuses connection" error.

  1. Samsung Galaxy A03 This time logs use like this (full log)
[NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
[NOTICE] Switching to guard context "bridges" (was using "default")
[NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
[NOTICE] Opening Socks listener on /data/user/0/org.torproject.torbrowser/cache/tor-private/socks-ipc
[NOTICE] Opened Socks listener connection (ready) on /data/user/0/org.torproject.torbrowser/cache/tor-private/socks-ipc
[NOTICE] Bootstrapped 1% (conn_pt): Connecting to pluggable transport
[NOTICE] Bootstrapped 2% (conn_done_pt): Connected to pluggable transport

After that the bootstrapping process stops.

We asked users to install TBA Alpha and check - they still cannot connect to Tor. It case 2 logs look like this:

[NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
[NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
[NOTICE] Opening Socks listener on /data/user/0/org.torproject.torbrowser_alpha/cache/tor-private/socks-ipc
[NOTICE] Opened Socks listener connection (ready) on /data/user/0/org.torproject.torbrowser_alpha/cache/tor-private/socks-ipc
[NOTICE] Bootstrapped 5% (conn): Connecting to a relay
[NOTICE] Closing no-longer-configured Socks listener on ???:0
[NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
[NOTICE] Delaying directory fetches: DisableNetwork is set.

Users are from different counties, second one uses bridges to connect.

Also from google play reviews:

I've been having a "proxy refused connection" issue and I don't know what is causing it

Latest update, keeps crashing on Galaxy s23.