Japan Server Error Fix Lab

Home / Cloudflare / Cloudflare

Cloudflare 526 safe restart decision response

A Cloudflare safe restart decision note for 526: TLS or certificate failure caused by hostname mismatch, expired chain, protocol policy, SNI, or mixed content. It includes evidence, output examples, branches, and the smallest reliable fix.

high5265 min read
First command
grep -R "526" ./logs
First evidence

Treat 526 as a safe restart decision case. First collect evidence for whether reload, restart, queue drain, or rollback is safer.

Search queries
Cloudflare 526Cloudflare error 526Cloudflare 526 safe restart decision response

When this happens

Use this when a restart might fix the symptom but could also interrupt users or jobs. Do not stop at the screen message; validate whether reload, restart, queue drain, or rollback is safer first.

Symptom checklist

  • 526 appears repeatedly in the Cloudflare UI or logs.
  • CF-Ray, SSL mode, proxied DNS, origin response differs between successful and failed requests.
  • The issue appears only after separating proxied requests from direct origin requests.
  • It often follows deploys, permission changes, configuration edits, or data refreshes.

Likely causes

  • 526 specifically changes the investigation surface for Cloudflare: verify the exact failing object, route, user, and timestamp before applying the broader pattern.
  • The certificate chain, hostname, SNI, or TLS policy does not match the request.
  • A proxy or load balancer terminates TLS with a different certificate than the origin.
  • Browsers may cache HSTS or mixed-content decisions after the server is fixed.
  • The visible browser error hides whether the failure is certificate, protocol, or content policy.
  • A renewal completed in the panel but the web server still serves the previous certificate.
  • For the safe restart decision case, the first useful clue is whether reload, restart, queue drain, or rollback is safer.

First 1-minute checks

  1. Write down the first failure time, latest change, affected user, path, and object ID.
  2. Compare CF-Ray, SSL mode, proxied DNS, origin response for success and failure in the same window.
  3. Test the hypothesis: TLS or certificate failure caused by hostname mismatch, expired chain, protocol policy, SNI, or mixed content.
  4. Classify this as safe restart decision: whether reload, restart, queue drain, or rollback is safer.
  5. Capture current values before changing configuration.

First evidence

Treat 526 as a safe restart decision case. First collect evidence for whether reload, restart, queue drain, or rollback is safer.

Output examples

Normal output

Config test passes and active requests or jobs can be drained safely.

Failing output

The service is crash-looping, has invalid config, or still has in-flight critical jobs.

Output-to-action branches

  • A restart might fix the symptom but could also interrupt users or jobs.
    Run config tests, inspect active jobs, choose reload when possible, and prepare rollback.
  • The working and failing outputs differ.
    Act on the differing layer first: For 526, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
  • Command output is normal but users still fail.
    Separate browser cache, cookies, permissions, and network location before declaring it fixed.

Do not do this

  • Do not restart blindly before saving logs and validating configuration.
  • Do not change multiple layers before identifying the failing layer.
  • Do not delete production data, grant broad permissions, or disable security controls as a first response.

Evidence quality

Auto-generated operator draft: includes issue-specific causes, commands, output branches, and unsafe-action warnings. Official-source links and real incident validation are queued for enrichment.

Commands to run first

grep -R "526" ./logs
curl -Iv https://example.com --resolve example.com:443:ORIGIN_IP
openssl s_client -connect ORIGIN_IP:443 -servername example.com -showcerts
curl -sI https://example.com | grep -i 'cf-ray\|server'
dig +short example.com
openssl s_client -connect example.com:443 -servername example.com -showcerts
curl -Iv https://example.com
nmap --script ssl-enum-ciphers -p 443 example.com
systemctl status SERVICE --no-pager && journalctl -u SERVICE -n 100 --no-pager

Fix order

  1. Record the full 526 message, failing URL, user, object ID, and latest change.
  2. Collect issue-specific evidence for TLS or certificate failure caused by hostname mismatch, expired chain, protocol policy, SNI, or mixed content.
  3. Compare the failing case with a successful case before editing settings.
  4. If this is the safe restart decision branch, Run config tests, inspect active jobs, choose reload when possible, and prepare rollback.
  5. Re-check with the same command and URL, then record the normal output.

Actions by cause

  • For 526, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
  • Inspect the returned certificate with SNI before editing DNS.
  • Install the full chain and reload the web server or load balancer.
  • Align TLS mode, cipher policy, and origin certificate policy.
  • Replace insecure embedded assets when the issue is mixed content.
  • Clear HSTS or browser cache only after confirming the server response is corrected.
  • For the safe restart decision branch, Run config tests, inspect active jobs, choose reload when possible, and prepare rollback.

Verification metadata

  • operator-draft
  • official-reference-linked
  • 2026-07-23

Update queue

  • Review cadence
    weekly-source-review
  • Next enrichment
    Add one official-source check and one real output example for Cloudflare 526.

Environment-specific checks

  • Shared hosting, proxies, VPNs, or CDN layers can change proxied requests from direct origin requests results.
  • Do not trust only the Cloudflare UI; compare command output.
  • Japanese hosting panels may show completion before DNS or SSL fully propagates.
  • Test from both office and external networks.

Prevent it next time

  • Store normal examples for CF-Ray, SSL mode, proxied DNS, origin response.
  • Add SSL mode, origin certificate, and Cloudflare IP allow rules to the release checklist.
  • Keep recurring errors in the same note format.
  • Split alerts by error rate, latency, certificates, disk, and permission changes.