dwinden
Forum Replies Created
-
So find someone technical to do it for you.
The in my previous post provided procedure is not that complicated.dwinden
Happy to hear enabling the local brute force protection setting resolves the issue.
It was probably this entry from the 5.2.1 Changelog that caused the issue:
Bug Fix: Fixed warning that could occur on a failed login when Local Brute Force Detection is disabled.
dwinden
Is the Enable local brute force protection settings checkbox ticked in the Brute Force Protection section of the iTSec plugin Settings page ?
dwinden
Please note that since the 5.2.0 release (5.2.1 included) clicking on the One-Click Secure button in the First Important Steps modal window will not do anything despite the fact that it still reports:
Site Secured. Check the dashboard for further suggestions on securing your site.
which is also kind of lame as there is no longer a Security Status section on the Dashboard page …
Note this is not a bug, since iThemes knowingly removed the code that was normally executed behind this button …
Anyway I think it would have been better to completely remove the One-Click Secure button from the modal window …First time users of the plugin will think they are securing their site with one click while in fact absolutely nothing happens …
dwinden
Ok, before enabling the Scheduled Database Backups option again follow the procedure below.
In the Exclude Tables setting of the Database Backups section on the iTSec plugin Settings page make sure the:
[prefix]_itsec_temp,
[prefix]_itsec_lockouts,
[prefix]_itsec_logtables are excluded from the backup.
(Where [prefix] should be substituted with your database tables prefix).Next check for the presence of wp-content/uploads/ithemes-security/backup.lock folder. Delete the folder manually if it exists.
Now login to your database using phpMyAdmin and if necessary select your database.
To view your database structure, click the Structure tab at the top of your phpMyAdmin window. In the Structure window, you can view the table names, the number of records in each table, the size of each table etc.
Identify the table(s) with 10000s or 100000s records.
Exclude that (those) table(s) from the iTSec plugin Database Backup.Then try and create a backup manually. Click on the Create Database Backup button (it’s under the Backups tab). If the manual Database Backup completes successfully study the excluded tables. Ask yourself: what data is stored in that (those) table(s) ? Is there any point in including the data of those tables in a backup ? Can I delete all records from this (those) table(s)?
Often there are log tables holding many many many records of data which is useless.In other words try and reduce the database footprint(size) if possible.
Once you are confident the database footprint is minimized and a manual Database Backup works you can try and enable the Scheduled Database Backups setting again …
dwinden
If you require no further assistance please mark this topic as ‘resolved’.
(Bumping as sometimes new post emails are not send or received).dwinden
As the iThemes Security plugin does not include a CAPTCHA feature I think the best you can do is open a topic in the forum of the plugin that the CAPTCHA feature belongs to …
If you are using the reCAPTCHA feature of the iThemes Security Pro plugin please open a support ticket with iThemes here.
dwinden
@marcelo Pedra
From the iTSec Pro 2.1.5 history.txt file:
Bug Fix: Multiple activated installs of iThemes Security are now supported without fatal errors being generated on subsequent activations. Only one install will run at a time however.
This really needs some explanation. What is the benefit of all this ?
Is the last activated plugin the one running ?
So you can switch easily from one installed version to another or from
iTSec to iTSec Pro (and vice versa) ?dwinden
Happy to hear you were able to resolve the issue.
Please take a moment to share the solution with the community.dwinden
It seems the WP Dashboard login screen can be accessed using one of the 5 default WP login URLs. The other 4 result in a 404.
That is weird since you have enabled the iTSec plugin Hide Backend feature. None of the 5 default WP login URLs should work.
Only the secret WP Dashboard slug as specified in the Hide Backend feature should allow you to access the WP Dashboard login screen.Apart from that you still haven’t clarified what exact login issue you are having …
There may be a conflict with another plugin.
Are you using any other security plugin ?
Please list all the active plugins.dwinden