How to Troubleshoot Common WordPress Website Problems Print

  • wordpress login, database connection, cpanel, plugin conflict, wordpress troubleshooting, php errors, website down, white screen, critical error, wp toolkit, error 500
  • 0

How to Troubleshoot Common WordPress Website Problems

WordPress websites can occasionally experience problems caused by software updates, plugin conflicts, theme compatibility issues, database errors, or hosting configuration changes.

Some problems are relatively easy to identify, while others require additional investigation.

Lagrange Point Media (LPM) provides several tools through cPanel that can help DIY Hosting customers diagnose common WordPress issues.

This guide explains how to identify and troubleshoot frequent WordPress errors without making unnecessary changes to your website.

1. Before You Begin Troubleshooting

Before making changes, gather some basic information about the problem.

Consider:

  • When did the problem begin?

  • Was WordPress recently updated?

  • Were any plugins or themes installed or modified?

  • Was the PHP version changed?

  • Does the problem affect the entire website or only certain pages?

  • Can you still access the WordPress administration dashboard?

  • Are other websites on the same hosting account affected?

If your website is still accessible, create a current backup before modifying files, plugins, themes, or database information.

Important: Avoid making several changes at once. Changing one thing at a time makes it easier to identify the actual cause of a problem.

2. WordPress Displays a Critical Error

WordPress may display a message similar to:

"There has been a critical error on this website."

This generally indicates that WordPress encountered a fatal PHP error.

Possible causes include:

  • An incompatible plugin.

  • A theme problem.

  • A PHP version compatibility issue.

  • A failed or incomplete update.

  • An error in custom PHP code.

  • A missing or damaged application file.

How to troubleshoot:

  1. Check whether the problem began after a recent update or installation.

  2. Review any WordPress recovery email sent to the site's administration email address.

  3. Check available PHP error logs.

  4. If a particular plugin or theme was recently changed, investigate that component first.

  5. Review compatibility requirements before making further changes.

WordPress may provide a recovery mode link by email when certain fatal errors occur. This feature does not work for every error.

Important: The critical error message alone does not identify the exact cause. Error logs are often necessary for a reliable diagnosis.

3. Troubleshooting a Plugin Conflict

Plugins can conflict with WordPress, themes, PHP versions, or other plugins.

If you suspect a plugin:

  1. Sign in to your WordPress dashboard.

  2. Navigate to Plugins > Installed Plugins.

  3. Identify any recently installed or updated plugins.

  4. Deactivate the suspected plugin if doing so will not disrupt essential business functions.

  5. Test the affected website feature.

  6. Review the plugin's documentation and compatibility requirements.

If the problem disappears after deactivation, the plugin or an interaction involving it may be responsible.

For more complicated issues, testing in a staging environment is preferable when one is available.

Warning: Deactivating plugins used for payments, memberships, forms, or bookings can interrupt important website functionality.

4. What If You Cannot Access the WordPress Dashboard?

If a plugin error prevents access to the WordPress dashboard, you may be able to disable the suspected plugin through cPanel File Manager.

  1. Sign in to the LPM Client Portal.

  2. Open cPanel from your active hosting service.

  3. Search for File Manager.

  4. Navigate to your WordPress installation directory.

  5. Open wp-content/plugins.

  6. Locate the suspected plugin's folder.

  7. Rename the folder temporarily.

  8. Try accessing your website again.

For example, you could temporarily rename:

contact-form-plugin

to:

contact-form-plugin-disabled

This prevents WordPress from loading the plugin from its expected directory and can cause WordPress to mark it as inactive.

Important: This is a troubleshooting technique, not a permanent repair. Restore the directory name when appropriate and investigate the underlying problem.

5. Error Establishing a Database Connection

WordPress may display:

"Error establishing a database connection"

This means WordPress could not establish the database connection it needs.

Possible causes include:

  • Incorrect database credentials.

  • A database user without the required permissions.

  • An incorrect database hostname.

  • A database service problem.

  • Missing or damaged database information.

How to troubleshoot:

  1. Open cPanel.

  2. Confirm that the expected database exists.

  3. Check that the appropriate database user is assigned to it.

  4. Open File Manager.

  5. Locate the WordPress wp-config.php file.

  6. Review the configured database name, username, and hostname.

  7. Compare those settings with the database information in cPanel.

The database connection settings commonly include:

  • DB_NAME

  • DB_USER

  • DB_PASSWORD

  • DB_HOST

Security Warning: The wp-config.php file contains sensitive credentials. Do not share its complete contents or post database passwords in support tickets.

If the credentials appear correct, the problem may involve the database service or another server-side issue.

6. Understanding HTTP 500 Errors

An HTTP 500 Internal Server Error indicates that the server encountered an unexpected condition while processing the request.

On WordPress websites, possible causes include:

  • PHP fatal errors.

  • Application configuration problems.

  • Invalid .htaccess directives.

  • Plugin or theme failures.

  • File permission problems.

  • Server-side configuration issues.

How to troubleshoot:

  1. Check whether the error affects the entire website.

  2. Review recent changes.

  3. Examine available error logs.

  4. Check whether the problem began after a PHP version change.

  5. Investigate recently modified plugins, themes, or configuration files.

Do not assume every HTTP 500 error is caused by WordPress.

Important: An HTTP 500 status is a general error response. The relevant server or application logs are usually needed to determine the specific cause.

7. WordPress Shows a Blank or White Screen

A blank page may indicate that WordPress or PHP encountered an error that is not being displayed to visitors.

Possible causes include:

  • A PHP fatal error.

  • A plugin or theme conflict.

  • An incomplete update.

  • Application resource limitations.

  • Custom code errors.

Begin by reviewing recent changes and checking available error logs.

If the problem started after installing a plugin, investigate that plugin first.

Tip: Avoid enabling public display of detailed PHP errors on a live website. Error messages may expose sensitive application information.

8. Checking WordPress Debug Logs

WordPress includes debugging settings that can help identify PHP-related problems.

These settings are defined in the wp-config.php configuration file.

For example:

define( 'WP_DEBUG', true );

define( 'WP_DEBUG_LOG', true );

define( 'WP_DEBUG_DISPLAY', false );

When configured correctly, WordPress can write debugging information to a log file, commonly wp-content/debug.log.

Important: These settings should be used carefully. Debug logging can expose sensitive information and generate large files.

Before enabling debugging:

  1. Create a backup of wp-config.php.

  2. Check whether the constants already exist.

  3. Modify existing definitions rather than adding conflicting duplicates.

  4. Keep debug messages hidden from public visitors.

  5. Disable unnecessary debugging after troubleshooting.

  6. Remove or secure debug logs containing sensitive information.

Debug logging does not capture every possible server or application problem.

9. Troubleshooting WordPress Login Problems

If you cannot access your WordPress dashboard, first determine whether the login page loads.

For a standard WordPress installation, the login area is commonly available at:

https://example.com/wp-admin/

Replace example.com with your domain.

If you forgot your password:

  1. Open the WordPress login page.

  2. Click Lost your password?

  3. Enter your username or account email address.

  4. Follow the password reset instructions.

If the reset email does not arrive, check your spam folder and verify that your website can send email.

WP Toolkit may also provide a way to access the administration dashboard for a recognized installation.

Note: Security plugins and custom configurations may change the standard WordPress login address or restrict access.

10. Troubleshooting Broken Pages and 404 Errors

If your homepage works but other WordPress pages display 404 errors, the problem may involve permalink configuration or URL rewriting.

To investigate:

  1. Sign in to WordPress.

  2. Navigate to Settings > Permalinks.

  3. Review the selected permalink structure.

  4. Click Save Changes to refresh the configuration.

  5. Test the affected pages again.

WordPress may update its rewrite rules when you save permalink settings, depending on file permissions and server configuration.

Important: Do not change your permalink structure unnecessarily on an established website. Changing URLs can break existing links and may require redirects.

If the problem continues, review relevant .htaccess rules and application configuration.

11. Troubleshooting a Slow WordPress Website

Slow website performance can have several causes.

Common contributors include:

  • Large, unoptimized images.

  • Excessive or inefficient plugins.

  • Slow database queries.

  • External scripts and third-party services.

  • Resource-intensive background tasks.

  • Inefficient themes or custom code.

  • Caching configuration problems.

  • Hosting resource limitations.

To investigate:

  1. Identify which pages are slow.

  2. Determine whether the problem affects visitors, administrators, or both.

  3. Check for recently installed plugins or themes.

  4. Review image sizes and external resources.

  5. Examine available hosting resource information.

  6. Review caching configuration.

  7. Investigate database or application errors when indicated.

Important: Installing a caching plugin does not automatically resolve every performance problem. Incorrect caching can also interfere with shopping carts, logins, and other dynamic website features.

12. Troubleshooting Problems After Changing PHP Versions

WordPress, plugins, and themes must be compatible with the PHP version running your website.

If your website stops working after changing PHP versions:

  1. Open cPanel.

  2. Search for MultiPHP Manager.

  3. Locate your domain.

  4. Review the selected PHP version.

  5. If necessary, temporarily return to the previously working version, provided it remains available.

  6. Test your website.

  7. Investigate compatibility before upgrading again.

LPM provides multiple PHP versions, but not every version is suitable for every WordPress installation.

Important: Reverting to an older PHP version may restore functionality, but it does not correct the underlying compatibility issue. Unsupported PHP versions should not be used as a permanent solution.

13. Troubleshooting Problems After an Update

A WordPress update may complete successfully while a plugin, theme, or custom feature stops functioning.

If this happens:

  1. Identify what was updated.

  2. Review the update's release notes.

  3. Check available error logs.

  4. Test the affected functionality.

  5. Investigate compatibility with other components.

  6. Consider restoring an appropriate backup if necessary.

Avoid repeatedly reinstalling or updating components without identifying the cause.

Warning: Restoring an older database backup can overwrite newer posts, orders, registrations, and other website data.

14. Understanding WordPress Maintenance Mode

WordPress may temporarily display a maintenance message while applying updates.

This is normal during certain update operations.

If an update is interrupted, WordPress may remain in maintenance mode.

In some cases, a temporary .maintenance file remains in the WordPress installation directory.

If you have confirmed that no update is running, an experienced user can inspect the installation directory using File Manager and remove a stale .maintenance file when appropriate.

Warning: Do not remove the file while an update is still in progress. Doing so may interfere with the update process.

15. When to Contact LPM Support

Some WordPress problems involve the hosting environment rather than the application itself.

Contact LPM support when:

  • Your website is inaccessible and you cannot identify the cause.

  • You encounter repeated server errors.

  • A database connection problem persists despite correct settings.

  • File permissions prevent normal website operation.

  • A hosting-related configuration issue is suspected.

  • You need assistance reviewing available restoration options.

Submit a support ticket through the LPM Client Portal.

Please include:

  • Your domain name.

  • The exact error message.

  • When the problem began.

  • Any recent changes.

  • Whether the WordPress dashboard is accessible.

  • Which troubleshooting steps you've already attempted.

Screenshots of error messages can also be helpful.

LPM can assist with hosting-related problems. Advanced plugin troubleshooting, custom code repairs, and website development may require a separate service.


Additional Resources:


Was this answer helpful?

« Back