I have tried a fresh install of WordPress, no themes, and no-plugins and I am still getting this error. The web host (SiteGround) claims everything is working fine on their end.
It appears that if I provide a valid login email and password, the form functions fine. However, if I leave either fields blank or if I provide information that doesn’t match a valid login, then it throws the critical error.
I got the Exact same error and am also using the Ultimate Member plugin. namecheap is my hosting provider
Fatal error: Uncaught ArgumentCountError: Too few arguments to function siteground_xmlrpc_bruteforce_detector(), 1 passed in /home/customer/www/**************/public_html/wp-includes/class-wp-hook.php on line 287 and exactly 2 expected in /var/lib/sec/wp-settings.php:18 Stack trace: #0 /home/customer/www/**************/public_html/wp-includes/class-wp-hook.php(287): siteground_xmlrpc_bruteforce_detector(Object(WP_Error)) #1 /home/customer/www/**********/public_html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(”, Array) #2 /home/customer/www/************/public_html/wp-includes/plugin.php(484): WP_Hook->do_action(Array) #3 /home/customer/www/**************/public_html/wp-content/plugins/pagerestrict/pagerestrict.php(195): do_action(‘wp_login_failed’, Object(WP_Error)) #4 /home/customer/www/**************/public_html/wp-includes/class-wp-hook.php(287): pr_authenticate(Object(WP_Error), ‘**************’, ‘**************’) #5 /home/customer/www/************** in /var/lib/sec/wp-settings.php on line 18
I also just began having this problem today. Appears like my error code is nearly or exactly the same:
Fatal error: Uncaught ArgumentCountError: Too few arguments to function siteground_xmlrpc_bruteforce_detector(), 1 passed in /home/customer/www/domainname.com/public_html/wp-includes/class-wp-hook.php on line 287 and exactly 2 expected in /var/lib/sec/wp-settings.php:18 Stack trace: #0 /home/customer/www/domainname.com/public_html/wp-includes/class-wp-hook.php(287): siteground_xmlrpc_bruteforce_detector(‘info@beathallc….’) #1 /home/customer/www/domainname.com/public_html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array) #2 /home/customer/www/domainname.com/public_html/wp-includes/plugin.php(484): WP_Hook->do_action(Array) #3 /home/customer/www/domainname.com/public_html/wp-content/plugins/ultimate-member/includes/core/um-actions-login.php(78): do_action(‘wp_login_failed’, ‘info@useremail….’) #4 /home/customer/www/domainname.com/public_html/wp-includes/class-wp-hook.php(287): um_submit_form_errors_hook_login(Array) #5 /home/customer/www/domain in /var/lib/sec/wp-settings.php on line 18
I use SiteGround, and I notice they just uploaded an article about their customers not needing to worry about bruteforce due to their built-in protection….
Any help would be greatly appreciated.
Good to know I’m not the only one. Please let me know if you find a solution. I will share here as well if I come across anything.
From what I can tell, it seems like this message arises whenever an error message should be shown.
For example, if someone enters an incorrect password, they’d usually receive an error message stating so, but they’re directed to a page with this error instead.
Likewise, when any of the admins on my site try to login from the frontend, they usually get an error message stating they need to use a different page to enter in the 2FA code, but instead of getting that message they receive this error message.
BUT if admins login on the correct screen, or if users enter their correct password, then they receive the previously posted error message.
Hi @beacondigital, @dav3mexico – it looks like the issue is triggered with the Siteground plugin or modification to the core files. See the highlighted function below:
Fatal error: Uncaught ArgumentCountError: Too few arguments to function siteground_xmlrpc_bruteforce_detector(), 1 passed in /home/customer/www/**************/public_html/wp-includes/class-wp-hook.php on line 287 and exactly 2 expected in /var/lib/sec/wp-settings.php:18
I suggest that you contact Siteground support to assist you with this issue. UM doesn’t use any Siteground functions to that trigger this issue
Regards,
-
This reply was modified 5 years, 1 month ago by
Champ Camba.
Siteground had provided a hotfix for my site while they are fixing the root cause.
Add this to wp-config.php
/** Sets up WordPress vars and included files. */
require_once ABSPATH . ‘wp-settings.php’;
#@include_once(‘/var/lib/sec/wp-settings.php’); // Added by SiteGround WordPress management system
>> Note that they had commented out the original code auto-added by SG and replaced with an ABSPATH code instead.
I’m waiting on the finalization of the fix as we speak.
@mpiscoso Turns out my client is on Siteground , I will give your fix a try and I will open a ticket with Siteground
It appears that the fix might have been pushed out. Both my development site and my test site are no longer exhibiting this issue. Has anybody else found their login working properly this morning?
Mine is working and my ticket with SG reflected the same.
Hi Everyone,
Thanks for letting us know how you resolve the issue. I am closing this thread now.
Regards,
