What it means
A certificate is trusted when its chain ends at a root certificate in the browser's root store. Yours ends at a root that isn't in the Mozilla root store, which is what Firefox and most Linux systems trust and closely matches the stores of Chrome, Safari and Windows. Common causes are certificates from a company's internal authority, test authorities, and authorities that browsers have stopped trusting.
Why it matters
Visitors see a security warning, and apps and API clients refuse to connect. Adding the root to your own computer makes the warning disappear for you only; everyone else still gets it.
How to fix it
- Check where the certificate came from. If it was issued by an internal or test authority, it was never meant for public visitors.
- Get a certificate from a publicly trusted authority. Let's Encrypt is free and trusted everywhere; your hosting provider can often issue one for you.
- Install it with its full chain and remove the old certificate, then reload the web server.
- If an appliance, proxy or security product in front of your server replaces certificates, configure it to present a publicly trusted one for this site.
Let's Encrypt with certbot
sudo certbot --nginx -d example.com -d www.example.com requests and installs a trusted certificate. Use
--apache for Apache.
Check it worked
Run the SSL check again. The chain should end at a well-known root, and the card should say "Trusted".