Systemic network bug (net_error -200) in Chrome/Edge Flatpak breaks WhatsApp Web, Canva, and Facebook

Hello, Endless OS community!

I am experiencing a severe and persistent issue when using Chromium-based browsers (Google Chrome and Microsoft Edge) installed via Flatpak on my system. Initially, the issue seemed restricted to WhatsApp Web (where the QR Code stays in an infinite loading loop and phone number login also fails), but I have noticed that the failure is systemic and is breaking multiple productivity tools and social media platforms.

Observed symptoms:

  1. WhatsApp Web: QR Code stuck in an endless loading loop and refusal to validate sessions.

  2. Canva: Inability to save design progress or export files. The website displays saving errors and freezes when trying to process downloads.

  3. Facebook: Constant failures when trying to create or save posts (posts and photos disappear or get stuck loading indefinitely).

When running the affected browsers via terminal to inspect network behavior, I noticed that the Chromium engine fails to perform the security handshake (SSL handshake) with the servers of these platforms. Here is the error log generated in the terminal:

bash

[80:94:0811/194434.343626:ERROR:net/socket/ssl_client_socket_impl.cc:978] handshake failed; returned -1, SSL error code 1, net_error -200
[80:94:0811/194434.343813:ERROR:net/socket/ssl_client_socket_impl.cc:978] handshake failed; returned -1, SSL error code 1, net_error -200

Use o código com cuidado.

Important context about the scenario:

  • Problem isolation: On Mozilla Firefox, absolutely everything works perfectly (WhatsApp Web, Canva, and Facebook). This proves that the issue is not with my internet connection or the websites themselves, but rather with the Chromium engine running inside the Flatpak sandbox on Endless OS.

  • Troubleshooting attempts made without success: Disabling hardware acceleration (--disable-gpu), deep cleaning the cache in Flatpak folders (~/.var/app/), using incognito mode, and disabling extensions. I also tried to adjust /etc/resolv.conf, but the immutable nature of the OS prevents direct manual changes (Operation not permitted).

Everything points to a communication breakdown or a lack of permission for Chromium applications in Flatpak to access and properly validate the security certificates and cryptographic keys from the operating system (which are essential for WebSockets and secure asynchronous HTTP requests).

Does anyone from the development team or the community know if there is a pending runtime update or a planned fix to resolve this failure within the Chromium ecosystem on Endless OS?

Thank you in advance for the support!

Please make sure the flatpak Chrome comes from Flathub. Endless OS had provided home built Chrome flatpak, but discontinued and moved to Flathub.

This means the flatpak Chrome comes from Flathub:

$ flatpak info com.google.Chrome -o
flathub

If updating Chrome does not solve the problem, then I suggest that report this issue to upstream source Issues · flathub/com.google.Chrome · GitHub

The flatpak Edge’ issue can be reported to Issues · flathub/com.microsoft.Edge · GitHub

As atualizações dos navegadores não estão resolvendo o problema! Obrigado pelo retorno.