{"id":5501,"date":"2026-10-19T14:03:32","date_gmt":"2026-10-19T12:03:32","guid":{"rendered":"https:\/\/peterteszary.com\/?post_type=sgkb-docs&#038;p=5501"},"modified":"2026-10-19T14:04:43","modified_gmt":"2026-10-19T12:04:43","slug":"mi-a-teendo-ha-szetesett-az-oldal-vagy-500-as-hibat-kapok","status":"publish","type":"sgkb-docs","link":"https:\/\/peterteszary.com\/en\/utmutato\/mi-a-teendo-ha-szetesett-az-oldal-vagy-500-as-hibat-kapok\/","title":{"rendered":"What should I do if the page has fallen apart or I get a 500 error?"},"content":{"rendered":"<p class=\"wp-block-paragraph\">There is no more daunting experience for a webshop owner or company manager than typing the company name address in the browser and a cold one instead of the expected design <em>\u2018500 Internal Server Error\u2019<\/em> message, or a completely white screen (the so-called \u201cWhite Screen of Death\u201d).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If this happens, the first impulse is most often panic. However, before writing in despair or stopping ads, it\u2019s a good idea to go through a quick, logical checklist. Often the problem can be identified in a few minutes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What Causes Error 500 or White Screen?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">An HTTP error of 500 means that something unexpected has occurred on the server, but the system does not know exactly what it is. The most common causes are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A code error for a freshly installed or updated plugin.<\/li>\n\n\n\n<li>PHP version is not compatible (e.g. your hosting is too old or too new for PHP).<\/li>\n\n\n\n<li>The available memory (Memory Limit) on the server is full.<\/li>\n\n\n\n<li>An incorrect line code in the individual files of the website (e.g. <code>functions.php<\/code>in ).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Step by step: Protocol for quick debugging<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If the page is broken, you can try the following steps to save it before seeking external help:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>1. Update cache (Cache \/ Hard Refresh)<\/strong> The error may have already been resolved, but your browser still shows the incorrect status. Push one <strong>Ctrl + F5<\/strong> (Windows) or <strong>Cmd + Shift + R<\/strong> (Mac) to reload the page completely. <em>[Screenshot location: Browser update button and keyboard shortcut icon]<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>2. Think about it: What happened in the last 10 minutes?<\/strong> Mistakes rarely happen on their own. Remember:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Have you just pressed an update in Control Panel?<\/li>\n\n\n\n<li>Have you just installed a new plugin?<\/li>\n\n\n\n<li>Did you just change anything in the code or settings? <em>If so, that element is most likely the cause of the system crash.<\/em><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>3. Access the Hosting interface<\/strong> If your website (<code>\/wp-admin<\/code>) is also unavailable, you cannot log in to the WordPress internal interface. In this case, you need to log in to your hosting provider\u2019s interface (e.g. CloudPanel, cPanel).<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>File Manager:<\/strong> Find your website folder in the <code>wp-content\/plugins<\/code> folder. If you just installed an extension, rename it (e.g. <code>woocommerce<\/code>about <code>woocommerce-OLD<\/code>). This will \u201cturn off\u201d the plugin for WordPress. If that makes the page come back, we've got the culprit! <em>[Screenshot location: File Manager of the hosting, highlighting the possibility of renaming the plugins folder]<\/em><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>4. Check the PHP version<\/strong> If your hosting has been updated to PHP (or changed by you), but an older plugin isn\u2019t compatible with it, it immediately throws an error of 500. Go to the hosting manager, find the <strong>PHP Settings \/ PHP Version<\/strong> menu and try to go back to a more stable version (e.g. from PHP 8.0 to 7.4, or vice versa, depending on the error phenomenon). <em>[Screenshot location: PHP version selection interface for hosting]<\/em><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">\ud83d\udca1 Pro Tip: Turn on Debugger (WP_DEBUG)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If you're more tech-savvy, you can ask your developer (or turn on the <code>wp-config.php<\/code> file) to activate debugging: <code>define( 'WP_DEBUG', true );<\/code> Instead of the white screen, the system will display exactly which line of the file the error is in. This is an immediate compass for the developer to repair.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">You're not making it? Stop experimenting with files.<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">When it comes to a WooCommerce webshop, file deletion or folder modification in the blind can do more harm than good.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the page hasn't recovered with the steps above, don't waste your precious time: open an SOS ticket in the <strong>peterteszary.com Error ticket<\/strong> , attach a screenshot of error 500 and I will fix the problem from the background as a matter of urgency!<\/p>","protected":false},"excerpt":{"rendered":"<p>Instead of the expected design, you will be greeted with a cold \u201c500 Internal Server Error\u201d message or a completely white screen (the so-called \u201cWhite Screen of Death\u201d).<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"slim_seo":{"title":"Mi a teend\u0151, ha sz\u00e9tesett az oldal vagy 500-as hib\u00e1t kapok? - peterteszary.com","description":"A v\u00e1rt diz\u00e1jn helyett egy rideg \"500 Internal Server Error\" \u00fczenet, vagy egy teljesen feh\u00e9r k\u00e9perny\u0151 (az \u00fagynevezett \"White Screen of Death\") fogadja."},"_slim_seo_primary_term_sgkb-docs-category":590,"_slim_seo_primary_term_sgkb-docs-tag":593,"footnotes":""},"sgkb-docs-category":[590],"sgkb-docs-tag":[593],"class_list":["post-5501","sgkb-docs","type-sgkb-docs","status-publish","hentry","sgkb-docs-category-hibaelharitas-troubleshooting","sgkb-docs-tag-hibajelensegek"],"meta_box":[],"_links":{"self":[{"href":"https:\/\/peterteszary.com\/en\/wp-json\/wp\/v2\/sgkb-docs\/5501","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/peterteszary.com\/en\/wp-json\/wp\/v2\/sgkb-docs"}],"about":[{"href":"https:\/\/peterteszary.com\/en\/wp-json\/wp\/v2\/types\/sgkb-docs"}],"author":[{"embeddable":true,"href":"https:\/\/peterteszary.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/peterteszary.com\/en\/wp-json\/wp\/v2\/comments?post=5501"}],"version-history":[{"count":2,"href":"https:\/\/peterteszary.com\/en\/wp-json\/wp\/v2\/sgkb-docs\/5501\/revisions"}],"predecessor-version":[{"id":5503,"href":"https:\/\/peterteszary.com\/en\/wp-json\/wp\/v2\/sgkb-docs\/5501\/revisions\/5503"}],"wp:attachment":[{"href":"https:\/\/peterteszary.com\/en\/wp-json\/wp\/v2\/media?parent=5501"}],"wp:term":[{"taxonomy":"sgkb-docs-category","embeddable":true,"href":"https:\/\/peterteszary.com\/en\/wp-json\/wp\/v2\/sgkb-docs-category?post=5501"},{"taxonomy":"sgkb-docs-tag","embeddable":true,"href":"https:\/\/peterteszary.com\/en\/wp-json\/wp\/v2\/sgkb-docs-tag?post=5501"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}