# Help Category: Common Errors

> Canonical: https://jethost.com/kb/category/common-errors/ · Results: 24 · Page 1 of 3

Fix the most common website and browser errors — SSL, connection, DNS, cache and WordPress errors — with clear, step-by-step guides for both visitors and site owners.

- [How to Fix Error 508 (Resource Limit Is Reached)](https://jethost.com/kb/how-to-fix-error-508-resource-limit-is-reached/) — Error 508 means your hosting account briefly hit one of its allocated resource limits, so the server stopped serving requests for a moment. It affects visitors as a short outage, and it points to your site using more than its share, not to a broken server. It is fixable, usually by cutting load or caching. […]
- [How to Fix Cloudflare Error 526 (Invalid SSL Certificate)](https://jethost.com/kb/how-to-fix-cloudflare-error-526/) — Cloudflare Error 526 means Cloudflare could not validate the SSL certificate on your origin server while SSL mode is set to Full (strict). It affects visitors trying to reach your site, and it points to a certificate problem on the server, not to Cloudflare. It is fixable, usually by installing a valid, trusted certificate. If […]
- [How to Fix Cloudflare Error 525 (SSL Handshake Failed)](https://jethost.com/kb/how-to-fix-cloudflare-error-525/) — Cloudflare Error 525 means the SSL handshake between Cloudflare and your origin server failed, so the secure connection could not be set up. It affects visitors when your Cloudflare SSL mode is Full or Full (strict), and it almost always traces back to the certificate or configuration on your server. It is fixable, usually by […]
- [How to Fix Cloudflare Error 522 (Connection Timed Out)](https://jethost.com/kb/how-to-fix-cloudflare-error-522/) — Cloudflare Error 522 means Cloudflare tried to open a connection to your origin server but it never answered in time. It affects every visitor to your site, and it almost always points to the server or its firewall rather than to Cloudflare. It is fixable once you confirm the server is up and reachable. If […]
- [How to Fix Cloudflare Error 520 (Web Server Returned an Unknown Error)](https://jethost.com/kb/how-to-fix-cloudflare-error-520/) — Cloudflare Error 520 means Cloudflare reached your origin server but got back an empty, unknown, or malformed response. It affects anyone trying to load your site, and it points to a problem on the server, not on Cloudflare. The good news: it is almost always fixable once you know where to look. If the trouble […]
- [How to Fix HTTP Error 504 (Gateway Timeout)](https://jethost.com/kb/how-to-fix-http-error-504-gateway-timeout/) — HTTP Error 504 – “Gateway Timeout” – means a gateway server waited for another server behind it and got no reply in time, so it gave up. The page didn’t load because something was too slow, not because it refused. It usually points to a slow script, server load, or a timeout set too low. […]
- [How to Fix HTTP Error 503 (Service Unavailable)](https://jethost.com/kb/how-to-fix-http-error-503-service-unavailable/) — HTTP Error 503 – “Service Unavailable” – means the server is up but can’t handle the request right now. It is usually temporary: a traffic spike, a resource limit, scheduled maintenance, or, on WordPress, an update that got stuck. Here is how to clear it. What the error means A 503 is the server saying […]
- [How to Fix HTTP Error 502 (Bad Gateway)](https://jethost.com/kb/how-to-fix-http-error-502-bad-gateway/) — HTTP Error 502 – “Bad Gateway” – means one server, acting as a gateway, got an invalid reply from another server behind it. The page didn’t load because the hand-off failed. It is usually temporary and caused by server load, a crashed PHP process, or a CDN like Cloudflare. Here is how to clear it. […]
- [How to Fix HTTP Error 500 (Internal Server Error)](https://jethost.com/kb/how-to-fix-http-error-500-internal-server-error/) — HTTP Error 500 – the “Internal Server Error” – means the server hit a problem but can’t say what, so it shows a blank or generic page instead of your site. It’s almost always fixable, and usually comes from a broken .htaccess file, a PHP memory limit, or a plugin or theme conflict. Here is […]
- [How to Fix the DNS_PROBE_FINISHED_BAD_CONFIG Error](https://jethost.com/kb/how-to-fix-dns-probe-finished-bad-config/) — DNS_PROBE_FINISHED_BAD_CONFIG means Chrome could not look up the site’s address because your DNS settings look wrong. The fault is almost always on your device or network, not the website, so a few local checks clear it fast. What the error means Your browser tried to match the site name to an IP address and the […]

> Next: https://jethost.com/kb/category/common-errors/page/2/