📖 ~1 min read
Table of contents
Symptom & Impact
`zypper refresh` aborts with SSL handshake or certificate validation errors against SCC or local mirrors.
Environment & Reproduction
Occurs after CA bundle updates or when system clock drifts on registered SLES 16 hosts.
Root Cause Analysis
Expired or missing intermediate CA certificates break TLS to SUSE Customer Center.
Quick Triage
Check time sync first: `timedatectl status` and verify `/etc/ssl/ca-bundle.pem` is current.
Step-by-Step Diagnosis
Run `zypper –no-gpg-checks refresh -fdb` and inspect `/var/log/zypper.log` for the failing host.

Solution – Primary Fix
Reinstall `ca-certificates-mozilla` and run `update-ca-certificates`, then retry `zypper refresh`.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Temporarily point to a local SMT/RMT mirror that uses an internal CA you trust.
Verification & Acceptance Criteria
`zypper refresh` returns clean and `SUSEConnect –status` shows all products active.
Rollback Plan
Restore the previous `/etc/ssl` snapshot via `snapper undochange` if certificate state regresses.
Prevention & Hardening
Enable chronyd and monitor CA bundle versions via configuration management.
Related Errors & Cross-Refs
Often coincides with `SUSEConnect` 4xx/5xx errors and broken `zypper services` output.
Related tutorial: View the step-by-step tutorial for sles-16.
View all sles-16 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
SUSE Customer Center connectivity troubleshooting and `ca-certificates` package notes.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.