Count Block Errors After Upgrade To 2.1.3

Posted: Mon Jan 10, 2005 8:58 am

Hi

In the past 24 hours I have had over 300 attempts to intrude into my site, yet my count block has remained at 170 since updating to 2.1.3.

It seems both hackers beware blocks are not increasing in count.

Next, IPs are also now not making it into the .htaccess file, where in all previous versions this worked fine.

I did an incremental in place upgrade from 2.1.1 to 2.1.3 and got no error messages during the process, but it appears as though NukeSentinel is simply email notifying me about intrusion attempts, and though set to email, block and forward, it appears as though the only thing that is really working is me getting the emails.

Any ideas?

registered · Posted: Tue Jan 11, 2005 11:00 am

Did you upload the new files or just compare and update the files?

Posted: Tue Jan 11, 2005 11:06 am

Uploaded all new files and ran installer.

Posted: Wed Jan 12, 2005 10:54 am

I ended up having to uninstall NukeSentinel again and re-install.

Upon completion of that process, I found that my NukeSentinel menus identify the version as 2.1.2 instead of 2.1.3.

Is something awry?

Thanks
Steph

Client Joined: Apr 10, 2004 Posts: 649 Location: UK

Mine say 2.1.2 as well after I'd uninstalled Sentinel 2.1.0 and did a fresh install of Sentinel 2.1.3

Posted: Thu Jan 27, 2005 9:49 am

run the following query from phpMyAdmin:

Code:

UPDATE `nuke_nsnst_config` SET `config_value` = '2.1.3' WHERE `config_name` = 'version_number' LIMIT 1 ;