"Option FollowSymLinks not allowed here" For All Domains Moved To New DA Server

S

SixSicSix

Verified User
Joined
Dec 10, 2009
Messages
5
"Option FollowSymLinks not allowed here" For All Domains Moved To New DA Server

[Sun Jan 01 12:21:16 2012] [alert] [client 123.45.67.89] /home/xxxxxxxx/domains/xxxxxxxxxxxxxxxxxxxxxxxx.com/public_html/.htaccess: Option FollowSymLinks not allowed here

So we're seeing this on every single domain moved last night to a new DA server running the latest release with the latest Apache and PHP 5.2.17 with suphp.

the only fix so far is to edit every single domain's custom HTTPD configuration in DA and add:

Code: 
<Directory /home/xxxxxxxx/domains/xxxxxxxxxxxxxxxxxxxxxxxx.com/public_html>
        AllowOverride All
</Directory>
<Directory /home/xxxxxxxx/domains/xxxxxxxxxxxxxxxxxxxxxxxx.com/private_html>
        AllowOverride All
</Directory>

Has anyone had this problem? If there is something we can do to fix this for all 300 domains without having to edit each custom HTTPD conf by hand (back to mod php maybe?) it would be an immense help.
 
Ah I'll have to try that next time. Here was my fix I threw together:

makecustomhttpdDA.sh

Code: 
#!/bin/bash
# Automatically makes a custom httpd.conf with the Apache overrides fix

# Make a list

ls -al /usr/local/directadmin/data/users | grep ^d | awk '{print $9}' | grep -v ^\\\. > /usr/local/directadmin/data/users/list.txt

#Get username and work on them one by one

for i in `cat /usr/local/directadmin/data/users/list.txt`
        do
                echo "Working on $i..."

                #Get domains and work on them one by one

                for e in `cat /usr/local/directadmin/data/users/$i/domains.list`
                        do
                                echo "Making the custom httpd.conf for $i and placing it into the following file"
                                echo "/usr/local/directadmin/data/users/$i/domains/$e.cust_httpd"
                                echo "<Directory /home/$i/domains/$e/public_html>" > /usr/local/directadmin/data/users/$i/domains/$e.cust_httpd
                                echo "AllowOverride All" >> /usr/local/directadmin/data/users/$i/domains/$e.cust_httpd
                                echo "</Directory>" >> /usr/local/directadmin/data/users/$i/domains/$e.cust_httpd
                                echo "<Directory /home/$i/domains/$e/private_html>" >> /usr/local/directadmin/data/users/$i/domains/$e.cust_httpd
                                echo "AllowOverride All" >> /usr/local/directadmin/data/users/$i/domains/$e.cust_httpd
                                echo "</Directory>" >> /usr/local/directadmin/data/users/$i/domains/$e.cust_httpd
                                chown diradmin:diradmin /usr/local/directadmin/data/users/$i/domains/$e.cust_httpd
                        done
                echo "$i done"
        done

#Rebuild the users' confs

echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
/usr/local/directadmin/dataskq d 6

#Done!

echo "All done."
 
And why did you need it that way (I mean using cust_httpd)? The same could be achieved an easier way... Did you read the link user ditto gave you?
 
You must log in or register to reply here.
Back
Top