Skip to content
Rescue 404

/server-errors/

HTTP and Server Errors Troubleshooting

Decode HTTP status codes and browser connection errors—from 403 and 404 to 500, 502, 503, 504, and ERR_ connection failures.

48 topics · 12 published guides

Common symptoms

  • Specific HTTP status code on one or all pages
  • Browser ERR_ connection messages
  • Gateway timeouts under load
  • Origin down behind a CDN
  • Too many redirects

Start here

  1. 01 Record the exact status code or ERR_ message
  2. 02 Test the origin URL bypassing CDN if possible
  3. 03 Check server and application error logs
  4. 04 Note whether the error is global or path-specific

All problems in this category

Showing 48 topics · 12 published guides

Frequently asked questions

What is the difference between 502 and 503? +
502 usually means a gateway got an invalid response from upstream. 503 means the service is unavailable or overloaded and may recover when capacity returns.

Repair dispatch

Still Need Help Fixing Your Website?

If you are not comfortable editing website files, changing server settings, repairing a database, or troubleshooting a live website, professional help may prevent additional damage or downtime. We will review the problem before accepting the repair.

  • You will receive a clear explanation of the likely cause.
  • We will tell you if the issue falls outside our repair scope.
  • No additional work will be performed without approval.
  • A backup should be created whenever access and website condition allow it.

Do not share passwords through an unencrypted contact form — use Password Pusher (self-destructing link). Prefer a dedicated Rescue 404 admin account, not your personal owner login; if you cannot create one yet, we will add ours after repair.