This one is sneaky. You install a new certificate, open the site in desktop Chrome, see the padlock and move on. Days later customers report that phones flag the site as unsafe, the mobile app cannot connect or payment notifications stopped arriving. SSL checkers say "Chain issues: Incomplete" or "Extra download". The cause is the same every time: the server is not sending the intermediate certificate.
How the chain works
CAs do not sign site certificates with their root key; the root is kept offline and signs intermediates, and an intermediate signs your certificate. Roots are preinstalled in operating systems and browsers, intermediates are not, so the server must send them. Without the intermediate, the client cannot link your certificate to a trusted root, even though the certificate itself is perfectly valid.
Why only some devices fail
Desktop browsers often hide the problem by fetching the intermediate from the certificate's AIA field or reusing one cached from other sites. curl, Python, PHP, Java and mobile apps usually rely only on what the server sends. That is why server-to-server traffic breaks first: a Tashkent online flower shop may stop receiving payment confirmations because the payment provider cannot verify the shop's certificate, leaving paid orders marked unpaid.
Detecting it
A correct server sends at least two certificates, 0 s: for your site and 1 s: for the intermediate. Only certificate 0 plus return code 20 or 21 means the chain is incomplete. curl shows the same thing.
echo | openssl s_client -connect example.uz:443 -servername example.uz -showcerts 2>/dev/null \
| grep -E '^ *[0-9] s:|i:|Verify return code'
# When the chain is incomplete:
# 0 s:CN = example.uz
# i:C = US, O = Let's Encrypt, CN = R11
# Verify return code: 21 (unable to verify the first certificate)
curl -sS -o /dev/null https://example.uz/
# curl: (60) SSL certificate problem: unable to get local issuer certificate
Building the full chain file
Concatenate your certificate first, then the intermediates. Leave the root out; clients already have it. Check the count and the signature, and if two certificates end up glued together on one line, add a newline between them.
cat example.uz.crt intermediate.crt > fullchain.crt
grep -c 'BEGIN CERTIFICATE' fullchain.crt
openssl verify -untrusted intermediate.crt example.uz.crt
Nginx
Nginx has no separate chain directive: the file in ssl_certificate must contain both the site certificate and the intermediates. Pointing it at the site certificate alone is the most common mistake.
server {
listen 443 ssl;
server_name example.uz www.example.uz;
ssl_certificate /etc/ssl/example.uz/fullchain.crt;
ssl_certificate_key /etc/ssl/example.uz/private.key;
}
sudo nginx -t && sudo systemctl reload nginx
Apache
Since Apache 2.4.8, put the full chain in SSLCertificateFile. Older versions use SSLCertificateChainFile, which still works but is deprecated.
# Apache 2.4.8 and newer
SSLCertificateFile /etc/ssl/example.uz/fullchain.crt
SSLCertificateKeyFile /etc/ssl/example.uz/private.key
# Older Apache versions
SSLCertificateFile /etc/ssl/example.uz/example.uz.crt
SSLCertificateChainFile /etc/ssl/example.uz/intermediate.crt
Certbot files
Hand-configured servers often point at cert.pem, which is exactly the incomplete chain. Always use fullchain.pem.
# Certbot files
/etc/letsencrypt/live/example.uz/cert.pem # site certificate only
/etc/letsencrypt/live/example.uz/chain.pem # intermediate only
/etc/letsencrypt/live/example.uz/fullchain.pem # the right choice
/etc/letsencrypt/live/example.uz/privkey.pem # private key
Hosting panels
On sayt.uz hosting, Let's Encrypt certificates issued through the panel include the chain automatically. When you upload a commercial certificate by hand, paste the intermediate or CA bundle into the chain field instead of leaving it empty, then confirm return code 0 with OpenSSL.
After the fix
Re-test with curl or OpenSSL rather than your own browser, whose cache can fool you again. If the mail server uses the same certificate, check ports 465 and 993 too. Make sure the next renewal installs the full chain as well, or the problem will return in a year.