Internal Server Error on Activation

  • Resolved Alice Farrelly

    (@alicemaywebdesign)


    7 years, 9 months ago

    When I activate the plugin and log out again there is an “Internal Server Error” across the whole site when I try to log back in.

    If I remotely deactivate the plugin (using ManageWP) it still has the error until I delete the plugin.

    The path to “wordfence-waf.php” seems to be correct.

    When I activate Debug it shows this in the log:

    [02-Jun-2017 04:06:49 UTC] PHP Notice: Undefined index: hook_suffix in /home/lovedal1/public_html/wp-admin/includes/class-wp-screen.php on line 229

    The line it references is:

    $id = $GLOBALS['hook_suffix'];

    Any help is appreciated.

    Thanks in advance,

    Alice

    Site – https://www.lovedaleweddingchapel.com.au/

    Error
    Internal Server Error

    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Please contact the server administrator, [email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

    More information about this error may be available in the server error log.

    Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

Viewing 5 replies - 1 through 5 (of 5 total)

  • Hi Alice,
    I doubt this notice could cause this “internal server error”, wasn’t there any “fatal” error in the debug.log at the same time when you got this “internal server error”? or even in the server log files (you can check different error log files location from “Wordfence > Tools => Diagnostics => Log Files”) or simply ask your hosting provider.

    Also, do you get this error only after you log out?

    Thanks.

    Thread Starter Alice Farrelly

    (@alicemaywebdesign)

    Hi,

    The only think I could find was when I tried “Test your WordPress host’s available memory” it was having a fatal error so I decreased the amount of memory Wordfence should request when scanning. It now successfully passes the test. I have not had any more errors in the logs since but still get the Internal Server Error.

    If I do not log out I can keep doing things on the website. When I use an incognito window I can access the website until I try to log in on that window again. The Live Traffic actually says I am logging in successfully. It is like it has to do with logging in not out.

    Thanks,

    Alice

    Thread Starter Alice Farrelly

    (@alicemaywebdesign)

    @wfalaa – I did get those couple memory fatal errors when I did the tests but it has gone back to saying that there is an undefined index. I don’t understand why.

    [06-Jun-2017 23:33:48 UTC] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 47710209 bytes) in /home/lovedal1/public_html/wp-content/plugins/wordfence/lib/wordfenceClass.php on line 4445
[07-Jun-2017 00:49:55 UTC] PHP Notice:  Undefined index: hook_suffix in /home/lovedal1/public_html/wp-admin/includes/class-wp-screen.php on line 229

    Hi Alice,
    For the fatal error relate to the memory limit, you can increase the “WP_MEMORY_LIMIT” in wp-config.php file according to this guide. (try something like 256M).

    The other PHP notice, it could be related to other plugins? I suggest disabling other plugins (except Wordfence) and re-check this issue, also I recommend upgrading PHP version installed on your server, right now it seems that you are running PHP 5.3.29, which is an old release (2014), we recommend using at least version 5.6 and WordPress recommends using version 7 or newer.

    Thanks.

    Thread Starter Alice Farrelly

    (@alicemaywebdesign)

    Thanks @wfalaa. I upgraded the PHP to 5.6 (7 would not work) and it seems to be working now. I don’t normally use this host so I had not had the problem before.

    My memory limit seems to be set in wp-constants not in wp-config but I think I have updated it now.

    Thanks,

    Alice

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Internal Server Error on Activation’ is closed to new replies.