Results 11 to 16 of 16
I've also tried this:
<Directory /home/webadmin/daveturkington.com/html>
Options Indexes Includes FollowSymLinks
AllowOverride All
</Directory>...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 11-13-2004 #11Just Joined!
- Join Date
- Nov 2004
- Posts
- 11
I've also tried this:
<Directory /home/webadmin/daveturkington.com/html>
Options Indexes Includes FollowSymLinks
AllowOverride All
</Directory>
- 11-13-2004 #12Just Joined!
- Join Date
- Nov 2004
- Posts
- 11
Where I am at now
Hi,
This is what I have for my VirtualHost entry now
I feel like this should work, but I am still getting a permissions error. The directories all have Traversal set and permissions are all 777.Code:<VirtualHost 192.168.0.100:9001> ServerAdmin email@domain.com DocumentRoot /home/webadmin/domain.com/html ServerName 192.168.0.100 <Directory "/home/webadmin/domain.com/html/"> # Possible values for the Options directive are "None", "All", # or any combination of: # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews # Options Indexes FollowSymLinks AllowOverride None Order allow,deny Allow from all </Directory> </VirtualHost>
Any ideas?
- 11-13-2004 #13Linux Guru
- Join Date
- Oct 2001
- Location
- Täby, Sweden
- Posts
- 7,578
That "ServerName 192.168.0.100" seems suspicious. Isn't it supposed to be "ServerName domain.com"?
- 11-13-2004 #14Just Joined!
- Join Date
- Nov 2004
- Posts
- 11
Tried that before and that didn't make a difference. Is this attribute even necessary? I don't have the domain pointed to this server anyway. I will be referring to it via IP.
Originally Posted by Dolda2000
- 12-09-2005 #15Just Joined!
- Join Date
- Dec 2005
- Posts
- 1
SELinux chcon
If you're running SElinux (more secure) then you may have to change the "security context" with chcon.
ls -lZ
will give you a long format directory listing. If you are running SE, it will have an additional attribute, the security context. which might look like
user_u:object_r:user_home_t
for the pages to be served you need to change the context to user_u:object_r:httpd_sys_content_t
which can be done with
chcon -t httpd_sys_content_t filename
Or you could disable SELinux, and not have to worry about it.
If that's not your issue, I'm not sure.
- 12-10-2005 #16Just Joined!
- Join Date
- Oct 2005
- Location
- North Carolina, USA
- Posts
- 45
Maybe too obvious, but did you remember to set User and Group directives in the httpd config file so that your server is running as webadmin in the users group?


Reply With Quote
