WordPress website issues: Fix 4 Common Errors

Why WordPress Website Issues Happen–And Why You Can Fix Them

WordPress website issues are a fact of life for anyone running a site on the world’s most popular platform. The good news? Most problems are fixable–even if you’re not a developer.

Quick Answers to Common WordPress Problems:

Issue	Quick Fix
Critical Error	Disable plugins via FTP, enable debug mode
Database Connection Error	Check wp-config.php credentials, repair database
White Screen of Death	Deactivate plugins, increase PHP memory
500 Internal Server Error	Rename .htaccess, reset permalinks
404 Errors on Posts	Reset permalinks in Settings
Stuck in Maintenance Mode	Delete .maintenance file via FTP

This guide walks you through the most common WordPress website issues, explains what causes them, and shows you how to fix them step by step. Most problems stem from a few key areas: plugin or theme conflicts, corrupted files, database problems, or server resource limits. Once you know what to look for, troubleshooting becomes much easier.

I’m Kevin Gallagher, founder of wpOncall. With over fifteen years of experience managing thousands of WordPress sites, I’ve seen every WordPress website issue imaginable. I’m here to help you solve yours and get your site back up and running.

First-Step Diagnostics: Is It Down for Everyone or Just You?

When your site won’t load, the first step is to determine if the WordPress website issue is global or local to your machine. If it’s down for everyone, it’s likely a server or site-level problem. If it’s just you, the fix is often simpler, like clearing a cache.

Here’s how to diagnose the problem systematically:

Use an uptime checker. Free tools like downforeveryoneorjustme.com check your site from multiple locations. If it reports your site is “up,” the problem is likely on your end.
Test in a different browser or incognito window. Your browser’s cache can sometimes cause loading issues. An incognito or private window bypasses this stored data. If the site loads, clear your browser’s cache and cookies.
Try another device or network. Use your phone (on mobile data, not Wi-Fi) to see if the site loads. If it does, the issue is with your computer or local network. You can also ask a friend in another location to check.
Restart your router. A simple restart can resolve temporary network glitches. You can also try using a VPN; if the site loads with the VPN on, your ISP might be having DNS issues.
Check your hosting provider’s status page. Most hosts have a public status page for server issues or maintenance. This is worth checking before you start troubleshooting, as a server outage is out of your hands. For WordPress.com sites, check the Automattic status page.

If you’ve confirmed the site is down for everyone, it’s time to troubleshoot the actual WordPress website issues causing the outage.

Decoding Common WordPress Website Issues and Error Messages

Error messages are clues, not catastrophes. They point you toward a solution. Let’s decode the most common WordPress website issues and their fixes.

How to Handle a ‘Critical Error on Your Website’

This error, often caused by a plugin/theme conflict or an outdated PHP version, is less scary than it looks thanks to WordPress’s fatal error protection.

Check your admin email. WordPress often sends a recovery email with a link to access your site in “recovery mode,” allowing you to deactivate the faulty plugin or theme.
Enable debug mode. If you didn’t get an email, access your site’s files via FTP or your host’s file manager. Open wp-config.php and change define( 'WP_DEBUG', false ); to true. Add define( 'WP_DEBUG_LOG', true ); below it to save errors to a debug.log file in the wp-content directory. This log will pinpoint the source of the error.
Deactivate plugins and themes. The most reliable fix is to disable all plugins and switch to a default theme. If you can’t access the dashboard, use FTP to rename the wp-content/plugins folder. If the site works, reactivate plugins one by one to find the culprit. For more details, see the Debugging in WordPress documentation.

Fixing the ‘Error Establishing a Database Connection’

This message means WordPress can’t connect to its database. The cause is usually incorrect credentials, a corrupted database, or a server issue.

Check wp-config.php credentials. Via FTP, open wp-config.php and verify that DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST are correct. You can find these details in your hosting control panel. Refer to the guide on editing wp-config.php.
Repair the database. WordPress has a built-in repair tool. Add define('WP_ALLOW_REPAIR', true); to your wp-config.php file. Then visit yourdomain.com/wp-admin/maint/repair.php. Click “Repair Database.” Important: Remove the line from wp-config.php when you’re done, as it’s a security risk.
Contact your host. If the steps above don’t work, the database server may be down. Contact your hosting provider for assistance.

Solving the WordPress ‘White Screen of Death’ (WSOD)

The WSOD is a blank white screen with no error message, typically caused by a plugin/theme conflict or exhausted PHP memory.

Deactivate all plugins. Via FTP, steer to the wp-content/ directory and rename the plugins folder to plugins_old. If your site reappears, a plugin is the cause. Rename the folder back and reactivate plugins one by one in the dashboard to find the faulty one.
Switch to a default theme. If plugins aren’t the issue, the theme might be. Via FTP, go to wp-content/themes/ and rename your active theme’s folder. WordPress will fall back to a default theme.
Increase PHP memory. Add define('WP_MEMORY_LIMIT', '256M'); to your wp-config.php file, just before the /* That's all, stop editing! */ line. For more information, see the PHP Memory limit documentation.

Troubleshooting the ‘500 Internal Server Error’

This vague error means something went wrong on the server. Common causes include a corrupted .htaccess file, plugin/theme conflicts, or exhausted PHP memory.

Rename your .htaccess file. Using FTP, find the .htaccess file in your WordPress root directory and rename it to .htaccess_old. If this fixes the site, go to Settings > Permalinks in your dashboard and click “Save Changes” to generate a new, clean file.
Deactivate plugins and themes. Follow the same process described for the WSOD to rule out plugin or theme conflicts.
Replace WordPress core files. If you suspect corrupted core files, download the latest version of WordPress from WordPress.org. Via FTP, upload and overwrite the wp-admin and wp-includes folders. Do not overwrite the wp-content folder or wp-config.php file.

Resolving Content, Functionality, and Access Problems

Not all WordPress website issues are critical errors. Sometimes, the problems are more subtle, like broken buttons or inaccessible pages. Here’s how to tackle them.

How to Fix Plugin and Theme Conflicts

Conflicts between plugins or themes are a leading cause of WordPress website issues. This happens when two pieces of code don’t work well together, causing anything from a visual glitch to a site crash.

The Deactivation Method: The classic way to find a conflict is to deactivate all plugins. If the problem disappears, reactivate them one by one, checking your site after each activation. The last plugin you enabled is the culprit. If you can’t access your dashboard, rename the wp-content/plugins folder via FTP to disable them all.
Theme Conflicts: To check for a theme conflict, switch to a default WordPress theme (like Twenty Twenty-Four) from Appearance > Themes. If the issue is resolved, the problem lies with your theme.
Use a Staging Site: Test updates and changes on a staging site–a clone of your live site–to avoid affecting visitors. Most quality hosts offer one-click staging.
Use the Health Check Plugin: The official Health Check & Troubleshooting plugin lets you disable plugins and switch themes only for your admin session, so you can troubleshoot without disrupting the live site.

What to Do When Stuck in ‘Maintenance Mode’

If your site is stuck showing “Briefly unavailable for scheduled maintenance,” it means an update was interrupted and a temporary file was left behind.

The fix is simple: delete the .maintenance file. Connect to your site via FTP or your host’s file manager, find the .maintenance file in your root directory, and delete it. Your site will immediately come back online. You may need to enable viewing of hidden files to see it. For more details, see the WordPress documentation on this issue.

Fixing ‘404 Not Found’ Errors on Posts and Pages

If your homepage loads but internal pages show a “404 Not Found” error, the issue is almost always with your permalinks. WordPress uses “rewrite rules” to create user-friendly URLs, and these can sometimes become corrupted.

The solution is to reset your permalinks. Go to Settings > Permalinks in your WordPress dashboard and simply click the “Save Changes” button. You don’t need to change any settings. This action flushes the old rules and regenerates them, fixing the 404 errors in most cases. If this doesn’t work, your server may need the mod_rewrite module enabled; contact your host for help. Learn more about pretty permalinks in the WordPress Codex.

Addressing ‘Connection Timed Out’ Errors

A “Connection Timed Out” error means your server took too long to respond, often because it’s overloaded. This is common on shared hosting plans when a site tries to perform a resource-intensive task.

Identify Resource Hogs: Deactivate plugins and switch to a default theme to see if the error stops. A poorly coded plugin or a heavy theme is often the cause.
Increase Server Limits: You can try increasing PHP’s max_execution_time. This setting is usually adjusted in your php.ini file or through your hosting control panel. The php.ini documentation has more technical details.
Upgrade Your Hosting: If timeout errors persist, your site has likely outgrown its hosting plan. Upgrading to a better plan or switching to managed WordPress hosting provides more resources and stability, reducing these types of WordPress website issues.

Advanced Troubleshooting and Preventative Maintenance

Beyond common errors, some WordPress website issues require a deeper look at your server configuration. More importantly, learning to prevent problems is the best strategy for a healthy site.

Domain, DNS, and Redirect Loop Issues

Problems at the domain and DNS level can make your site disappear or trap users in redirect loops.

DNS Errors: An error like DNS_PROBE_FINISHED_NXDOMAIN means your browser can’t find your server. This can happen if your domain has expired, your nameservers are incorrect, or there’s a DNS configuration issue. Use a tool like [whatsmydns.net](https://www.whatsmydns.net/#A/) to check DNS propagation and verify your domain’s A record points to your server’s IP address.
Redirect Loops: The ERR_TOO_MANY_REDIRECTS error often occurs after installing an SSL certificate or due to a misconfigured plugin. Ensure your WordPress Address and Site Address in Settings > General both use https://. If you use a CDN like Cloudflare, set its SSL/TLS mode to “Full (strict).” Also, try deactivating security or redirection plugins and clearing all caches.

Restoring Your Site and Managing Backups

Backups are your most critical safety net. A recent, working backup can turn a catastrophe into a minor inconvenience. Without one, you risk losing everything.

How to Restore: Most quality hosts offer one-click restoration from automated backups. You can also use a backup plugin to restore your site from the WordPress dashboard. Manual restoration via FTP and phpMyAdmin is also possible but requires more technical expertise.
The Golden Rule: Always back up your database and files before making major changes like updating WordPress core, themes, or plugins. This gives you a clean restore point if something goes wrong. For more details, see the official guide on [Backing up your database](https://wordpress.org/documentation/article/backing-up-your-database/). Set up automated daily backups and store them off-site (e.g., in cloud storage).

The Importance of Updates and Security

Outdated software is the #1 cause of hacked WordPress sites. Hackers use automated bots to scan for known vulnerabilities in old versions of WordPress core, plugins, and themes. Ignoring updates is like leaving your front door open uped.

Update Regularly: Make it a weekly habit to apply all available updates in your dashboard. Updates patch security holes, fix bugs, and improve performance.
Remove Unused Code: Delete any inactive plugins and themes. Even disabled, they can be a security risk.
Scan for Malware: If you suspect your site is hacked (e.g., strange redirects, spam content), use a reputable security plugin to scan your files and database. These tools can often identify and remove malware automatically. For more information, consult the WordPress Security documentation.

Diagnosing PHP and Other Technical WordPress Website Issues

Some problems stem from your server’s underlying configuration.

Use a Recommended PHP Version: Running an outdated PHP version can cause performance and security issues. Your site should be on PHP 7.4 or higher. You can usually change this in your hosting control panel.
Check PHP Error Logs: These logs, accessible via your hosting panel or FTP, record all PHP errors and can pinpoint the exact file and line of code causing a problem.
Fix File Permissions: If you can’t upload images, your file permissions may be incorrect. Folders should typically be set to 755 and files to 644. You can change these via FTP. The [Correcting File Permissions](https://developer.wordpress.org/advanced-administration/server/file-permissions/) guide provides detailed instructions.
Fix Custom Post Type 404s: If links to custom post types are returning 404 errors, simply go to Settings > Permalinks and click “Save Changes” to flush and regenerate WordPress’s rewrite rules.

Frequently Asked Questions about WordPress Problems

Here are quick answers to some of the most common questions we hear about WordPress website issues.

When should I contact my web host for help?

You should contact your host after you’ve tried basic troubleshooting without success. If you’ve disabled plugins, switched themes, and checked your configuration files, the problem is likely on the server side.

Reach out to them for:

Server-level errors (e.g., database server is down).
Hitting resource limits you can’t change yourself.
Confirmed outages on their status page.

When you contact support, provide the exact error message, the troubleshooting steps you’ve already taken, and any recent changes you made. This helps them solve your problem faster.

How do I fix the ‘Sorry, you are not allowed to access this page’ error?

This error usually means there’s a problem with your user permissions, a corrupted .htaccess file, or a plugin conflict.

Check User Role: Ensure your user account is set to “Administrator” under Users > All Users.
Reset .htaccess: Rename your .htaccess file via FTP. If you can then access the page, go to Settings > Permalinks and click “Save Changes” to create a new one.
Deactivate Plugins: A security or user role plugin might be the cause. Rename the plugins folder via FTP to disable all plugins and see if that resolves the issue.

Why are my changes not appearing on the live site?

This is almost always a caching issue. Caching speeds up your site by storing static versions of your pages, but it can prevent you from seeing new changes immediately.

To fix this, you need to clear all layers of cache:

Browser Cache: Perform a hard refresh (Ctrl+F5 on Windows, Cmd+Shift+R on Mac) or clear your browser’s cache completely.
Server-Side Cache: Many hosts have their own caching. Look for a “Purge Cache” button in your hosting control panel.
Caching Plugin: If you use a caching plugin, find its “Clear Cache” or “Purge Cache” option in the WordPress admin bar or plugin settings.
CDN Cache: If you use a Content Delivery Network (CDN) like Cloudflare, log into its dashboard and purge the cache from there.

After clearing all caches, your changes should be visible.

Conclusion: Keep Your WordPress Site Healthy and Error-Free

Navigating WordPress website issues is manageable with a methodical approach. Most problems, from critical errors to the White Screen of Death, have clear causes and straightforward solutions. By treating troubleshooting like detective work, you can resolve many issues on your own.

However, prevention is always better than a cure. The foundation of a stable, secure website is proactive maintenance. This includes:

Regularly updating WordPress core, themes, and plugins.
Using high-quality, reputable software.
Maintaining consistent, off-site backups.

We understand that you’d rather focus on your business than troubleshoot PHP errors. If you’ve tried the steps in this guide and are still stuck, or if you simply want an expert to handle it all for you, that’s why we built wpOncall.

We specialize in WordPress website security and support, providing daily updates, backups, and unlimited expert help for any WordPress website issue. Our team offers fast response times and the expertise to keep your site protected and performing at its best. Let us be your WordPress pit crew, so you can focus on what you do best.

Let our experts handle your WordPress customer care