Website Repair
Help and Troubleshooting Guide
Clear explanations for WordPress, hosting, server, PHP, database, DNS, SSL, email, and performance problems—organized for people searching Google or asking AI assistants.
Issues we can fix
Website failures we diagnose and repair
Open a guide for safe DIY steps, or request a paid diagnostic when you want a professional to stabilize it.
400 · Server Errors
400 Bad Request
A 400 Bad Request means the server understood you reached it but refused the request as malformed or otherwise invalid—oversized/corrupt headers or cookies, bad URL encoding, WAF rejection, or a client sending a body the app cannot parse. Fix or clear the offending request data; this is not a generic “site down” outage.
Fix this error →
401 · Server Errors
401 Unauthorized
A 401 Unauthorized means the server requires valid credentials to access this resource and either none were sent or the ones sent were rejected — it is a login/authentication failure, not a permissions block like 403 or a missing page like 404. Fix the credentials, the authentication method, or the rule demanding them, depending on where the request is failing.
Fix this error →
403 · Server Errors
403 Forbidden
A 403 Forbidden means access was denied for this URL — commonly wrong file permissions, a deny rule in `.htaccess`, ModSecurity or WAF blocks, IP denylists, hotlink protection, or ownership that PHP cannot read. Fix the specific deny rule or permissions rather than chmodding everything to 777.
Fix this error →
404 · Server Errors
404 Not Found
A 404 means the server responded but could not find a matching resource—on WordPress that is usually broken permalinks, a deleted/unpublished page, a wrong document root after migration, or a CDN still caching an old 404. Confirm the URL exists in wp-admin, resave permalinks, and purge caches before rewriting the whole site.
Fix this error →
429 · Server Errors
429 Too Many Requests
HTTP 429 Too Many Requests means a rate limit, bot challenge, or abuse rule stopped this client from making more requests for a while—wait out Retry-After if present, then identify which layer (host, Cloudflare, security plugin, or API) is throttling before cutting limits that protect the site.
Fix this error →
500 · Server Errors
500 Internal Server Error
A 500 Internal Server Error means the server reached your site but crashed while handling the request — commonly a PHP fatal, bad `.htaccess`, wrong permissions, or exhausted memory on WordPress. Read the error log first, then isolate plugins and theme and repair `.htaccess` or memory — do not keep refreshing and hoping.
Fix this error →
502 · Server Errors
502 Bad Gateway
A 502 Bad Gateway means a reverse proxy or load balancer could not get a valid response from the upstream (often PHP-FPM, Apache, or your origin) — restart or repair the backend worker, then check timeouts and overload rather than chasing a WordPress PHP fatal alone.
Fix this error →
503 · Server Errors
503 Service Unavailable
A 503 Service Unavailable means the server (or something in front of it) is temporarily refusing to handle requests — often WordPress maintenance mode, resource limits, overload, DDoS protection, or a host account suspension — so clear maintenance flags and capacity issues before treating it like a PHP fatal.
Fix this error →
504 · Server Errors
504 Gateway Timeout
A 504 Gateway Timeout means a proxy or gateway gave up waiting for an upstream response — often slow PHP, a stuck database query, exhausted workers, or a CDN/origin timeout — not a missing page. Confirm the real status code, find what is hanging in logs, then fix the slow upstream rather than only raising timeouts.
Fix this error →
Beaver Builder Problems
Beaver Builder After Migration Layout Broken
A Beaver Builder layout that breaks specifically after a site migration is almost always a URL, serialization, or asset problem introduced during the move — not damage to Beaver Builder itself. The most common causes are a non-serialization-safe search-replace that corrupted saved layout data, missing wp-content/uploads files, a CDN or cache still pointing at the old host, or mixed-content blocking on the new SSL setup. Fix URLs with a serialization-aware tool, confirm uploads copied completely, and check for mixed-content warnings before assuming the layout data is lost.
Fix this error →
Beaver Builder Problems
Beaver Builder Editor Blank
A blank Beaver Builder editor — a white or gray canvas with the toolbar visible but no rows or modules rendering — is different from an editor that spins forever and never finishes loading. Blank canvas usually points to a JavaScript error breaking the panel after it loads, a rendering conflict from theme CSS or an optimizer, or a corrupted layout, while an endless spinner points to admin-ajax, memory, or a stuck request. Check the browser console for JavaScript errors first, then work through cache and conflict isolation.
Fix this error →
Beaver Builder Problems
Beaver Builder Editor Not Loading
When the Beaver Builder editor will not load — spinning forever, stuck on “Loading builder engine,” or failing outright — the usual causes are a plugin or theme conflict, an optimizer or CDN rewriting builder scripts, PHP memory limits, or a blocked admin-ajax request. Append `&safemode` to the editor URL to isolate a conflict, clear every cache layer, confirm admin-ajax is not returning a 403, and raise PHP memory before assuming Beaver Builder itself is broken.
Fix this error →
Beaver Builder Problems
Beaver Builder Layout Broken
A Beaver Builder layout that looks broken on the front end — columns stacked wrong, rows overlapping, spacing collapsed, or content out of order — is usually a stale CSS cache, a CDN serving an old stylesheet, a responsive/mobile setting, a missing module from a deactivated add-on, or a theme style conflict, rather than damage to the layout data itself. Compare the editor preview to the live front end first: if the editor looks correct and only the live page is wrong, it is almost always cache or CDN, not the layout.
Fix this error →
Beaver Builder Problems
Beaver Builder Update Broke Website
If your site broke right after updating Beaver Builder, Beaver Themer, or a Beaver Builder add-on — a critical error, layout collapse, or blank front end — the update most likely exposed a version mismatch between Beaver Builder and an add-on, a PHP compatibility issue, or a conflict with another plugin or the theme that only surfaces with the new code. Check debug.log for the fatal error first, then roll back the specific plugin that changed rather than guessing at unrelated fixes.
Fix this error →
cPanel Problems
Cannot Log In to cPanel
When cPanel rejects your login, refuses to load, or bounces you back to the login screen, the usual causes are a wrong login URL or port, an account lockout from failed attempts or a security app, stale cookies, or your host disabling the account for a billing or abuse hold. Confirm the exact address your host issued (often `yourdomain.com:2083` or a dedicated subdomain), clear cookies or try a private window, and check with your host before assuming the panel itself is broken.
Fix this error →
Plesk Problems
Cannot Log In to Plesk
When Plesk rejects your login, times out, or bounces back to the login screen, the usual causes are a wrong URL or port (Plesk normally listens on `:8443`), a temporary lockout from Fail2Ban or ModSecurity after failed attempts, a suspended subscription, stale cookies, or the Plesk service itself down on the server. Confirm the exact address and port your host gave you, wait out any lockout instead of retrying, and check for a suspension notice before assuming the panel is broken.
Fix this error →
WordPress Admin Problems
Cannot Log In to WordPress Admin
Most WordPress admin login failures come from wrong credentials, a redirect loop (URL or HTTPS mismatch), a security plugin lockout, or a PHP error that breaks wp-login.php or the dashboard after auth. Recover by resetting the password via hosting or database tools, clearing cookies, fixing siteurl/home, and temporarily disabling security plugins via FTP—not by repeatedly guessing passwords.
Fix this error →
Cloudflare Errors
Cloudflare Blocking wp-admin (WordPress Repair)
When Cloudflare is blocking wp-admin, check Security Events for a WAF, custom rule, rate limit, or Bot Fight action on /wp-admin/ and /wp-login.php, then allowlist your IP or skip the false-positive rule for those paths—without turning off protection for the whole site.
Fix this error →
520 · Cloudflare Errors
Cloudflare Error 520
Cloudflare Error 520 means Cloudflare reached your origin and got an empty, malformed, or otherwise unusable HTTP response—fix origin crash logs, oversized headers, firewall interference, and protocol mismatches before changing DNS or SSL modes.
Fix this error →
521 · Cloudflare Errors
Cloudflare error 521
Cloudflare Error 521 means Cloudflare reached your origin server’s IP but the web server there actively refused the connection — usually because the web service is stopped, crashed, or a firewall is blocking Cloudflare’s IP ranges. Confirm the origin web server is running and reachable on port 80/443 before touching DNS or Cloudflare settings.
Fix this error →
522 · Cloudflare Errors
Cloudflare Error 522
Cloudflare Error 522 means Cloudflare resolved your DNS but could not finish a TCP connection to your origin before its timeout. Confirm the origin web server is running, listening on the proxied ports, not overloaded, and not firewalling Cloudflare’s IP ranges—then correct any stale origin IP in Cloudflare DNS.
Fix this error →
523 · Cloudflare Errors
Cloudflare error 523
Cloudflare Error 523 means Cloudflare cannot reach your origin’s IP at the routing/address level—verify the proxied A/AAAA (or CNAME target) points at the current host IP and that the network path to that origin is not blackholed before treating it like a refused connection or timeout.
Fix this error →
524 · Cloudflare Errors
Cloudflare Error 524
Cloudflare Error 524 means Cloudflare successfully connected to your origin server but the origin took too long to send back a complete HTTP response — usually slow PHP, a stuck database query, or exhausted server resources, not a network outage. Fix what is slow on the origin rather than only raising Cloudflare timeout settings.
Fix this error →
525 · Cloudflare Errors
Cloudflare Error 525
Cloudflare Error 525 means the TLS handshake between Cloudflare and your origin failed while SSL/TLS mode is Full or Full (strict)—confirm port 443 is open, a usable certificate is installed on the origin, and cipher/SNI settings match before treating it like a timeout or refused connection.
Fix this error →
129 published guides · more inventory titles coming soon · Browse all categories
Signal board
Browse by category
Grouped by system so you can find the right area without scanning every specialty channel.
5 systems · 25 diagnostic channels
CMS & Applications
WordPress, plugins, themes, builders, and storefront software.
Infrastructure
Hosting accounts, servers, PHP, databases, and control panels.
Network & Security
DNS, certificates, Cloudflare, and compromise / hardening issues.
Performance
Speed, caching layers, and CDN behavior.
Operations
Backups, migrations, email delivery, admin access, and general site issues.