{"id":8051,"date":"2026-05-08T14:04:25","date_gmt":"2026-05-08T12:04:25","guid":{"rendered":"https:\/\/mybox.com\/help\/?post_type=manual_kb&#038;p=8051"},"modified":"2026-06-08T09:49:22","modified_gmt":"2026-06-08T07:49:22","slug":"ecranul-alb-al-mortii-wsod-in-wordpress-cauze-si-remedieri","status":"publish","type":"manual_kb","link":"https:\/\/mybox.com\/help\/ro\/knowledgebase\/white-screen-of-death-wsod-in-wordpress-causes-and-fixes\/","title":{"rendered":"Ecranul alb al mor\u021bii (WSoD) \u00een WordPress - Cauze \u0219i remedieri"},"content":{"rendered":"<div class=\"translation-block translation-block-merged\">\n<p class=\"wp-block-paragraph\">The &#8220;White Screen of Death&#8221; is one of the most common yet alarming WordPress issues. It occurs when your website displays a completely blank page with no error message, effectively locking you out of both the front end and the dashboard. This typically happens when a script on your <strong>mybox-hosted<\/strong> server times out or encounters a fatal error.<\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_86 ez-toc-wrap-left counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1' ><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/white-screen-of-death-wsod-in-wordpress-causes-and-fixes\/#Common_Causes_of_the_White_Screen\" >Common Causes of the White Screen<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/white-screen-of-death-wsod-in-wordpress-causes-and-fixes\/#Step_1_Enable_WordPress_Debug_Mode\" >Step 1: Enable WordPress Debug Mode<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/white-screen-of-death-wsod-in-wordpress-causes-and-fixes\/#Step_2_Deactivate_All_Plugins\" >Step 2: Deactivate All Plugins<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/white-screen-of-death-wsod-in-wordpress-causes-and-fixes\/#Step_3_Switch_to_a_Default_Theme\" >Step 3: Switch to a Default Theme<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/white-screen-of-death-wsod-in-wordpress-causes-and-fixes\/#Step_4_Increase_the_PHP_Memory_Limit\" >Step 4: Increase the PHP Memory Limit<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/white-screen-of-death-wsod-in-wordpress-causes-and-fixes\/#Step_5_Check_for_Auto-Update_Failures\" >Step 5: Check for Auto-Update Failures<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/white-screen-of-death-wsod-in-wordpress-causes-and-fixes\/#Technical_Analysis_via_mybox_Logs\" >Technical Analysis via mybox Logs<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/white-screen-of-death-wsod-in-wordpress-causes-and-fixes\/#Summary\" >Summary<\/a><\/li><\/ul><\/nav><\/div>\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Common_Causes_of_the_White_Screen\"><\/span>Common Causes of the White Screen<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Plugin or Theme Conflicts:<\/strong> A recent update or a poorly coded plugin can crash the site.<\/li>\n\n\n\n<li><strong>Exhausted PHP Memory:<\/strong> Your site has reached the memory limit assigned to it.<\/li>\n\n\n\n<li><strong>Coding Errors:<\/strong> A small typo in a file like <code>functions.php<\/code> or <code>.htaccess<\/code>.<\/li>\n\n\n\n<li><strong>Database Issues:<\/strong> Corrupted tables or a failed connection to the database.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Step_1_Enable_WordPress_Debug_Mode\"><\/span>Step 1: Enable WordPress Debug Mode<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Since the white screen hides the actual error, you need to force WordPress to reveal what is going wrong.<\/p>\n\n\n\n<ol start=\"1\" class=\"wp-block-list\">\n<li>Connect to your FTP account via your preferred FTP client.<\/li>\n\n\n\n<li>Locate the <code>wp-config.php<\/code> file in your root directory.<\/li>\n\n\n\n<li>Search for the line: <code>define( 'WP_DEBUG', false );<\/code><\/li>\n\n\n\n<li>Change it to: <code>define( 'WP_DEBUG', true );<\/code><\/li>\n\n\n\n<li><strong>Save the file.<\/strong> Refresh your site. Instead of a white screen, you should now see a specific error message pointing to a specific file and line number.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Step_2_Deactivate_All_Plugins\"><\/span>Step 2: Deactivate All Plugins<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<\/div>\n\n<div id=\"mybox-1634351801\" class=\"mybox-content mybox-entity-placement\"><div class=\"early-access-banner-inpost\">\r\n  <div class=\"banner-left-inpost\">\r\n    <div class=\"icon-box-inpost\">\r\n      <img decoding=\"async\" src=\"https:\/\/mybox.com\/help\/wp-content\/uploads\/2026\/02\/square-info-icon.svg\" alt=\"Info\">\r\n    <\/div>\r\n    <div class=\"text-box-inpost\">\r\n      <span class=\"label-inpost\"><span class=\"translation-block translation-block-banner-text\">Acces timpuriu<\/span><\/span>\r\n      <h4><span class=\"translation-block translation-block-banner-text\">Mai ave\u021bi nevoie de ajutor?<\/span><\/h4>\r\n      <p><span class=\"translation-block translation-block-banner-text\">Contacta\u021bi echipa noastr\u0103 de servicii pentru clien\u021bi.<\/span><\/p>\r\n    <\/div>\r\n  <\/div>\r\n\r\n  <div class=\"banner-right-inpost\">\r\n    <a href=\"https:\/\/panel.mybox.com\/helpdesk2\/v\/list\/\" class=\"banner-button-inpost\"><span class=\"translation-block translation-block-banner-text\">Trimite mesaj<\/span><\/a>\r\n  <\/div>\r\n<\/div><\/div>\n\n<div class=\"translation-block translation-block-merged\"><p class=\"wp-block-paragraph\">If the debug message points to a plugin folder, or if you can&#8217;t access the debug log, deactivating plugins is the next logical step.<\/p>\n\n\n\n<ol start=\"1\" class=\"wp-block-list\">\n<li>Via FTP, go to <code>\/wp-content\/<\/code>.<\/li>\n\n\n\n<li>Rename the <code>plugins<\/code> folder to <code>plugins_old<\/code>.<\/li>\n\n\n\n<li>Check your site. If it loads, a plugin was the culprit.<\/li>\n\n\n\n<li>Rename the folder back to <code>plugins<\/code>, then log in to your dashboard and activate them one by one to find the specific one causing the crash.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Step_3_Switch_to_a_Default_Theme\"><\/span>Step 3: Switch to a Default Theme<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If plugins aren&#8217;t the issue, your theme might be.<\/p>\n\n\n\n<ol start=\"1\" class=\"wp-block-list\">\n<li>Using FTP, navigate to <code>\/wp-content\/themes\/<\/code>.<\/li>\n\n\n\n<li>Rename your active theme&#8217;s folder (e.g., <code>mytheme_old<\/code>).<\/li>\n\n\n\n<li>WordPress will automatically attempt to fall back to a default theme (like <em>Twenty Twenty-Four<\/em>). If the site comes back, you know the issue lies within your theme&#8217;s code.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Step_4_Increase_the_PHP_Memory_Limit\"><\/span>Step 4: Increase the PHP Memory Limit<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Sometimes the white screen happens because a process is simply too &#8220;heavy&#8221; for the default settings.<\/p>\n\n\n\n<ol start=\"1\" class=\"wp-block-list\">\n<li>In your <code>wp-config.php<\/code> file, add this line before the &#8220;Happy blogging&#8221; message: <code>define('WP_MEMORY_LIMIT', '256M');<\/code><\/li>\n\n\n\n<li>Additionally, you can adjust the PHP limits globally within your <strong>mybox panel<\/strong> under the <strong>PHP Settings<\/strong> section to ensure your environment has enough resources for your specific site requirements.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Step_5_Check_for_Auto-Update_Failures\"><\/span>Step 5: Check for Auto-Update Failures<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If the white screen appeared during an update, a <code>.maintenance<\/code> file might be stuck.<\/p>\n\n\n\n<ol start=\"1\" class=\"wp-block-list\">\n<li>Check your root folder via <strong>FTP<\/strong>.<\/li>\n\n\n\n<li>If you see a file named <code>.maintenance<\/code>, delete it.<\/li>\n\n\n\n<li>This often clears the &#8220;Briefly unavailable&#8221; or white screen issue immediately.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Technical_Analysis_via_mybox_Logs\"><\/span>Technical Analysis via mybox Logs<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If none of the above works, the <strong>mybox panel<\/strong> provides deeper insights:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Error Logs:<\/strong> Access the &#8220;Logs&#8221; section in your panel to see real-time server errors (500 errors). These often provide a more technical explanation than WordPress&#8217;s internal debug mode.<\/li>\n\n\n\n<li><strong>Restoring Backups:<\/strong> If you cannot find the source of the error, use the <strong>mybox<\/strong> backup tool to restore your site to a state from 24 or 48 hours ago when it was working perfectly.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Summary\"><\/span>Summary<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">While the White Screen of Death looks intimidating, it is almost always caused by a minor code conflict or a resource limit. By using the debug mode and the file management tools in your <strong>mybox panel<\/strong>, you can quickly identify the source and restore your site to full functionality.<\/p>\n<\/div>","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"template":"","format":"standard","manualknowledgebasecat":[58],"manual_kb_tag":[545,718,1603,2179,2940,2942,3476,3710,5110,8622,8623,8624,8625,8626,543],"class_list":["post-8051","manual_kb","type-manual_kb","status-publish","format-standard","hentry","manualknowledgebasecat-web-applications-cms","manual_kb_tag-wordpress-troubleshooting","manual_kb_tag-htaccess-file","manual_kb_tag-deactivate-plugins","manual_kb_tag-wordpress-config-file","manual_kb_tag-wordpress-debug-mode","manual_kb_tag-plugin-conflicts","manual_kb_tag-theme-conflicts","manual_kb_tag-functions-php-file","manual_kb_tag-memory-limit","manual_kb_tag-fatal-php-error","manual_kb_tag-coding-errors","manual_kb_tag-database-issues","manual_kb_tag-wordpress-white-screen","manual_kb_tag-default-theme","manual_kb_tag-white-screen-of-death"],"_links":{"self":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/8051","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb"}],"about":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/types\/manual_kb"}],"author":[{"embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":2,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/8051\/revisions"}],"predecessor-version":[{"id":8052,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/8051\/revisions\/8052"}],"wp:attachment":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/media?parent=8051"}],"wp:term":[{"taxonomy":"manualknowledgebasecat","embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manualknowledgebasecat?post=8051"},{"taxonomy":"manual_kb_tag","embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb_tag?post=8051"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}