Help with apache virtualhost

[Red Squirrel]

I've done this a million times and it's always worked fine... but not this time.

I am trying to add a new virtualhost, and it refuses to work. I just get forbidden when I try to access it. This is the directive:

<VirtualHost *:80>
DocumentRoot "/raid1/intranet/main/tools/webmail"
servername webmail.borg.loc

<directory />
allow from all
allowoverride all
options +followsymlinks +symlinksifownermatch
</directory>
</virtualhost>

I added options +followsymlinks +symlinksifownermatch since I found on google it would fix the issue, but it's still not working.

Here is one that works, I really don't understand why one would work and the other would not.

<virtualhost *:80>
documentroot /raid1/applications
servername applications.borg.loc
serveralias apps.borg.loc
</virtualhost>

I have tried to set the folder permissions to 777 in desperation thinking it may be a permission issue, still no luck. The error I get in the log is this:

[Wed Nov 23 03:37:12 2011] [error] [client 10.1.2.20] Options FollowSymLinks or SymLinksIfOwnerMatch is off which implies that RewriteRule directive is forbidden: /raid1/intranet/main/tools/webmail/

I don't get why one folder would work and the other would not. It just makes no sense.

 

[Red Squirrel]

ok turns out that particular folder had a .htaccess which I was not seeing in samba. wow... ok, I fixed it. I thought it was an empty folder. I think it's time for me to go to bed. 😛

 

[Nothinman]

Setting permissions to 777 is never the answer and the error you posted pretty clearly states that it wasn't a permissions issue in the first place.

 

[postaled]

ok turns out that particular folder had a .htaccess which I was not seeing in samba. wow... ok, I fixed it. I thought it was an empty folder. I think it's time for me to go to bed. 😛

Haha! I read the thread title and thought 'Wow, sounds like he might have a .htaccess sitting in there'

You beat me to it.

🙂

 

[Red Squirrel]

Setting permissions to 777 is never the answer and the error you posted pretty clearly states that it wasn't a permissions issue in the first place.

It was done as a troubleshooting step so I could rule out a permission issue. I am the only one with access to this server.

 

[Nothinman]

It was done as a troubleshooting step so I could rule out a permission issue. I am the only one with access to this server.

I get that, but if you have Apache installed you're not the only one with access to the server and that error clearly says that it's not a permissions problem so I don't get why you would even try that.