phpnuke install on ispconfig

Hangin' Around Joined: Dec 04, 2005 Posts: 31

Fresh install of phpnuke 7.6.3.1 on suse 10 server using ispconfig.

I'm getting internal server error. Error log says .htaccess options not allowed here. As far as I can tell this is to do with httpd.conf AllowOverride. I have changed AllowOverride to All and restarted apache2 but still get the same error. Any suggestions?

Thx

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

There are usually at least 2 places that need to be changed to AllowOverride All. Make sure you have changed them all.

Posted: Sun Feb 26, 2006 11:04 pm

Yes that works. Started by changing all of them then just trial and errored them down to the one that did the trick. Thanks.

Posted: Sun Feb 26, 2006 11:20 pm

Posted: Mon Feb 27, 2006 2:55 am

So apparently there is still a problem. None of the site pages are displayed (pages are blank). There are no error messages in the log and display errors are on but none show up. I can view analyzer.php and phpinfo.php everything looks fine. Confused

Posted: Fri Mar 03, 2006 8:52 pm

At the risk of appearing a bit foolish... I remembered my php include path had been modified and once I corrected that everything worked wonderful.

Posted: Fri Mar 03, 2006 9:47 pm

Regular Joined: Mar 26, 2006 Posts: 87 Location: UK

I have a similar problem... /home/fhlinux203/j/my_domain/user/htdocs/nuke/.htaccess: Options not allowed here.

Is this something I can ask my webhosting service to rectify, or do I have to resign myself to not being able to use RavenNuke76? Sad

Thanks for any advice.

P.S. According to phpinfo, Server API = Apache.

Posted: Sun Mar 26, 2006 11:15 am

I have said this many, many, many times. You do NOT need .htaccess to run RavenNuke76, any more than you need .htaccess to run phpnuke. However, your host is being pretty short sided by not allowing you to use .htaccess.

Posted: Sun Mar 26, 2006 12:51 pm

Ok, not being able to find a suitable solution by searching, I decide to try renaming .htacces... PRESTO!!!

Posted: Sun Mar 26, 2006 1:42 pm

Quote:

Ok, not being able to find a suitable solution by searching, I decide to try renaming .htacces... PRESTO!!!

hmmm y not just delete it then..the .htaccess will serve no purpose then
sorry i wasnt clear ealier so i need to restate it..ravens right there is no need for either. renaming it makes it useless so y bother having it there.
but also id sudjest u go with a better host that is more capable or complete as raven would say it Laughing

Posted: Sun Mar 26, 2006 4:17 pm

As I said above, you don't need .htaccess nor .staccess if you can use Http Auth. You only have to have them for CGI Auth.

Posted: Sun Mar 26, 2006 6:49 pm

Thanks for you replies...

I am a total novice regarding Nuke and the like.

Knowing how experienced users frown upon those who run around squawking "IM A NOOB PLZ HELP", I first tried searching the forums for an answer. When I found another user with a similar problem, although I couldn't see the absolute solution, I thought it an appropriate place to ask for advice.

I have had a little experience producing a clumsy website using Frontpage, which I notice produces several .htaccess files without my webhost's server complaining about them.

So I didn't find this rant...

Raven wrote:

I have said this many, many, many times. You do NOT need .htaccess to run RavenNuke76, any more than you need .htaccess to run phpnuke. However, your host is being pretty short sided by not allowing you to use .htaccess.

... particularly helpful; as far as I knew one of Nuke's files might need changing to prevent it referencing .htaccess.

Thanks again.

Posted: Sun Mar 26, 2006 10:40 pm

Trust me, that is not even close to being a rant Wink

. It was just a statement of fact.

Posted: Sun Mar 26, 2006 11:23 pm

Perhaps a coment in the page Install RavenNuke76(tm) Tables To The Database of the installation guide could be added...

Quote:

That IS what you should see at this point. If you do not, then something has gone wrong. Retrace your steps and try again until your receive that message.

Also check you server's error.log; if you see something like "your_domain/user/htdocs/nuke/.htaccess: Options not allowed here", try renaming/deleting .htaccess as this file is not essential to installation.

I can't find a FAQ or sticky regarding deleting .htaccess. Wink

Posted: Sun Mar 26, 2006 11:50 pm

You never mentioned that this was a RavenNuke76 install. Nor is it in the RavenNuke76 forums. It is in the RN76 documentation about when you need them and when you don't.

Posted: Mon Mar 27, 2006 12:22 am

Raven wrote:

You never mentioned that this was a RavenNuke76 install.

Scroll up.

fade2gray wrote:

Is this something I can ask my webhosting service to rectify, or do I have to resign myself to not being able to use RavenNuke76?

Posted: Mon Mar 27, 2006 1:11 am

You are correct. When I saw the forum it was in, I raced ahead. In any event, In the documentation for RN76, it does state when you need it and when you don't.

Posted: Mon Mar 27, 2006 1:40 am

Raven wrote:

You are correct. When I saw the forum it was in, I raced ahead. In any event, In the documentation for RN76, it does state when you need it and when you don't.

Raven, at my level of experience, the references made to .htaccess in the documentation found in /rwsRavenNuke76_v2.02.00_FULL/ is way over my head; hence the need for me to have asked for advice in the first place.

A simple comment as outlined above would help elimate the need for you to bang-your-head over it, using the likes of me as the wall. Wink

Thanks.

Posted: Tue Apr 11, 2006 1:06 pm

fade2gray did you have AllowOverride Indexes AuthConfig Limit FileInfo as well as AllowOverride All? If you did try removing or commenting out AllowOverride Indexes AuthConfig Limit FileInfo.

Posted: Fri Apr 21, 2006 9:04 pm

Hi BriX, sorry for the delayed response - for some reason I didn't receive an e-mail notification for your reply.

BriX wrote:

fade2gray did you have AllowOverride Indexes AuthConfig Limit FileInfo as well as AllowOverride All? If you did try removing or commenting out AllowOverride Indexes AuthConfig Limit FileInfo.

Sorry to sound dense, but is that something I should be able to configure myself? I use a web hosting service and haven't noticed anything in the control panel that might facilitate this. Confused

Posted: Tue May 30, 2006 9:34 am

Its unlikely that you will find a way to change this via the control panel of your web hosting service. In order to make the changes I suggested, you would need access to the web server configuration files. The web host would likely never allow this. Wink

Posted: Thu Jun 14, 2007 7:12 pm

Just thought I'd bring this old cherry back to the surface now that I've progressed to delving around inside the NukeSentinel settings.

The only way I could initially get RN to work was to delete all .htaccess files from my installation (to prevent a server error) and just ignore the "File does not exist or is not correctly CHMODed." warning in the NukeSentinel settings.

But I have since discovered that I can password protect individual folders from within my web host's control panel. Applying this to a root nuke installation folder produces a .htaccess file and another file containing the encrypted password/s. All I had to do was modify the .htaccess file to meet NS's requirements and rename the password file to .staccess, then after setting NS to "Admin CGIAuth" I can protect any file in my Nuke installation by copying the .htaccess into it and making a few tweaks to the contents.

May have been a bit slow getting there, but progress or what? Dance-Y

Posted: Thu Jun 14, 2007 8:01 pm

Yes. Nicely done, but the real question is, Can NukeSentinel write to the .htaccess, and the only thing that I personally can think of that would allow this, would be that the group name had to be different. When you create a file, via ftp client, it creates that file with the owner and group both assigned to the user, unless somehow .htaccess is being created as nobody, which is not allowed by apache, then I could understand this delima, but if it is being created by an ftp interface, it should have never been named nobody. So once again, something in the root configuration of the server is a little off, IMO. So I would still sudjest you find a more complete Host. I'm sorry to say this, but in my experience, problems that arrise like this, only make me question the host, because if it is being an issue of how you created it, then it simply should not be allowed to be created like that.

Somethings only lead to further problems down the road, and if this is an issue of creation as I suspect, Then all other scripts are working without something being right in ownership. If this is as I suspect, you could be in Hackers dream world. I truly hope that I am wrong and this is an issue that I have no thought of yet, but please be carefull.

Posted: Thu Jun 14, 2007 8:47 pm

Thanks for your reply gregexp - maybe I didn't explain myself too well.

From my web based control panel I select a folder to password protect, giving any username and password (I could add numerous usernames/passwords but that would be pointless as the encrypted passwords would be different to those generated by "Build CGIAuth file: .staccess"). This generates a .htaccess file with the contents...

AuthUserFile /path_to/.username_password_file
AuthName "protected access"
AuthType Basic
require valid-user

I change that to....

# -------------------------------------------
# Start of NukeSentinel(tm) admin.php Auth
# -------------------------------------------
<Files >
deny from all
</Files>

<Files admin.php>
<Limit GET POST PUT>
require valid-user
</Limit>
AuthName "Restricted by NukeSentinel(tm)"
AuthType Basic
AuthUserFile /path_to/.staccess
</Files>
# -------------------------------------------
# End of NukeSentinel(tm) admin.php Auth
# -------------------------------------------

Then rename .username_password_file to .staccess deleting the contents, and when I apply "Build CGIAuth file: .staccess" the content gets re-populated with the correct sentineladmin names and encrypted p/words.

Also, blocked ip's are being written to .htaccess.

Does that make more sense, and do you still consider it a risk? (I operate on a really tight budget, and my host is one of the cheapest I can find in the UK for the package it offers).