The key distinction: Browsers connect while a CLI API client reports an unknown issuing authority. The visible error may appear at the last stage of a longer process; its source is not necessarily the screen or service that displays it. The steps below separate diagnosis from modification and define an observable success condition.
Recognize this failure and establish a baseline
Test the served chain with openssl s_client using the exact hostname. Record the observed result with its time and environment. If you have multiple sites, service accounts, installations or regions, label them clearly so a working control is not confused with the failing target.
DNS, the CDN edge, TLS termination and the origin are distinct hops. A response that looks correct from one network or cache tier can conceal a rule mismatch or a stale edge copy elsewhere. A precise comparison is usually more informative than clearing caches, restarting every service or changing unrelated permissions. Confirm the reproduction using a harmless sample and preserve the current configuration before editing it.
Three ways to isolate the cause
| Diagnostic angle | What to inspect | Interpret the result |
|---|---|---|
| Reproduction and scope | Test the served chain with openssl s_client using the exact hostname. | If the control succeeds, the difference between the two paths is evidence; do not change their shared infrastructure first. |
| Configuration or contract | The origin may omit an intermediate CA certificate or send an incorrect chain. | If the setting, identifier or interface differs from its documented contract, fix that discrepancy in the narrowest possible scope. |
| Runtime and downstream dependencies | Check SNI, alternate virtual hosts, certificate expiry and client trust stores. | If the initial configuration is consistent, use timestamps, error codes and component logs to identify the first failing hop. |
First safe fix: change one variable
Recommended correction: Install the full CA chain from the issuing provider without using an unrelated root. Apply it first in a staging environment or on one limited test object when production traffic, orders or private information could be affected. Write down the previous setting and expected result so a rollback is straightforward.
Why not reset everything? The origin may omit an intermediate CA certificate or send an incorrect chain. A broad reset can hide the original cause and create additional failures in permissions, orders, certificates or background jobs. If the proposed correction does not change the exact reproduction test, revert it and move to the advanced inspection instead of stacking speculative fixes.
Step-by-Step Troubleshooting
Choose Beginner for reversible checks or Advanced for scoped investigation with sanitized evidence.
Record the failure boundary
Browsers connect while a CLI API client reports an unknown issuing authority. Capture the precise timestamp, version and one anonymized request, screen or operation. The first objective is to distinguish a consistently failing action from an intermittent side effect; write down what still works.
Perform the smallest comparison
Test the served chain with openssl s_client using the exact hostname. Keep the account, configuration and data set constant wherever possible. If the comparison requires a staging environment, avoid reproducing it with real payment, customer or production credentials.
Make one reversible correction
Install the full CA chain from the issuing provider without using an unrelated root. Save or export the setting that will change, note its previous value and alter only this one likely cause. After the adjustment, do not proceed until you have run the same failing operation again.
Prove the outcome
Independent API clients validate the full chain without disabling verification. Repeat the test a second time, including after a safe restart or fresh request when relevant. Verify that a formerly working neighboring feature has not regressed.
Locate the technical ownership
The origin may omit an intermediate CA certificate or send an incorrect chain. Identify which component owns this state and whether it is an application setting, remote contract, data store, runtime or security policy. Correlate a single request identifier across layers.
Inspect the deeper signal
Check SNI, alternate virtual hosts, certificate expiry and client trust stores. Save only sanitized event identifiers, configuration names and measurements; mask credentials, tokens, private keys, customer information and raw personal content.
Separate competing explanations
Test the served chain with openssl s_client using the exact hostname. Compare the failing path to a control path. If both fail, investigate their shared dependency; if only one fails, focus on their first differing layer. Reassess the origin may omit an intermediate CA certificate or send an incorrect chain.
Validate safely and plan rollback
Independent API clients validate the full chain without disabling verification. Restore the previous setting if the exact failure persists. Document the observed result, the change identifier, and a small repeatable verification for the next release.
Advanced diagnosis: inspect the first failing boundary
Check SNI, alternate virtual hosts, certificate expiry and client trust stores. When reading logs, match the same request or transaction across components. A message produced downstream can be secondary to an earlier denial, timeout, incompatible contract or unavailable resource. Use a small known-good request to remove unrelated data from the comparison.
Evidence to keep: Capture the software or protocol version, a masked timestamp, the operation being attempted, the relevant configuration key, and the outcome of the control test. Note both positive and negative findings. If a security rule is involved, preserve the original protection and grant only a narrowly scoped supported exception.
Optional read-only diagnostic
If you have authorized access to the affected host and understand its environment, the following example only inspects state. Replace the example host, service, schema or namespace with your own; it does not repair anything by itself.
openssl s_client -connect api.example.com:443 -servername api.example.com -showcertsHow to verify the repair
Passing result: Independent API clients validate the full chain without disabling verification. Verify the exact operation rather than assuming that an adjacent screen, health endpoint or cached response proves success. Repeat once under normal conditions and check one previously healthy workflow for regressions.
If the result changes only in staging, compare release version, permissions, environment variables and network path with production. If success is intermittent, compare two successive runs and retain the corresponding log evidence before declaring the incident closed.
Solution Checklist
Safety and rollback
Avoid: Do not use insecure TLS flags as a permanent production fix. Store backups, before-and-after settings and sanitized evidence securely. If the action involves orders, identities, databases or customer information, complete an authorized rollback or request maintenance approval before making another production change.
If it still fails
Return to the first comparison: Test the served chain with openssl s_client using the exact hostname. Then investigate the remaining owner: Check SNI, alternate virtual hosts, certificate expiry and client trust stores. Escalate with a concise timeline and the exact point at which expected behavior differs. Do not send passwords, API keys, recovery codes, complete customer records or private signing material to outside support.
Prevent the next occurrence
Version DNS and edge rules, test both authenticated and anonymous paths, and periodically verify TLS and cache behavior from more than one region. Record the minimum regression test for this exact workflow: Independent API clients validate the full chain without disabling verification. This is more reliable than applying generic maintenance advice each time a dependency changes.