Your Site is Experiencing a Technical Issue

  • Resolved barnez

    (@pidengmor)


    5 years, 6 months ago

    Hi,

    I have a site running WordPress 5.2.1, NinjaFirewall 3.9.1. and PHP 7.2.17.
    This morning I received the following error by email:

    Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

    In this case, WordPress caught an error with one of your plugins, NinjaFirewall (WP Edition).

    First, visit your website (https://www.xxxx.com/) and check for any visible issues. Next, visit the page where the error was caught (https://www.xxxx.com/wp-admin/admin-post.php?Action=EWD_UFAQ_UpdateOptions) and check for any visible issues.

    The site seems to be functioning fine.
    Here are the error details:

    
=============
An error of type E_ERROR was caused in line 57 of the file /home/xxxxx/public_html/wp-content/plugins/ninjafirewall/lib/utils.php. Error message: Uncaught Exception: Could not gather sufficient random data in /home/xxxxx/public_html/wp-content/plugins/ninjafirewall/lib/utils.php:57
Stack trace:
#0 /home/xxxxx/public_html/wp-content/plugins/ninjafirewall/lib/utils.php(57): session_start()
#1 /home/xxxxx/public_html/wp-content/plugins/ninjafirewall/ninjafirewall.php(221): nfw_session_start()
#2 /home/xxxxx/public_html/wp-includes/class-wp-hook.php(286): nfw_admin_init('')
#3 /home/xxxxx/public_html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array)
#4 /home/xxxxx/public_html/wp-includes/plugin.php(465): WP_Hook->do_action(Array)
#5 /home/xxxxx/public_html/wp-admin/admin-post.php(30): do_action('admin_init')
#6 {main}

Next Exception: Could not gather sufficient random data in /home/xxxxx/public_html/wp-content/plugins/ninjafirewall/lib/utils.php:57
Stack trace:
#0 /home/xxxxx/public_html/wp-content/plugins/ninjafirewall/lib/utils.php(57): session_start()
#1 /home/xxxxx/public_html/wp-content/plugins/ninj

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author nintechnet

    (@nintechnet)

    Something wrong happened with your PHP interpreter when NF called the session_start() function. But the backtrace only shows the call to session_start() thus we’ll likely never know what really happened. As long as this is not a recurring problem, there’s nothing you need to do or change.

    Thread Starter barnez

    (@pidengmor)

    Thanks! That’s reassuring. I’ll keep an eye on it.

    Thread Starter barnez

    (@pidengmor)

    Hi,

    Just to update on this issue, I have received two more identical reports by email, one for this site and another from another site also running NF.

    I checked the firewall logs, for the minute when the email was generated and sent, and there are 2 x similar events logged regarding rule 1456 (WordPress vulnerability):

    Site 1:

    
06/Jun/19 21:05:38  #7416505  CRITICAL  1456  51.77.136.xxx    GET /wp-admin/admin-post.php - Unauthorized options change - [REQUEST:updated = true] - www.xxxxxx.com
06/Jun/19 21:05:52  #4073961  CRITICAL  1456  51.77.136.xxx    GET /wp-admin/admin-post.php - Unauthorized options change - [REQUEST:updated = true] - www.xxxxxx.com

    Site 2:

    
07/Jun/19 16:59:10  #5265752  CRITICAL  1445  217.182.193xxx   GET /wp-admin/admin-ajax.php - Unauthenticated action - [GET:swp_url = https://pastebin.com/raw/Da23nNZ9] - www.xxxxxx.es
07/Jun/19 16:59:11  #8822311  CRITICAL  1456  217.182.193xxx   GET /wp-admin/admin-post.php - Unauthorized options change - [REQUEST:updated = true] - www.xxxxxx.es
07/Jun/19 16:59:21  #1551268  CRITICAL  1456  217.182.193xxx   GET /wp-admin/admin-post.php - Unauthorized options change - [REQUEST:updated = true] - www.xxxxxx.es

    Is this a coincidence?

    Plugin Author nintechnet

    (@nintechnet)

    When those requests hit the admin-post.php, NF called session_start() and your PHP interpreter threw the error.
    This is an issue with your configuration. Make sure PHP is allowed to access (read) /dev/urandom as it seems it cannot. You can also verify the path with phpinfo() by searching the session.entropy_file directive.

    Thread Starter barnez

    (@pidengmor)

    Thanks for your advice. I have followed this up with the host. They say there are no corresponding errors logged in the error logs. They have enabled phpinfo() and there is no session.entropy_file directive. Also, they do not allow the ability of PHP to read /dev/urandom as the parameter which provides it is turned off for security reasons.

    It looks like my hands are tied and I may need to accept those occasional errors.

    Plugin Author nintechnet

    (@nintechnet)

    It is used to generate random bytes, that’s odd they block it. PHP may need it for instance for cryptographic purposes .

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Your Site is Experiencing a Technical Issue’ is closed to new replies.