File does not exist error. But it does exist!

apache-2.2

I moved a Zen Cart installation from a different server to a new one on Rackspace running Redhat Enterprise Linux 5.

I had everything up and running until today. My most recent actions to this particular set of files involve changing the owner of the files to a newly created group. My user is still the owner.

I am now receiving a file does not exist error on some files and directories that I can confirm do in fact exist. I can't navigate to the directory or any file underneath it in the web browser.

When I navigate to them in FF i get:

Not Found
The requested URL was not found on this server.

My error logs dont show any difference in the file being requested.

Any ideas as to why this would happen? Could changing the group have affected this.

Thanks in advance

Best Answer

Check your log files to see what the server is actually attempting to pull. I'd be willing to bet that this is either an issue with file permissions, or something in the servers config, related to document roots or some such. Realistically though we really need more information, and maybe a few examples, etc...

Related Solutions

Linux – File permissions on web server

It's really hard to give a solid answer for this because security is a balance between protecting your resources from intruders while still allowing your users (and the Web server) to access the resources they need access to.

Starting from a more restrictive platform, you can always lighten up on security as you discover that more people need access to certain things. It sounds like you've put a lot of thought into this, so you could surely give it a try and lighten things up as you learn more about usage patterns and what works and doesn't work.

Php – Fixed: Apache – PHP permissions to create / edit files and directories

Giving the apache user write access to your entire DocRoot is not ideal. I usually configure things a bit differently.

First I identify a place where the files will be written - this can be in the DocRoot, or it can be in a separate location that's brought in with an Alias configuration in apache.

I create a group (usually called www-pub) and add the apache user to it.

Then I do

chown root:www-pub <directory>

and

chmod g+rwxs <directory>

which sets the setgid bit, meaning that any files or directories created under the top will have the same group as the parent directory, as well as being writable (and readable) by that group.

That way, you restrict where and what the apache user can get at, but still allow file creation and so forth in that area only.

Best Answer

Related Solutions

Linux – File permissions on web server

Php – Fixed: Apache – PHP permissions to create / edit files and directories

Related Topic