UREGENT! Updated to 3.97 and now magento site is a mess

12 posts / 0 new

Topic locked

#1 Fri, 12/14/2012 - 11:13

Smalls

UREGENT! Updated to 3.97 and now magento site is a mess

Updated to 3.97, in the process it gave me a prompt saying I should disable symlinks which replaced Options +FollowSymLinks with Options +SymLinksifOwnerMatch and now the magento site is a complete mess, no images are loading etc.

How can I re-enable sym links and get it working?

Thank you very much in advance!

Here's the error from the log file:

[Fri Dec 14 11:54:00 2012] [alert] [client xxx.93.168.xxx] /home/domainname/public_html/media/.htaccess: Option All not allowed here, referer: http://www.domainname.ca/webpage.html

#2 Fri, 12/14/2012 - 11:37

Smalls

I think this is a FIX for the problem. Can someone in the know please confirm whether or not this is a proper fix? Thanks a million!!

I believe I got the site back up and running by going to virtualmin -> websitedomain -> services -> configure website AND configure website for SSL and going to edit directives for both and finding "SymLinksifOwnerMatch" and replacing it with "FollowSymLinks"

Also, i found any .htaccess files in the directories and commented out:

Options +SymLinksifOwnerMatch

Here's an example from configure website -> edit directives

ServerName websitedomain.ca ServerAlias www.websitedomain.ca ServerAlias webmail.websitedomain.ca ServerAlias admin.websitedomain.ca DocumentRoot /home/websitedomain/public_html ErrorLog /home/websitedomain/logs/error_log CustomLog /home/websitedomain/logs/access_log combined ScriptAlias /cgi-bin/ /home/websitedomain/cgi-bin/ DirectoryIndex index.html index.htm index.php index.php4 index.php5 Options -Indexes IncludesNOEXEC SymLinksifOwnerMatch +ExecCGI allow from all AllowOverride All Options=ExecCGI,Includes,IncludesNOEXEC,Indexes,MultiViews,SymLinksIfOwnerMatch allow from all AllowOverride All Options=ExecCGI,Includes,IncludesNOEXEC,Indexes,MultiViews,SymLinksIfOwnerMatch RewriteEngine on RewriteCond %{HTTP_HOST} =webmail.websitedomain.ca RewriteRule ^(.) http://websitedomain.ca:20000/ [R] RewriteCond %{HTTP_HOST} =admin.websitedomain.ca RewriteRule ^(.) http://websitedomain.ca:10000/ [R]

#3 Fri, 12/14/2012 - 11:42

Smalls

for comparison, here is the original from services -> configure website -> edit directives... Don't forget you need to edit the configure website AND configure website for SSL for it to work properly!

#4 Fri, 12/14/2012 - 12:54

andreychek

I responded to another of your posts before seeing this one -- take a peek in your Apache error logs, in $HOME/logs/error_log, and let us know what error(s) you're seeing.

Then we can assist you in getting things back to normal again :-0

-Eric

#5 Fri, 12/14/2012 - 12:55

Smalls

Hi Eric,

The error was: [Fri Dec 14 11:54:00 2012] [alert] [client xxx.93.168.xxx] /home/domainname/public_html/media/.htaccess: Option All not allowed here, referer: http://www.domainname.ca/webpage.html

Thanks! I'm back up and running now, I just want to make sure my "fix" mentioned above was correct (and secure as possible). Thanks again

#6 Fri, 12/14/2012 - 12:57

andreychek

Ah, I missed that you did offer your Apache error logs... thanks! :-)

Can you post the contents of your "/home/domainname/public_html/media/.htaccess" file?

It sounds like there's an option being used there that's not compatible with the recent updates.

-Eric

#7 Fri, 12/14/2012 - 12:59

Smalls

Hi Eric, attached to this post, thanks

#8 Fri, 12/14/2012 - 13:12 (Reply to #7)

tpnsolutions

Hi,

If memory serves me right, you should be able to edit your ".htaccess" file to correct this error on the website level.

Look for the line your ".htaccess" file reading:

Options +SymLinksifOwnerMatch

Change this to read:

Options +FollowSymLinks

This should make that website operate the way it was originally, as the changes were done at the Apache configuration level therefore you should be able to still manipulate the ".htaccess" file on the website level.

Let us know if this works for you!

-Peter

Best Regards,
Peter Knowles | TPN Solutions
Email: pknowles@tpnsolutions.com | Skype: tpnassist

#9 Fri, 12/14/2012 - 13:22

Smalls

Hi Peter,

That did not work it was the first thing I tried, thanks for the advice though

#10 Fri, 12/14/2012 - 13:39 (Reply to #9)

tpnsolutions

Hi,

No worries, perhaps Jamie, Joe or Eric may have an alternate ideas.

In the meantime, have you checked the error log? If so, what if any errors are showing up. Most apps like these are pretty verbose in the error log, even if not on screen.

-Peter

Best Regards,
Peter Knowles | TPN Solutions
Email: pknowles@tpnsolutions.com | Skype: tpnassist

#11 Sat, 12/15/2012 - 01:57

sentient

Please check my post here, there may be a solution.

http://www.virtualmin.com/node/24518

#12 Thu, 09/26/2013 - 11:51

philmck

An update in case it helps anyone: This combination worked for me with Virtualmin 4.02gpl and Magento 1.8.0.0 (stable) running on Ubuntu 10.04 LTS with php-suhosin installed.

In Magento .htaccess and media/.htaccess, change

Options +FollowSymLinks

Options +SymLinksifOwnerMatch

Also in media/.htaccess, comment out

#Options All -Indexes

Phil McKerracher www.beeches.it

Topic locked