How to fix common WordPress errors

WordPress powers a huge share of business websites in Uganda, from salons in Ntinda to tour operators in Jinja. It is reliable most of the time, but every site owner eventually meets an error message that makes the heart sink. The good news is that most common WordPress errors have well known causes and simple fixes. This guide shows you how to fix common WordPress errors yourself, in a safe order, before you need to call a developer.

Before you fix anything: three safety steps

1. Take a backup. Download a copy of your files and database from your hosting control panel, or confirm your host has a recent backup you can restore.
2. Get access outside WordPress. Make sure you can log in to cPanel (or your host's panel) and use the File Manager or an FTP client such as FileZilla. Many errors lock you out of the dashboard, so this is your back door.
3. Change one thing at a time. Note what you change so you can undo it if it does not help.

1. The white screen of death

You open your site and see a completely blank page, or a message saying "There has been a critical error on this website." This is usually caused by a plugin or theme conflict, or PHP running out of memory.

How to fix it

1. Check your admin email. Newer versions of WordPress send a recovery mode link to the site admin address when a fatal error happens. Click it to log in and deactivate the faulty plugin.
2. If there is no email, open File Manager, go to wp-content, and rename the plugins folder to plugins-off. Reload your site. If it works, a plugin is to blame.
3. Rename the folder back to plugins, then rename individual plugin folders one by one until the site breaks again. The last one you renamed is the culprit.
4. If plugins are not the issue, switch to a default theme by renaming your active theme folder inside wp-content/themes.

2. Error establishing a database connection

This means WordPress cannot talk to its MySQL database. Your content is usually safe; the site just cannot reach it.

How to fix it

• Open wp-config.php and check that DB_NAME, DB_USER, DB_PASSWORD and DB_HOST match the database details in your hosting panel. A recent password change or migration often breaks this.
• In cPanel, open MySQL Databases and confirm the user is still assigned to the database with all privileges.
• If the details are correct, the database server may be overloaded or down. Contact your host and ask them to check.
• If the error appears only on the admin side, the database may need repair. Add define('WP_ALLOW_REPAIR', true); to wp-config.php, visit yoursite.com/wp-admin/maint/repair.php, run the repair, then remove the line straight away.

3. 500 Internal Server Error

A generic message meaning something went wrong on the server, without saying what. The most common causes are a corrupted .htaccess file, a plugin problem, or PHP limits.

How to fix it

1. In File Manager, enable "show hidden files", find .htaccess in your main folder and rename it to .htaccess-old.
2. Reload your site. If it works, log in and go to Settings, then Permalinks, and click Save. WordPress will create a fresh .htaccess file.
3. If the error continues, try the plugin folder trick from the white screen section.
4. Check the error log in cPanel (often under Metrics or Errors). It usually names the file causing trouble.

4. 404 errors on posts and pages

Your homepage loads, but clicking any post shows "Page not found". This is almost always a permalink issue.

Fix: go to Settings, then Permalinks, and click Save Changes without changing anything. This rewrites the rules. If that fails, check that .htaccess exists and is writable.

5. Stuck in maintenance mode

You see "Briefly unavailable for scheduled maintenance. Check back in a minute." long after an update. This happens when an update is interrupted, for example by a slow connection or power cut, which is not unusual during load shedding.

Fix: in File Manager, delete the file called .maintenance in your main WordPress folder. Then log in and rerun any updates that did not finish.

6. Memory exhausted error

The message reads "Allowed memory size of X bytes exhausted". A plugin or process needs more PHP memory than is allowed.

• Add define('WP_MEMORY_LIMIT', '256M'); to wp-config.php above the line that says "That's all, stop editing".
• In cPanel, use Select PHP Version or MultiPHP INI Editor to raise memory_limit.
• If your plan has a hard cap, ask your host whether an upgrade is needed, or find the heavy plugin and replace it.

7. Login page keeps refreshing or redirecting

You enter your details and the login page simply reloads. Causes include cookies, a wrong site URL, or a security plugin.

1. Clear your browser cookies and cache, or try a private window.
2. Check that the WordPress Address and Site Address are correct. You can force them by adding define('WP_HOME','https://yoursite.com'); and define('WP_SITEURL','https://yoursite.com'); to wp-config.php.
3. Rename your security or login plugin folder temporarily.

8. Mixed content and SSL warnings

After installing an SSL certificate, the padlock may not appear, or the browser shows "Not secure". This happens when some images or scripts still load over http.

Fix: update both site URLs to https in Settings, then General. Use a search and replace plugin to change old http links in the database, or a plugin like Really Simple SSL as a short term measure. Clear any caching plugin afterwards.

9. Image upload errors

"HTTP error" when uploading media usually comes from large image files, low memory, or folder permissions.

• Resize photos from your phone before uploading. Images straight from a modern phone can be several megabytes each.
• Check that the wp-content/uploads folder has permissions of 755.
• Raise upload_max_filesize and post_max_size in your PHP settings if needed.

10. Emails from forms not arriving

Contact form messages vanish, and customers think you are ignoring them. WordPress uses basic PHP mail by default, which is often filtered as spam.

Fix: install an SMTP plugin such as WP Mail SMTP and connect it to your business email account. Make sure your domain has correct SPF, DKIM and DMARC records so messages are trusted.

How to prevent WordPress errors

• Update WordPress core, themes and plugins regularly, but test big updates on a staging copy first.
• Remove plugins you no longer use.
• Only install plugins and themes from trusted sources. Avoid "nulled" premium themes, which often contain malware.
• Keep automatic daily backups and know how to restore one.
• Use a supported PHP version, and check that your plugins support it.
• Choose hosting with enough resources for your traffic.

Baasa Cloud's WordPress hosting includes daily backups, LiteSpeed caching and a support team in Uganda that can look at error logs with you when something breaks.

Frequently asked questions

Will fixing these errors delete my content?

No. Renaming plugin folders or replacing .htaccess does not touch your posts or pages, which live in the database. That is still why a backup comes first.

How do I turn on debugging?

In wp-config.php set WP_DEBUG to true and add WP_DEBUG_LOG set to true. Errors will be saved to wp-content/debug.log. Turn it off once you are done, as the log can reveal sensitive details.

When should I call a developer?

If your site shows strange redirects, unknown admin users, or spam links, you may have been hacked. That needs a proper cleanup rather than a quick fix.

Conclusion

Most WordPress errors look scary but come down to a handful of causes: a plugin conflict, a broken .htaccess file, wrong database details, or tight server limits. Work through the steps calmly, change one thing at a time, and always keep a backup ready. If you would rather have experts handle it, our team at Baasa Cloud can help you get your site back online.