Blocked from my site by Sentinel

registered · Hangin' Around Joined: Sep 25, 2005 Posts: 48

I can't access my site anymore?!

I get this message:

Quote:

You have been blocked from entering this site.

You are using a possible Harvester on this site.

All of the following information has been gathered to assist the webmaster should this need to be reported to local or federal law enforcement.

If you think this is a mistake you can contact the site webmaster at webmaster(at)shimshon9(dot)com.

User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Remote Address: 84.108.29.86
Client IP: none
Forwarded For: none
Date Blocked: 2006-12-01 @ 08:03:59 PST GMT -0800
Block expires: Permanent

What can I do?
Thanks.

Posted: Fri Dec 01, 2006 10:36 am

Remove your IP address from your .htaccess file and also from your database. Then add your IP address to the protected ranges in Sentinel, this should stop you from getting banned again.

Posted: Fri Dec 01, 2006 12:50 pm

Thanks,
but I can't find my IP in the .htaccess.
How do I find it in the DB?

Posted: Fri Dec 01, 2006 12:54 pm

OK, I found it in the DB.
Everything works again.
Thanks So much!

Posted: Sat Dec 02, 2006 7:25 am

Glad it is working for you. You must not have it setup in Sentinel to write banned ips to your htaccess, so that is why it didn't show up there. Smile

Client Joined: Jan 29, 2004 Posts: 624

jakec wrote:

Remove your IP address from your .htaccess file and also from your database. Then add your IP address to the protected ranges in Sentinel, this should stop you from getting banned again.

I've done that, over and over... remove my IP from .htaccess and from nsnst_blocked_ips in phpmyadmin... then I go back to my admin, click on a link any link, Blocks, Modules, Nukesentinel, and bing I'm banned again and off I trot to phpmyadmin and .htaccess to deban my IP again. What the hell is going on? How do I find the ip lo and ip hi #s for my IP so I can put the sucker in nsnst_protected_ranges? Would an allow from my IP range do it in .htaccess? I am supposed to be 'protected' as the God admin in NS, why am I getting banned? I cleared my cookies and cache and logged back into 'my' admin and bing I got banned again.

Posted: Fri Mar 23, 2007 8:53 am

FireATST wrote:

Glad it is working for you. You must not have it setup in Sentinel to write banned ips to your htaccess, so that is why it didn't show up there. Smile

Oh but I did hehe and I am getting written in my own .htaccess.

Posted: Fri Mar 23, 2007 9:36 am

Well... I tried an 'allow from xxx.xx.xxx.xxx/x' (my IP range) in .htaccess and went off to my admin, I clicked Content OK, clicked Nukesentinel OK, clicked Protected Range bing I got banned... this time my full IP not xxx.xx.xxx.* like before. A small improvement Cheers

but I'm still banned from 'my' site. Could this have anything to do with localhost?
http://www.ravenphpscripts.com/postt7780.html
I upgraded to NS 2.5.07 yesterday.

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

When you did your upgrade, did you [re]import the new IP2COUNTRY table through NS Admin screen.

Posted: Sat Mar 24, 2007 3:21 pm

No, I did the IP2Country through RavenNuke 2.10 installsql.php, then upgraded Nukesentinel from the install version 2.5.06 back to 2.5.07. I doubt IP2Country was the problem, I think getting my IP banned resulted from putting rnconfig.php in my .htaccess with a deny from all, I removed it from .htaccess and I don't get banned from my admin now. I guess I assumed rnconfig should be in .htaccess like config.php. Live and learn...

Posted: Sat Mar 24, 2007 3:41 pm

You can only deny from all if the file is never directly called. deny from all files can be included/required, assuming the permissions allow read access. I wasn't aware that we were directly calling rnconfig so I will have to look into that one.

registered · Posted: Sat Mar 24, 2007 7:08 pm

I am confused. Here is how we are bringing in rnconfig.php:

require_once(NUKE_BASE_DIR.'rnconfig.php');

Posted: Sat Mar 24, 2007 9:20 pm

So try it yourself, put rnconfig in your .htaccess and see if you get banned from your admin. I need some replication. Smile

Posted: Sun Mar 25, 2007 8:38 am

southern wrote:

I guess I assumed rnconfig should be in .htaccess like config.php. Live and learn...

First of all, I have never done this and in all my years now working with PHP-Nuke, I have never even heard of doing this. These two scripts can be "called" directly from a web browser and expose absolutely nothing back, so there is NO value in trying to do what you are doing.

Just leave them out of .htaccess and then all is right with the world? (At least that is what the rest of that post implies to me.)

Posted: Sun Mar 25, 2007 11:07 am

If Apache is not configured correctly, as often times it is not with those unfamiliar with Apache configuration, your *.php files will be shown in the browser. I, personally, have seen this on new sites. *.php files are not, automatically, defined to Apache. So, this may not be needed for experience users, but it is another layer of security. Better safe than sorry Wink

Posted: Sun Mar 25, 2007 3:01 pm

montego wrote:

First of all, I have never done this and in all my years now working with PHP-Nuke, I have never even heard of doing this. These two scripts can be "called" directly from a web browser and expose absolutely nothing back, so there is NO value in trying to do what you are doing.

Just leave them out of .htaccess and then all is right with the world? (At least that is what the rest of that post implies to me.)

As you wish, I yield to your experience. I was not implying that leaving config.php and other configuration files out of .htaccess would render all right with the world- are you a lawyer? I just wanted to know if anyone else would get banned from their admin by putting rnconfig in .htaccess but never mind. Smile

Posted: Sun Mar 25, 2007 3:07 pm

Raven wrote:

If Apache is not configured correctly, as often times it is not with those unfamiliar with Apache configuration, your *.php files will be shown in the browser. I, personally, have seen this on new sites. *.php files are not, automatically, defined to Apache. So, this may not be needed for experience users, but it is another layer of security. Better safe than sorry Wink

Well I just saw it a post a long time ago somewhere on securing config.php and I left it in .htaccess without thinking much about it, but since I know my webhost configures Apache right...

Posted: Sun Mar 25, 2007 3:52 pm

The life of a Host or close to it. I left out the part about stupid user tricks ROTFL

Posted: Sun Mar 25, 2007 6:39 pm

Oh well time to move on anyway.