📱
blog.cat.ssl

SSL errors on old Android devices: causes and what you can do

19.11.2026
← All articles

Site owners regularly hear "the site won't open on my phone, it says security error". You test on a computer, a new iPhone and a few current Android phones, and everything works. The problem only appears on Android devices that are several years old, especially budget phones and tablets that no longer receive updates. This is not random: several parts of HTTPS trust are outdated on these devices, and they clash with modern certificates.

Root certificates: who the device trusts

Every operating system ships a list of trusted root certificates. The browser walks the chain from the site certificate through the intermediate to the root, and if that root is not in the device's list, the certificate is rejected no matter how correctly it was issued. On Android this list is mostly updated through system updates, so it freezes when the manufacturer stops supporting the device. Let's Encrypt now relies on its own ISRG Root X1, and according to Let's Encrypt documentation, Android versions before 7.1.1 do not include it. A cross-signed chain used to keep older devices working, but it has been phased out, so very old Android devices may fail on Let's Encrypt sites. Check Let's Encrypt's official documentation for current details.

Other causes: TLS, SNI and the clock

Modern servers disable TLS 1.0 and 1.1 and accept only TLS 1.2 and 1.3. Some apps and built-in browsers on very old Android versions do not enable TLS 1.2 by default, so the error reads like "connection failed" or "protocol error" rather than a certificate problem. Ancient browsers may also lack SNI, which shared hosting needs to pick the right certificate, leading to a name mismatch. And old phones often have a wrong date after a full battery drain, so ask the user to check the date first.

Example: couriers with old phones

A Tashkent delivery service built a web app for couriers at kuryer.misol.uz. Office testing went fine, but on launch day several couriers could not log in. All had Android phones that stopped receiving updates years ago, and their built-in browser did not trust the certificate chain. The company installed Firefox on those phones, since Firefox on Android uses its own root store that updates with the browser, and planned a gradual phone replacement. Nothing had to be weakened on the server.

What to check on the server

First make sure the server sends the full chain. Modern browsers often fill in a missing intermediate; old devices do not.

openssl s_client -connect example.uz:443 -servername example.uz -showcerts </dev/null

You should see several BEGIN CERTIFICATE blocks with s: and i: lines. Only one means the chain is incomplete. Then check protocol support:

openssl s_client -connect example.uz:443 -servername example.uz -tls1_2 </dev/null
openssl s_client -connect example.uz:443 -servername example.uz -tls1_3 </dev/null

Re-enabling TLS 1.0 for a handful of old devices is not recommended, because it lowers security for everyone.

What to tell visitors

Know your audience

For most sites, old Android users are a small share. But if your customers or staff mostly use old devices, such as regional distributors or warehouse tablets, plan for it. Analytics or User-Agent data in server logs shows which Android versions visit. The free Let's Encrypt certificate on sayt.uz hosting works on all modern devices; for a specific problem with old ones, open a support ticket from the sayt.uz cabinet with the device model and Android version.

Related articles

🌐 One SSL certificate for both www and non-www: setting it up correctly 🔍 Checking an SSL certificate with OpenSSL: the commands you actually need ⚛️ Post-Quantum Encryption (ML-KEM): What Is Changing in TLS 🧭 Hundreds of domains on one server: how SNI keeps SSL from mixing up
🌐 Language
🇺🇿 O'zbek 🇺🇿 Ўзбек 🇷🇺 Русский 🇬🇧 English ✓