Help for owners
My site's padlock works on my computer but fails on some phones and apps
Short answer
Your server must send its own certificate and the intermediate certificates that link it to a trusted authority. If the intermediates are missing, some browsers cope and others, plus many apps and API clients, refuse. Browsers often cache intermediates, which hides the fault. The fix is installing the full chain on the server.
Does this sound like your situation?
- The padlock is fine on my laptop but customers on other devices see an error.
- My mobile app or an integration says the certificate is not trusted.
- A payment or webhook partner cannot connect to my site securely.
- It works in Chrome and fails in a command-line tool or another program.
- A certificate checker reports the chain as incomplete.
Why does this happen?
The intermediate certificate was not installed
A site certificate is signed by an intermediate authority, which browsers may not carry. nginx's documentation says some browsers reject such a certificate while others accept it, and that the server certificate must be combined with the bundle.
Confirmed by nginx.orgTechnical detail: The site looks fine in a browser but its SSL chain is incomplete
Browsers cache what they have seen
nginx notes that browsers often store intermediates they met before, so a site missing its bundle can still load for people who visited other sites. That is why your own device may look fine.
Confirmed by nginx.org
Apps and tools are stricter
Mobile apps, scripts and partner systems use their own trust lists and do not fetch missing links, so they fail where a browser did not.
The files were combined in the wrong order
The documentation says the server certificate must come first in the combined file. Otherwise the server can fail to start with a key mismatch.
Confirmed by nginx.orgTechnical detail: nginx refuses to start: private key does not match the certificate
What can I do about it today?
- Collect two examplesThe device or app that fails, with a screenshot of the error and the time it happened.
- Run a public certificate checker on your domainThese free online tools show whether the chain is complete. Share the result with your developer.
- Do not reinstall or buy a new certificate yetA new certificate installed the same way keeps the same fault.
- Tell integration partnersIf a partner is failing to connect, let them know a fix is under way.
- Ask your host for the certificate bundleMany hosts provide a chain file with the certificate.
When should I bring someone in?
- Your mobile app or payment connection is failing and the browser looks fine.
- The error started after a certificate was renewed or replaced.
- You do not know which file holds the intermediate.
How do I handle it?
- See what the server sendsI read the chain as an outside client sees it, not from a browser that caches.
- Combine the files in the correct orderServer certificate first, then the intermediates.
- Reload and retest from a clean clientCommand line and a fresh device, not only my own browser.
- Check apps and partnersMobile apps and webhook senders are tested against the fixed site.
- Note it for renewalsA renewal keeps the full chain, so the fault does not return.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Why can I not see the problem myself?
Your browser may already have the missing certificate cached from other sites. Other devices and apps do not.
Is the certificate itself bad?
Usually no. It is valid but delivered without the intermediates that connect it to a trusted authority.
Does it affect search ranking?
I do not have an official source for that, so I make no claim. The practical harm is that some users and apps cannot connect.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.