NEW automatic WordPress repair.

A fatal PHP error, almost always from one plugin or theme. We turn on error logging, disable plugins, find the exact culprit, then bring the healthy ones back. The safe auto-fix above does this for you.

The same kind of fatal error, but with the message hidden. We switch on WP_DEBUG, read the real error from the log, and disable whatever is crashing the page.

Usually an admin-only plugin conflict. We rename the plugins folder over FTP to disable everything at once, confirm the dashboard returns, then re-enable them one by one to catch the bad one.

A page builder, shortcode, or theme template is throwing an error on that template. The log pinpoints the file; we disable or roll back the offending component.

WordPress tried to email you a recovery link. If your site can’t send email, that link never arrives — which is exactly when this tool helps you get in without it.

An update half-applied or introduced an incompatibility. If you made a safety copy we roll straight back to it; otherwise we disable the updated plugin/theme and restore a clean version.

The database name, user, password or host in wp-config.php is wrong, or the database server is down. We verify the values over FTP. cPanel Confirm them under MySQL® Databases, and remember the host isn’t always localhost.

One or more tables are corrupted. We can enable WordPress’s built-in repair via define('WP_ALLOW_REPAIR', true). cPanel Or repair the table directly in phpMyAdmin → select tables → Repair table.

WordPress can’t see its tables — usually a wrong table prefix or a database that was emptied. We check the $table_prefix in wp-config.php against what’s actually in the database.

The table prefix in wp-config.php doesn’t match your database (common after a migration). We line the prefix back up so WordPress finds its data.

New host, new database credentials and often a new DB host name. cPanel Grab the correct details from MySQL® Databases and we’ll update wp-config.php for you.

Typically a broken .htaccess, an exhausted memory limit, or wrong permissions. We reset .htaccess to WordPress defaults and raise memory safely. cPanel The real reason is logged in Metrics → Errors.

The server is overloaded or PHP isn’t responding — often a resource limit on a crowded, oversold host. If it keeps happening, it’s a hosting problem, not a WordPress one (see our hosting tip below).

A permissions or .htaccess deny rule, or a missing index file. We correct the files we touch. cPanel Fix folder/file permissions in File Manager → Permissions.

Your permalink rules are gone. The fix is to regenerate them — usually by resaving Settings → Permalinks, or we restore a default .htaccess.

A loop between http and https, or a mismatch between your WordPress Address and Site Address. We set both correctly and align your SSL redirect.

PHP timed out or hit a server resource cap. We lighten the load (disable a heavy plugin, raise limits where allowed), but persistent 502s point to an underpowered host.

WordPress ran out of memory. We raise WP_MEMORY_LIMIT in wp-config.php. cPanel You can also raise memory_limit in the MultiPHP INI Editor.

A script ran longer than the server allows. cPanel Raise max_execution_time in the MultiPHP INI Editor, and we’ll find what’s running so long.

Usually too many plugins, no caching, or a slow, oversold server. We flag heavy and abandoned plugins; for the server side, the single biggest speed-up is moving to a fast host like InstantAccess.net.

Often a bloated wp_options autoload or a plugin polling on every page. We help trim autoloaded data and identify the culprit plugin.

The account is full — backups, logs and old uploads are the usual offenders. cPanel Check the Disk Usage tool to see what’s eating space.

We check selected core files and look for executable PHP in uploads. The tool can quarantine flagged upload files and replace checked core files with verified WordPress copies. A full compromise still needs a professional malware review, password rotation, and database inspection.

Classic SEO-spam injection in core files and the database. We clean the injected code and replace tampered core files with originals.

A backdoor created them. We help remove the rogue accounts, but the real fix is finding and deleting the backdoor file — which our malicious-file scan looks for.

Malicious code in .htaccess, index.php, or injected JavaScript. We reset .htaccess and hunt down the injected script.

Clean the infection first, then request a review in Google Search Console. Our free scan also checks whether your server IP sits on a spam blacklist.

That folder should never run PHP — those files are almost certainly malware. We quarantine them and can add a rule to stop PHP executing in wp-content/uploads.

No valid SSL certificate is installed. cPanel Turn on AutoSSL under SSL/TLS Status — a free certificate issues automatically, usually within minutes.

Your page is https but still loads some images, scripts or styles over http. We update those URLs to https so the padlock goes solid.

cPanel Re-run AutoSSL in SSL/TLS Status to renew it. If it won’t renew, DNS or domain validation is usually the blocker.

A redirect rule in .htaccess plus matching site URLs does it. We can add the rule and update WordPress’s addresses so every visitor lands on the secure version.

The certificate doesn’t match the domain, or none is installed for it. cPanel Confirm the right domain is covered in SSL/TLS Status.

PHP’s built-in mail is unreliable and often blocked. The fix is to send through proper SMTP. We can point you to a free SMTP setup so your site’s mail actually lands.

Missing SPF, DKIM or DMARC records. cPanel Open Email Deliverability — it flags exactly what’s missing and can repair the records for you.

Our free scan now checks this. A listing means the server has been sending spam — often a sign of a hack on a shared box. Clean the site, request delisting, and if it’s a chronic shared-host problem, move to a reputable host like InstantAccess.net.

Same root cause as above — unreliable PHP mail. An SMTP plugin fixes resets, notifications and WooCommerce receipts in one go.

Use the emergency administrator tool above: it stages a one-time helper that creates a fresh admin login, then deletes itself. Your database password is never read.

We can create a new admin for you, or you can reset the password directly. cPanel In phpMyAdmin, edit your row in wp_users and set the password with the MD5 function.

Usually a site-URL mismatch or a plugin printing output too early. We check your addresses and disable the offending plugin.

Stale cookies or a wrong Site Address. Clearing cookies plus correcting the site URL in the database fixes the loop.

A table-prefix mismatch hides the users table. We realign the prefix so your existing admin works again.

An update didn’t finish and left a .maintenance file behind. One click removes it and you’re back online instantly.

A stuck lock from an interrupted update. We clear the core_updater.lock row so updates run again.

We disable that single plugin (renaming its folder), confirm the site returns, then help you reinstall a clean, compatible version.

Wrong file ownership or permissions stop WordPress writing files. cPanel Reset ownership/permissions in File Manager, or we correct the affected files.

Use the plugin health check above once you’re connected — it flags out-of-date, abandoned, and PHP-incompatible plugins, the ones most likely to crash the site again.

The uploads folder isn’t writable, or the disk is full. We check permissions; cPanel verify free space in Disk Usage.

Folders 755, files 644, and wp-config.php tightened to 640 or 600. cPanel Set them in File Manager → Permissions.

A stray character or syntax error takes the whole site down. We restore the previous version of the file over FTP so you’re instantly back.

We reset it to the standard WordPress rules. If you had custom rules, we preserve a backup so nothing is lost.

cPanel Open FTP Accounts to see or create them. Tip: make a temporary FTP account just for this repair and delete it afterward.

cPanel Use MultiPHP Manager, select your domain, and pick a supported version — we’ll tell you which one your site needs.

cPanel The Backup tool downloads a full copy. For just the WordPress side, our snapshot feature saves your plugins, themes and mu-plugins on your own server.

DNS can take time to propagate, or the nameservers aren’t pointed at your host yet. Confirm the nameservers match your hosting account and give it a little time.

If you’re fighting constant 500/503 errors, slow loads, resource limits, or blacklist trouble, the server is the problem. We host and recommend InstantAccess.net — modern cPanel, current PHP, free SSL and daily backups.