Website Vidya
Web ServersStep-by-Step Guide

How to Fix Error 520: Web Server Is Returning an Unknown Error

How to Fix Error 520? It's a frustrating and complex error code. It indicates that the web page is not reachable. There could be several reasons behind this error code 520. This article covers, what this error code means, why it occurs and ...

RR
Rajesh RayLead Systems Educator
Published:
9 min read
How to Fix Error 520: Web Server Is Returning an Unknown Error
AI Executive SummaryCORE CIS AI

9 min read

How to Fix Error 520? It's a frustrating and complex error code. It indicates that the web page is not reachable. There could be several reasons behind this error code 520. This article covers, what this error code means, why it occurs and ...

Key Highlights
  • Common Causes of WordPress White Screen of Death Error in WordPress
  • How to Fix WordPress White Screen of Death Error - 6 Simple Ways
  • Plugin Issues
Grounded in full engineering runbookCORE CIS Ai Engine

The "White Screen of Death" (WSOD) is a common and frustrating issue that WordPress users may encounter. When this error occurs, the entire screen turns white, and users are left wondering what went wrong. The WSOD error can be caused by a variety of issues, ranging from plugin conflicts to server problems.

In this article, we will explore the common causes and learn how to fix WordPress white screen of death error.

Common Causes of WordPress White Screen of Death Error in WordPress

The White Screen of Death (WSOD) error can be attributed to various factors, with the following issues being key culprits:

Incompatible or Poorly-Coded Plugins and Themes: The WSOD Error often arises from plugins or themes that are incompatible or poorly coded. Conflicts between these components or with WordPress core files can disrupt the rendering process, resulting in a blank screen.

Advertisement

PHP Memory Exhaustion: WordPress relies on PHP scripts, each requiring a specific amount of memory to execute. If resource-intensive plugins, themes, or custom code exceed the website's memory limit, the PHP script may fail, leading to the WSOD Error.

Corrupted Core Files: Core files can become corrupted due to failed updates, malware infections, or incorrect manual modifications. Damaged essential files compromise the site's functionality, triggering the WSOD.

PHP Errors and Syntax Issues: Coding errors in PHP, such as syntax issues, missing semicolons, or incorrect function calls within themes, plugins, or custom code snippets, can cause script failure, resulting in a blank screen.

Exhausted Server Resources: Insufficient server resources, including CPU, memory, or disk space, can lead to the WSOD. Inadequate resources hinder the server's ability to process and serve the WordPress site effectively.

Failed Automatic Updates: Incomplete automatic updates of WordPress core, plugins, or themes can introduce inconsistencies in the codebase, triggering the WSOD Error.

Advertisement

Security Plugins and Settings: Overly aggressive security plugins or restrictive server settings may unintentionally block essential WordPress files, leading to the WSOD Error.

Database Issues: Problems with the WordPress database, such as corruption or connection errors, can disrupt site functionality, resulting in a blank screen.

Redirect Loops and URL Structure Errors: Incorrectly configured redirects or faulty permalink settings can create loops, preventing page loading and causing the WSOD Error.

File Permission Problems: Incorrect file permissions may prevent WordPress from accessing necessary files for rendering pages, triggering the WSOD Error.

Browser and Cache Issues: The WSOD can sometimes be caused by browser cache problems or server/plugin cache issues. Clearing the browser cache and purging server or plugin caches may resolve the issue.

Advertisement

How to Fix WordPress White Screen of Death Error - 6 Simple Ways

1. Plugin Issues

One of the most frequent causes of the WSOD error is a conflict with a WordPress plugin. If a recently installed or updated plugin is incompatible with your WordPress version or conflicts with other plugins, it can result in a white screen. To identify the problematic plugin, you can use the following steps:

  • Access your WordPress directory via FTP or file manager.
  • Navigate to the wp-content folder and then to plugins.
  • Temporarily rename the "plugins" folder to something like "plugins_backup".

This action will deactivate all plugins, allowing you to log in to your WordPress dashboard. Reactivate each plugin one by one to identify the problematic one.

2. Theme Issues

A poorly coded or incompatible theme can also lead to the White Screen of Death. To check if the theme is causing the issue, follow these steps:

  • Access your WordPress directory via FTP or file manager.
  • Navigate to the wp-content folder and then to themes.
  • Rename your active theme's folder to something else.

WordPress will automatically switch to the default theme, allowing you to determine if the theme was causing the problem.

3. PHP Memory Limit Exhaustion

If your WordPress site exhausts its allocated PHP memory limit, it can result in a WSOD error. To increase the memory limit, follow these steps:

Access your WordPress directory via FTP or file manager.

Locate the wp-config.php file and open it in a text editor.

Add the following line just before the "/* That's all, stop editing! */" line:

define('WP_MEMORY_LIMIT', '256M');

Adjust the memory limit value as needed, and save the file.

4. Issues with the .htaccess File

Corrupted or misconfigured .htaccess files can also trigger the WSOD error. To check this:

  • Access your WordPress directory via FTP or file manager.
  • Locate the .htaccess file and download it to your computer.
  • Replace the content of the file with the default WordPress .htaccess code.

Save the changes and upload the file back to your server.

5. Check the WordPress Error Logs

When modifying code in the WordPress backend, inadvertent typos in your source files can lead to issues. If you suspect this might be the root cause, examining the WordPress error log is crucial for pinpointing the problem. WordPress features a built-in debugging tool designed to assist in troubleshooting. Since this feature is disabled by default, follow the steps below to activate it:

1. Connect to your website using SFTP.

2. Navigate to the public_html folder.

3. Right-click on the wp-config.php file and select the View/Edit option.

4. Scroll to the file's bottom and insert the following line of code: define('WP_DEBUG', true); This instructs WordPress to log errors on your site.

5. Save the changes and revisit your website. While the white screen of death may persist, WordPress will log the error.

Once the debugger is active, access your error logs by following these steps:

1. Launch your SFTP client.

2. Open the public_html folder and then navigate to wp-content.

3. Locate and open the debug.log file using the View/Edit option.

4. At the file's bottom, review the last logged error.

If you can identify the problematic file, find it in your SFTP. If navigating your WordPress files is daunting, consider reaching out to your hosting provider. Provide them with a screenshot of your logged errors if you seek assistance without delving into the file structure personally.

6. Server Configuration Problems

In some cases, server-related issues such as PHP or database errors can cause the White Screen of Death. Check your server error logs for any clues about the problem. If necessary, contact your hosting provider for assistance.

Conclusion

The White Screen of Death error in WordPress can be a frustrating experience, but by systematically troubleshooting and identifying the root cause, you can resolve the issue and restore your website to normal functionality. Whether it's a plugin conflict, theme issue, memory limit, .htaccess problem, or server configuration, the steps outlined in this article should guide you through the process of fixing the WSOD error and getting your WordPress site back up and running.

RR
Written byVerified Author

Rajesh Ray

I’m Rajesh Rai, a full-stack developer, Linux administrator, and technology enthusiast passionate about making complex technology easier to understand and use.

SPAM-FREE MODERATED DISCOURSE

Join the Conversation & Perspective

Have thoughts, counterpoints, or reflections on this story? Engage directly with fellow readers and editorial contributors.

AT
MP
JV
+2

No comments on this guide yet. Be the first to share your thoughts or ask a question!

Recommended Reading10 Guides

Related Technical Guides

Tested runbooks, server administration walkthroughs, and troubleshooting guides

Web Servers•

How to Fix 400 Bad Request Error: 10 Easy Ways

Encountering an HTTP error can be frustrating, especially when the cause is unclear. One such error is the "400 Bad Request Error". This issue typically arises due to client-side problems, including incorrect syntax, invalid requests, or la...

RR
Rajesh Rai
Read More
Web Servers•

How to Install Nginx on CentOS 7: 4 Easy Steps

Nginx is a high performance web server software. Many big brands like Google, Facebook, Microsoft, Apple, Yahoo! and LinkedIn prefers Nginx over Apache and any other web server. And why not, it is the most flexible and lightweight web serve...

RR
Rajesh Rai
Read More
Web Servers•

How To Install NGINX on Ubuntu 18.04

Nginx is one of the most popular web servers. It is responsible for serving some of the largest websites and web apps on the internet. In this guide, we’ll discuss how to install Nginx on Ubuntu 18.04 server. How To Install NGINX on Ubuntu ...

RR
Rajesh Rai
Read More
Featured Infrastructure PartnerUp to 75% OFF + 3 Months Free

Supercharge Your Linux & Cloud Workloads with Hostinger

Deploy high-speed NVMe KVM VPS, Docker containers, and LiteSpeed-accelerated WordPress servers in under 60 seconds with full root access, dedicated IPv4, and 24/7 technical support.

Pure NVMe SSD StorageFull Root Access & SSHFree Domain & Unlimited SSL99.9% Uptime SLA
Plans from$2.99/mo
Claim Hostinger DealAffiliate link • Special discount applied at checkout