X.com (formerly Twitter) issues with Tor Browser

Serial.com · March 12, 2025, 5:00pm

Hey guys

Can you help me with the question below?

When reporting a bug, please include as many of these as possible:

Operating system you are using
openSuse TW
Tor Browser Version
14.0.7 (based on Mozilla Firefox 128.8.0esr)
Tor Browser Security Level
Standard
Step-by-step guide on how you got to the issue so we can reproduce it (e.g. I opened the browser, typed in a URL, clicked the (i) icon and my browser crashed)

After logging into X.com, the New Tor circuit for this Site (X.com) looks like an airport windsock. It changes every second, causing instability in browsing. Is this normal?

If the website’s own page is opened in a new tab, a new circuit for the website in question appears. Shouldn’t the circuit remain the same, once it is in a stable state?

(optional) A screenshot of the problem

The Tor Registry

2025-03-12 13:29:43.699 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2025-03-12 13:29:44.240 [NOTICE] Opening Socks listener on 127.0.0.1:9150
2025-03-12 13:29:44.240 [NOTICE] Opened Socks listener connection (ready) on 127.0.0.1:9150
2025-03-12 13:29:46.080 [NOTICE] Bootstrapped 1% (conn_pt): Connecting to pluggable transport
2025-03-12 13:29:46.082 [NOTICE] Bootstrapped 2% (conn_done_pt): Connected to pluggable transport
2025-03-12 13:29:46.339 [NOTICE] Bootstrapped 10% (conn_done): Connected to a relay
2025-03-12 13:29:46.799 [NOTICE] Bootstrapped 14% (handshake): Handshaking with a relay
2025-03-12 13:29:47.008 [NOTICE] Bootstrapped 15% (handshake_done): Handshake with a relay done
2025-03-12 13:29:47.009 [NOTICE] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
2025-03-12 13:29:47.197 [NOTICE] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
2025-03-12 13:29:47.892 [NOTICE] new bridge descriptor 'PraxedisGuerrero' (fresh): $5EDAC3B810E12B01F6FD8050D2FD3E277B289A08~PraxedisGuerrero [qSueJICMYZBsv2+lFaemfzHkPZxDER2ZDeQdiLDMIDY] at ip:port
2025-03-12 13:29:48.206 [NOTICE] Bootstrapped 100% (done): Done
2025-03-12 13:30:54.563 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with ip:port ID=<none> RSA_ID=CDF2E852BF539B82BD10E27E9115A31734E378C2 ("general SOCKS server failure")
2025-03-12 13:31:31.428 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with ip:port ID=<none> RSA_ID=CDF2E852BF539B82BD10E27E9115A31734E378C2 ("general SOCKS server failure")
2025-03-12 13:35:15.632 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with ip:port ID=<none> RSA_ID=CDF2E852BF539B82BD10E27E9115A31734E378C2 ("general SOCKS server failure")
2025-03-12 13:37:12.418 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with ip:port ID=<none> RSA_ID=CDF2E852BF539B82BD10E27E9115A31734E378C2 ("general SOCKS server failure")
2025-03-12 13:51:05.905 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with ip:port ID=<none> RSA_ID=CDF2E852BF539B82BD10E27E9115A31734E378C2 ("general SOCKS server failure")
2025-03-12 13:56:58.161 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with ip:port ID=<none> RSA_ID=CDF2E852BF539B82BD10E27E9115A31734E378C2 ("general SOCKS server failure")
2025-03-12 14:05:54.737 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with ip:port ID=<none> RSA_ID=CDF2E852BF539B82BD10E27E9115A31734E378C2 ("general SOCKS server failure")
2025-03-12 14:06:38.947 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with ip:port ID=<none> RSA_ID=CDF2E852BF539B82BD10E27E9115A31734E378C2 ("general SOCKS server failure")
2025-03-12 14:17:10.576 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with ip:port ID=<none> RSA_ID=CDF2E852BF539B82BD10E27E9115A31734E378C2 ("general SOCKS server failure")
2025-03-12 14:18:59.332 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with ip:port ID=<none> RSA_ID=CDF2E852BF539B82BD10E27E9115A31734E378C2 ("general SOCKS server failure")
2025-03-12 14:30:49.777 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with ip:port ID=<none> RSA_ID=CDF2E852BF539B82BD10E27E9115A31734E378C2 ("general SOCKS server failure")
2025-03-12 14:57:08.038 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with ip:port ID=<none> RSA_ID=CDF2E852BF539B82BD10E27E9115A31734E378C2 ("general SOCKS server failure")
2025-03-12 15:16:53.990 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with ip:port ID=<none> RSA_ID=CDF2E852BF539B82BD10E27E9115A31734E378C2 ("general SOCKS server failure")
2025-03-12 15:58:53.617 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with ip:port ID=<none> RSA_ID=CDF2E852BF539B82BD10E27E9115A31734E378C2 ("general SOCKS server failure")

MrWhike7 · March 13, 2025, 3:44pm

So basically for the past two days, i can’t log in to Twitter. Whenever i try to do it, it just gives me an error that something is wrong and stuff. Is Twitter no longer accessible via Tor or is it just my problem? Because someone named Serial.com made a post here about X(Twitter) 20 hours ago and seems they still can log in and don’t have any issues.
So if anyone help or just simply answer, i will be much appreciated.

Serial.com · March 14, 2025, 3:28pm

Hello

I haven’t figured out what’s going on yet, but there is a connection as tested, but it says it can’t connect to X.

Look:

Serial.com · March 14, 2025, 8:52pm

Hey guys

I tested the X.com login in all other browsers and it works normally.
It just doesn’t work in TorBrowser.

Everything suggests that there is something affecting the connection between the browser and the X server.

Maybe an X boycott of the TorBrowser browser?
Or TorBrowser restrictions on X site?

What do you say?

fw114 · March 17, 2025, 5:17pm

Since the latest attack on x it’s not possible to login with a Tor Browser.

What could be done here ?

MrWhike7 · March 17, 2025, 7:54pm

Okay, so it is not only just my problem.

BobbyB · March 19, 2025, 6:46am

OK, I don’t have a twitter account but got a login screen. Tried 3 times. Always came up. This capture is from a FR exit node. Maybe you get an IP with a bad rep or on an abuse report

Serial.com · March 19, 2025, 12:59pm

Regardless of which circuit or bridge is used, the login cannot be performed, but the server does not show what kind of error occurs.

The situation has been the same for almost a week.

When we are lucky, the captcha for the X game appears, but even though it is performed, the connection fails miserably.

fw114 · March 20, 2025, 5:59pm

Yeah, you always get the login page.
after that and enter username / passwort
u’ll get Error
rewgardless what bridge is in use.

I guess they banned all tor exit nodes for login after the last attack.

Serial.com · March 21, 2025, 11:34am

Hello

I believe it’s something different, as I used Tor Browser a little while ago on Windows 10, and it worked, despite the delay.

Using Tor Browser on openSUSE, the error is constant.

I checked the Tor Browser connection speed and the ping is very slow, and the relays are changing almost instantly. I believe this is one of the reasons.

Serial.com · March 23, 2025, 3:27am

Hey guys

After several complaints, X appears to have restarted, logging in using the Tor Browser.

There are still those silly captcha requirements, kind of time consuming, but it’s working.