http driving me crazy

[ice2003]

I am having a couple of problems that is driving me crazy with setting up an http service.

Have installed and am now running fedora 5 as i used to be running 4 , what i am wanting to do is change the root of the http docs, i change things via the config file of apache which works fine and point it to another dir , but when loding the page it gives me a you do not have access page. I have tried setting every sort of access to the dir but it just gives me the same thing. I am running it on just a local machine as i use it for my php coding testing.
What am i missing here is there something that i have not done right , both the firewall and selinux is turned off , another thing i am wanting to do is add a virtual host and point that in another dir , but i have to get the first one to work before i attempt that.

Any hints on where to go from here.

note: sorry put into wrong section should be server's could somebody move please.

[gavinw6662]

Well 2 things come to mind. First of all - if you disabled selinux - how'd you do it?

edit etc/sysconfig/selinux , or setenforce 0 ?? If you did it the first way, you will need to restart fedora. If you did it the second way, then selinux should be disabled. That's good. Now, in order to view the web doc's in that folder, you need to make sure the permissions are set accordingly on that directory. Typically, you need to make sure that the directory is atleast readable all the way across the board. Typically you need something like 755 - or 744. It relaly depends on your setup. But make sure that directory is something more than 700 cause that will cause problems. Everyone neads 'read' access to an apache directory.

[ice2003]

have done it both way's , either way selinux is disabled , and the folder is set to 777 so anything and everything should have access to it , but upon changing to that folder or any folder outside of /var/www/http throws up the access error , i am finding this so fustrating.
I had no problems with it on fedora 4 just changed the dir and bam thats where apache was getting the files from but now i am stummped.

[mdwolfe]

Originally Posted by ice2003

have done it both way's , either way selinux is disabled , and the folder is set to 777 so anything and everything should have access to it , but upon changing to that folder or any folder outside of /var/www/http throws up the access error , i am finding this so fustrating.
I had no problems with it on fedora 4 just changed the dir and bam thats where apache was getting the files from but now i am stummped.

Sometimes folders don't like being 777. Have you tried making the folder 755?

Mary

[ice2003]

yes have tried that as well with no success , i have just about given up now as everything i have tried seems to have failed.

[mdwolfe]

Originally Posted by ice2003

yes have tried that as well with no success , i have just about given up now as everything i have tried seems to have failed.

Try setting it up as a virtual host. My other directory sites are all virtual hosts.

Mary

[ltam]

Originally Posted by ice2003

have done it both way's , either way selinux is disabled , and the folder is set to 777 so anything and everything should have access to it , but upon changing to that folder or any folder outside of /var/www/http throws up the access error , i am finding this so fustrating.
I had no problems with it on fedora 4 just changed the dir and bam thats where apache was getting the files from but now i am stummped.

Are you trying to point to a directory still under the /var/www/html? Or outside?

[ice2003]

nope same deal , i dunno i give up something so simple that should not be a problem turns into a major drama its so fustrating.

[ccrvic]

Originally Posted by ice2003

nope same deal , i dunno i give up something so simple that should not be a problem turns into a major drama its so fustrating.

What *exact* error are you getting on the browser?
What error is reported in the Apache error log?
What are the permissions on the file in question?
What contexts in your httpd.conf contain a DocumentRoot directive?

Vic.

[fpoole]

If the directory's permissions aren't set to Allow,deny in httpd.conf, then none of the chmodding will do anything. Also, make sure you don't have any busted .htaccess files in that folder or subdirectories. That will screw up a server faster tahn anything else.

[ice2003]

Thanks for all the info guys i managed to solve the problem by the suggestion of setting up virtual hosts for users and did it that way. Its only on a local system running into a sandbox but the main thing is i finally got it work. Thanks for everybodys help