Problem after updating virtual servers to prevent unsafe symbolic links

10 posts / 0 new
Last post
#1 Thu, 12/13/2012 - 15:57
sergiok

Problem after updating virtual servers to prevent unsafe symbolic links

Hello,

After recent update to webmin-virtual-server from 3.96.gpl to 3.97.gpl, I was offered to perform the following (which I did, the process log below):

Fix Symbolic Link Permissions

Updating all virtual servers to prevent unsafe symbolic links .. .. fixed 1 domains

Applying web server configuration .. .. done

Searching for .htaccess files that use disallowed options .. .. found 2 in 1 domains

Virtualmin can fix these .htaccess files by changing the FollowSymLinks option to SymLinksifOwnerMatch. Unless this is done, accessing those directories via their websites will fail due to the use of the disallowed option.

How can I revert this procedure? I tried to restore a backup but this does not help, probably there is some configuration option that needs to be changed.

Please help, I am a total newbie in Virtualmin and hosting allover... Thanks.

Thu, 12/13/2012 - 16:17
andreychek

Howdy,

Reverting to a backup should undo the changes made during the upgrade process.

What problem is it you're having exactly?

If you're receiving an error of some sort with one of your domains, what errors do you see in the log file located in $HOME/logs/error_log?

-Eric

Thu, 12/13/2012 - 17:41
sergiok

There is no error, just my website looks weird now, no images and strange alignment... I did restore a backup but it did not help...

So I just want to revert this, but I do not know how.

Thu, 12/13/2012 - 18:47 (Reply to #3)
sergiok

n/a

Thu, 12/13/2012 - 18:57
sergiok

Looks like I resolved that! Eric, thanks for pointing me to the right log-file!

The log file had the following alerts there:

/home/domain.com/public_html/.htaccess: Option FollowSymLinks not allowed here

/home/domain.com/public_html/media/.htaccess: Option All not allowed here

/home/domain.com/public_html/media/.htaccess: Option FollowSymLinks not allowed here

I just commented-out these option lines in the associated .htaccess files (which were automatically added after updating virtual servers to prevent unsafe symbolic links) and now the website is up and running again.

Thu, 12/13/2012 - 22:19
andreychek

Super, I'm glad you got it working!

Fri, 12/14/2012 - 11:14
Smalls

Hi Sergio, can you tell me specifically which lines you commented out? I believe I'm having the same problem but commenting out:

Options +SymLinksifOwnerMatch

did not work? Thank you very much in advance!!

Fri, 12/14/2012 - 14:08 (Reply to #7)
sergiok

You need to review the error log file it will point out the file and lines that triggering the alerts.

Fri, 12/14/2012 - 16:45
yngens

Commenting out that option indeed helps, but at the same time causes other problems. Some discussion about this problem on http://drupal.org/node/105580, http://drupal.org/node/101197 and http://drupal.org/node/702106

Mon, 07/13/2015 - 16:42
jacobwilliam

I am pretty much pleased with your good work.You put really very helpful information. At Academy Women’s Healthcare Associates, we are committed to providing our Colorado Springs OB /GYN patients with a private practice in gynecology and obstetrics that is complete, up-to-date and patient-friendly.

OBGYN Colorado Springs

Topic locked