nlpro

Hi @supervinnie41,

I have actually performed some tests (using a frontend login form rendered by the WordPress Core wp_login_form() function) and the test results confirm what I said in my previous post.

If you require no further assistance please mark this topic as ‘Resolved’.

Hi @benkimkenya,

There seems to be a problem with the creation of the 14 plugin tables in the database. Please check the server log files for any errors.

Alternatively log into a database administration tool, like phpMyAdmin, with the same database credentials as your WordPress site is using (you can find the credentials in the wp-config.php file) and then try and manually create a table. Perhaps the account lacks the necessary privileges to create tables.

+++ To prevent any confusion, I’m not SolidWP +++

Hi @vvedebariton,

According to the 9.3.5 Changelog:

Bug Fix: PHP warning about translations being loaded too early.

Please update the SolSec plugin to the 9.3.5 release and then confirm the notice has been fixed in your env. If so, please mark this topic as ‘Resolved’.

• This reply was modified 2 days, 17 hours ago by nlpro.

Hi @supervinnie41,

I may have been a little premature with my first response to your question. I think we need to distinguish between SolSec plugin login features that:

• affect the login form display
• affect the actual submit of the login form (authentication)
• affect both of the above

Usually the WordPress Core wp_login_form() function is used to display a frontend login form. A global (automated) search through the SolSec plugin code reveals that it hooks into none of the 4 filters included in this function!

So let me rephrase my previous response. If the plugin login feature is supposed to alter the display of the login form then you will probably not see the changes in the frontend login form. That said, if the plugin login feature is supposed to affect the authentication (submit of the login form) then the feature will probably work, provided that the standard WordPress login/authentication form action is executed. This seems to be the case with login forms rendered by the WordPress Core wp_login_form() function.

(Standard WordPress login/authentication form action = POST request of wp-login.php).

Furthermore I don’t think you need to worry about brute force attacks. These usually happen (automated) using the WordPress Core wp-login.php and/or xmlrpc.php files directly.

• This reply was modified 3 days, 23 hours ago by nlpro.

Hi @supervinnie41,

The features that affect login are applied on the backend login form.

+++ To prevent any confusion, I’m not SolidWP +++

Hi @vvedebariton,

Let’s start by saying this is a harmless notice, which will only surface when WP_DEBUG is set to true (in the wp-config.php file) and the Site Language is set to anything other than English (United States).

Reproduced instantly, so I guess it does need some attention from SolidWP.

The notice shows up in both, frontend and in the WordPress Dashboard (backend) of WordPress 6.7

+++ To prevent any confusion, I’m not SolidWP +++

• This reply was modified 1 week ago by nlpro.
• This reply was modified 1 week ago by nlpro.
• This reply was modified 1 week ago by nlpro.

Hi @cp_so,

According to the 9.3.4 Changelog:

Bug Fix: PHP warning on Site Health page.

Please update the SolSec plugin to the 9.3.4 release (remove the temporary workaround filter I recommended) and then confirm the issue has been fixed in your env. If so, please mark this topic as ‘Resolved’.

Hi @boabo,

According to the 9.3.4 Changelog:

Bug Fix: PHP warning in the SSL module on some server setups.

Please update the SolSec plugin to the 9.3.4 release and then confirm the issue has been fixed in your env. If so, please mark this topic as ‘Resolved’.

Hi @subwebsites,

The Pro plugin includes a history.txt file which contains the Changelog. It’s usually publicly available from the plugin root folder. Try this URL.

One caveat, SolidWP is currently not up to date with their Pro plugin on their site ?? They are still on the 8.1.0 (2023-11-14) release while 8.5.0 (2024-06-18) is the latest.

@shanedelierrr

Can you poke around at SolidWP to get the Pro plugin updated on the SolidWP site?

+++ To prevent any confusion, I’m not SolidWP +++

Hi @boriskrielen,

On the dashboard is says: “No data” in the exclusions and the bans overview graph.

This is actually as designed and good news. It means there have not been any recent lockouts or bans. I think the fact that you (probably) have the Hide Backend module enabled and the WordPress core XMLRPC feature disabled, contributes to this desireable result. It means your site is not currently suffering from automated brute force attacks.

If you would temporarily disable the Hide Backend module, it would make the WordPress login page accessible again. I (or anyone/bots) could then attempt a number of failed login attempts which would then lead to 1 or more (IP) lockouts. Ultimately banning the IP of the attacker. Once such brute force attempts occur on your site, you will start seeing the lockouts/bans data in the SolSec plugin Dashboard page. Trust me ??

Hi @rashidavc18,

Ok, let’s try a more direct route. Please add (temporarily) the lines below to the wp-config.php file (if not already):

define( 'WP_DISABLE_FATAL_ERROR_HANDLER', true );
ini_set("display_errors", true);
ini_set("error_reporting", E_ALL & ~E_STRICT & ~E_NOTICE & ~E_WARNING & ~E_DEPRECATED);

Then try and access the page(s) that does(do) not work. You should see one or more PHP warnings/errors. Update the topic with the warnings/errors displayed.

Don’t forget to undo the changes to the wp-config.php file afterwards!

• This reply was modified 2 weeks, 6 days ago by nlpro.

Hi?@rashidavc18,

If I’m not mistaken the email you received usually includes more info (like an?Error Details section). Can you share the info from the Error Details section?

+++ To prevent any confusion, I’m not SolidWP +++

Hi @luquerias,

Thanks you for the update.

If the errors persist after deactivating the SolSec plugin then clearly they are not caused by the SolSec plugin and AutomatorWP support should further assist in resolving these errors ??

Hi?@thenoxx,

If you require no further assistance, please mark this topic as ‘Resolved’.

+++ To prevent any confusion, I’m not SolidWP +++

Hi?@josflachs,

If you require no further assistance, please mark this topic as ‘Resolved’.

+++ To prevent any confusion, I’m not SolidWP +++