Title: Internal Server Error after scan Last modified: April 7, 2021 --- # Internal Server Error after scan * Resolved [aisyahznl](https://wordpress.org/support/users/aisyahznl/) * (@aisyahznl) * [5 years, 2 months ago](https://wordpress.org/support/topic/internal-server-error-after-scan/) * Hello, after running the wordfence scan, my site is down. I’m unable to view anything at all. What I have tried 1) renaming the plugins folder 2) renaming the wflogs 3) clear cache * i’m not sure where else to look since i cant access my site at all. * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Finternal-server-error-after-scan%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 6 replies - 1 through 6 (of 6 total) * [Sunborn](https://wordpress.org/support/users/sunborn/) * (@sunborn) * [5 years, 2 months ago](https://wordpress.org/support/topic/internal-server-error-after-scan/#post-14286850) * You need to go to your web hosting control panel (NOT the wordpress admin panel), then go to PHP setting and temporarily enable the ‘display errors’ option. Then, refresh your website home page and you will see in your screen what it causes the error. Copy and paste the results here, so you can easily get help from someone here 🙂 * Plugin Support [wfphil](https://wordpress.org/support/users/wfphil/) * (@wfphil) * [5 years, 2 months ago](https://wordpress.org/support/topic/internal-server-error-after-scan/#post-14292515) * Hi [@aisyahznl](https://wordpress.org/support/users/aisyahznl/) * If you renamed the Wordfence plugin directory name then Wordfence cannot be the cause of your site being down as Wordfence will be inactive. * Do not follow the advice given by [@sunborn](https://wordpress.org/support/users/sunborn/) because the **_display\_errors_** PHP directive should never be enabled on a production website connected to the internet. You can see this in the PHP documentation here: * [https://www.php.net/manual/en/errorfunc.configuration.php#ini.display-errors](https://www.php.net/manual/en/errorfunc.configuration.php#ini.display-errors) * You will need to ask your hosting provider for assistance as they can look at the PHP error logs (if PHP error logging is enabled), the web server error logs and other error logs to see why the site went down. * [Sunborn](https://wordpress.org/support/users/sunborn/) * (@sunborn) * [5 years, 2 months ago](https://wordpress.org/support/topic/internal-server-error-after-scan/#post-14292999) * this is very true, however i meant temporary, just for 1 minute so she can see the code… is not a big harm, after all, as you can see, it is an empty site… 🙂 * this is how i fix a similar bug on one of my websites too just a week ago: * i suddenly had a blank home page (and wp-admin page too!) with an HTTP ERROR 500… so, i ask the hosting team what is going one and they told me to delete the worldfence folder and then install it again! * …and i said, why on earth i should do such thing? * so, i activate the display errors just for 30 seconds, and i see the message: * `Fatal error: Uncaught Error: Failed opening required '/home/u662469818/public_html/ wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/parser/lexer.php'( include_path='.:/opt/alt/php80/usr/share/pear:/opt/alt/php80/usr/share/php:/usr/ share/pear:/usr/share/php') in /home/u662469818/public_html/wp-content/plugins/ wordfence/vendor/wordfence/wf-waf/src/init.php:30 Stack trace: #0 /home/u662469818/ public_html/wp-content/plugins/wordfence/waf/bootstrap.php(31): require_once()# 1 /home/u662469818/public_html/wordfence-waf.php(6): include_once('/home/u66246981...')# 2 {main} thrown in /home/u662469818/public_html/wp-content/plugins/wordfence/ vendor/wordfence/wf-waf/src/init.php on line 30` * so, by simple logic, i check the folder and i saw that lexer.php was missing! * then, i simply download manually the worldfence.zip, extract it on my PC, and then just upload the lexer.php in the right directory * Problem solved, site was instantly back, no need to wait for supposed tech advice, which was totally destructive! (they couldn’t even tell me for sure what will happened with the 2 factor authentication, if i delete the folder!) * Plugin Support [wfphil](https://wordpress.org/support/users/wfphil/) * (@wfphil) * [5 years, 2 months ago](https://wordpress.org/support/topic/internal-server-error-after-scan/#post-14297618) * Hi [@sunborn](https://wordpress.org/support/users/sunborn/) * Thank for the additional information as that explains the situation fully. * Your absolute file path should never be disclosed publicly so you can edit your reply so that it looks something like this **_/home/xxxxx/public\_html/_**. * It is better to use PHP error logging that records all error logs in a file rather than enabling the displaying of PHP errors. Your hosting provider can help you setup PHP error logging if it isn’t enabled, or you can setup WordPress debugging as outlined below: * > [Debugging in WordPress](https://wordpress.org/support/article/debugging-in-wordpress/) * The missing file may possibly have been due to a failed update of the plugin. You can disable the option to update Wordfence automatically. This option can be found in the **_General Wordfence Options_** section on the **_All Options_** page. * If you have the email alert option **_Alert me with scan results of this severity level or greater_** set to at least **_Medium_** then you will receive an alert when a new version of Wordfence is available to install from the WordPress ** _Plugins_** page. * If a manual update fails too then you can delete the plugin manually and try and reinstall it again. This allows you to deal with the situation immediately rather than the auto update failing and you not being aware of the issue until a later point in time. * If you delete the Wordfence plugin directory then it won’t affect any of your settings such as two factor authentication as that is stored in the database. * [Sunborn](https://wordpress.org/support/users/sunborn/) * (@sunborn) * [5 years, 2 months ago](https://wordpress.org/support/topic/internal-server-error-after-scan/#post-14297738) * [@wfphil](https://wordpress.org/support/users/wfphil/) thank you 🙂 * that is very true about “/home/xxxxx/public_html/”!, it happened because because i am a multitask person and sometimes i can forget basic things, in order to do everything fast :-p …however i can not find an option to edit the post! Is it somewhere on my main WordPress profile? I can see the “Edit” link, only in on my latest reply, not everywhere! * also, thanks a lot for confirmation that deleting the Wordfence plugin directory it won’t affect any of my settings such as two factor authentication! - This reply was modified 5 years, 2 months ago by [Sunborn](https://wordpress.org/support/users/sunborn/). * Plugin Support [wfphil](https://wordpress.org/support/users/wfphil/) * (@wfphil) * [5 years, 2 months ago](https://wordpress.org/support/topic/internal-server-error-after-scan/#post-14297879) * Hi [@sunborn](https://wordpress.org/support/users/sunborn/) * I recall now that posts can only be edited for 60 minutes. You could join WordPress Slack and ask a moderator for assistance: * > [Slack](https://make.wordpress.org/chat/) Viewing 6 replies - 1 through 6 (of 6 total) The topic ‘Internal Server Error after scan’ is closed to new replies. * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865) * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/) * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq) * [Support Threads](https://wordpress.org/support/plugin/wordfence/) * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/) ## Tags * ["internal server error"](https://wordpress.org/support/topic-tag/internal-server-error/) * 6 replies * 3 participants * Last reply from: [wfphil](https://wordpress.org/support/users/wfphil/) * Last activity: [5 years, 2 months ago](https://wordpress.org/support/topic/internal-server-error-after-scan/#post-14297879) * Status: resolved