Who knows, maybe one day we will be free of the abrupt persecutions carried out by the big-techs.
OS: openSUSE Tumbleweed x86_64
Kernel: 6.2.8-1-default
FROM: GNOME 44.0
CPU: Intel i3 540 (4) @ 3067GHz
Torbrowser browser is updated to version 12.04 (based on Mozilla Firefox 102.9.Oesr) (64-bit) manually installed
Standard security level.
Whatsapp web link ( https://web.whatsapp.com/ ) does not connect and is completely unstable in the torbrowser, constantly flashing the icon to reload the current page. I tried to change the connection of the tab only and I was not successful.
I also tried to change the NoScript settings on the page, changing the settings from default to temporarily reliable, but even so, the page does not stabilize, making it impossible to connect via QR code reader.
Log:
2023-04-02 20:36:03.417 [NOTICE] New control connection opened from 127.0.0.1.
2023-04-02 20:36:03.417 [NOTICE] New control connection opened from 127.0.0.1.
2023-04-02 20:36:03.418 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2023-04-02 20:37:35.391 [NOTICE] Opening Socks listener on 127.0.0.1:9150
2023-04-02 20:37:35.392 [NOTICE] Opened Socks listener connection (ready) on 127.0.0.1:9150
2023-04-02 20:37:35.737 [NOTICE] Bootstrapped 5% (conn): Connecting to a relay
2023-04-02 20:37:35.999 [NOTICE] Bootstrapped 10% (conn_done): Connected to a relay
2023-04-02 20:37:36.268 [NOTICE] Bootstrapped 14% (handshake): Handshaking with a relay
2023-04-02 20:37:36.830 [NOTICE] Bootstrapped 15% (handshake_done): Handshake with a relay done
2023-04-02 20:37:36.831 [NOTICE] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
2023-04-02 20:37:36.834 [NOTICE] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
2023-04-02 20:37:36.837 [NOTICE] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
2023-04-02 20:37:37.814 [NOTICE] Bootstrapped 100% (done): Done
2023-04-02 20:37:38.036 [NOTICE] New control connection opened from 127.0.0.1.
2023-04-02 21:54:45.186 [NOTICE] New control connection opened from 127.0.0.1.
2023-04-02 21:54:46.097 [NOTICE] New control connection opened from 127.0.0.1.
2023-04-02 21:54:48.510 [NOTICE] New control connection opened from 127.0.0.1.
2023-04-02 22:08:24.474 [NOTICE] New control connection opened from 127.0.0.1.
2023-04-02 22:23:41.997 [NOTICE] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 502 buildtimes.
2023-04-02 22:53:34.269 [NOTICE] New control connection opened from 127.0.0.1.
JavaScript-heavy sites can sometimes experience functional issues in the Tor Browser. The simplest solution is to click on the Security icon (the little gray shield in the upper-right corner of the screen) and click on “Change…” Set your security to “Default”.
I even left it temporarily reliable to see if the page opens and nothing happens. The Qrcode screen does not appear and the page just keeps running, follow the image.
From the moment I started writing this text, capturing the photo, sending it from the phone to the desktop, the official whtasapp page has not stabilized.
Observation: The extensions that I had previously installed were all disabled and removed with the exception of NoScrip and, even so, the website page does not open.
I wouldn’t try to bend the Tor Browser to fit this use case for reasons already explained here:
The same problems appear when using the Brave browser, so the issue is probably the invasive code of the website.
If you really need to access web.whatsapp.com through Tor, I would recommend Tails. It is the easiest and safest method, but also the most resource-intensive and inconvenient. You can also do something similar to what Tails does with your own virtual machine or container, although this approach is more difficult and error-prone.
It seems that you are struggling with many problems using:
Tor (captchas, 403 error messages)
Tor Browser (web applications like Instagram)
The first problem comes with the security settings that website owners choose and there is little you can do about it on your end.
The second is related to the aforementioned incompatibility of limiting browser APIs to avoid fingerprinting and the web applications that expect them, do not fail gracefully when they do not work as expected, and bundle functionality with tracking.
My solution is to not use these web applications. Of course, it is not always possible. So, if I have to use them, I use disposable sessions (similar to what Tails does). If I am forced to use them for a longer period, I dedicate a virtualized system completely for this purpose, or even a physically separated device.
