chmod after install is complete

Hangin' Around Joined: May 28, 2006 Posts: 40

is it recommended to leave the htaccess to 644 after install is complete ?

if not where should it be chmoded too ?

Sells PC To Pay For Divorce Joined: Posts: 5661

you can leave it to that...

Posted: Mon Aug 07, 2006 2:23 am

sweet. thanks doood

registered · Worker Joined: Oct 07, 2003 Posts: 211

Can Sentinel still write to the .htaccess file if it is chmod to 644? I couldn't on my webserver.

Involved Joined: Jul 15, 2004 Posts: 252 Location: OKC, OK

Dauthus wrote:

Can Sentinel still write to the .htaccess file if it is chmod to 644? I couldn't on my webserver.

It depends on how the system is set up, some shared hosting plans will not work unless it is 666, the lower the better so try 644 first and then 666 if you have to.

registered · Posted: Tue Aug 08, 2006 1:24 pm

I agree with all that has been said, but just wanted to expound upon the concept so others will benefit from the "process". Start with the lowest and incrementally increase until it finally works.

Therefore, in this scenario, I would try 644 first (as others has suggested), then try 664, followed by 666.

Hangin' Around Joined: May 23, 2006 Posts: 40

Why does sentinel need to write to .htaccess ?

I ask this because I recently got a 505 Internal Server Error..
When I checked I found in the .htaccess that the most recent (and first in my case) hacker had been caught! To the ennd of the .htaccess file it added: deny from 216.145.5.42

The problem was that it added this to the end of the .htaccess file right behind a google tap script. So the script failed and the server refused to function.

Is there a work around for this? I dont want the server to get a 505 every time a hacker is caught.

Posted: Sun Aug 27, 2006 10:48 pm

Sentinel does not "need to write to .htaccess", but for most sites (where it does not cause a 500 error), it is a good thing because then that hacker's IP is banned at the web server level so that they never can get back to the site to try more things...

You have to leave a blank line at the bottom of your .htaccess file in order for Sentinel to write to it. Don't know what issue you are really having. I have google tap rewrite statements galore in my .htaccess along with many other little "tricks" and Sentinel can still write to it just fine.

If you do not wish for Sentinel to write to the .htaccess file, remove that option from each of your blockers (using the Blocker Configuration).

Posted: Sun Aug 27, 2006 11:44 pm

Ahh Thank You for the info.

Here was the error.

The last line in .htaccess was something like:

RewriteRule ^links.html links.html

and sentinel wrote to the .htaccess it saved as:

RewriteRule ^links.html links.html DENY FROM 216.145.5.42

It didnt index.

So I changed this to:

RewriteRule ^links.html links.html

#sentinel code
DENY FROM 216.145.5.42

Should that fix the error? Should it index correctly now? Or do I need to add a return under it so there is a blank line?

Thanks~~!!

Posted: Mon Aug 28, 2006 12:27 am

Just leave one blank line at the end. I.e., I believe hitting the carriage return after the .42 line should suffice.

Posted: Mon Aug 28, 2006 10:50 pm

Ok Great - Thanks!