ebyebots/chrome_fix

This repository addresses a specific internet access problem faced by users in Russia: certain legitimate websites such as GitHub, Discord, and web hosting providers show a connection error (ERR_CONNECTION_CLOSED) even though the sites themselves are not blocking Russian users. The culprit is a technique used by Russia's internet regulator (Roskomnadzor, abbreviated RKN) that identifies browser connections by their TLS fingerprint rather than by the website's IP address. When a browser opens an encrypted (HTTPS) connection, it sends an initial handshake message called a TLS Client Hello. This message has a characteristic pattern, known as JA3 or JA4, that depends on the browser version and its active internal flags. Russia's deep-packet inspection systems detect this pattern and drop the connection before it ever reaches the destination. Changing one browser flag reorders the encryption options inside the Client Hello, producing a fingerprint the blocking system does not recognize, which lets the connection go through. On Windows, the repository provides a one-click .bat script that writes the required setting to the Windows registry. Run it once as Administrator, restart the browser, and previously blocked sites become reachable again without a VPN or proxy. The manual equivalent is to open chrome://flags in any Chromium-based browser (Chrome, Edge, Opera, Yandex Browser), search for "Cryptography Compliance (CNSA)", set it to Enabled, and click Relaunch. A second optional flag, Enable Benchmarking, changes the JA4 fingerprint by a different path and can be tried if the first fix does not work. The README is written in Russian. The fix has been tested on Chrome, Brave, and Opera, and the flag mechanism also applies to Chromium browsers on Linux, macOS, ChromeOS, and Android.