Symlink between multiple domains on PLESK 8.1 (Linux)

Hey Experts!

I'm in a situation where I need to create a symlink from one domain to another in PLESK 8.1.  Althought the symlink is properly created, I keep getting a FORBIDDEN error from Apache when trying to access files which should  be accessible through the symlink.

I'm guessing this is a chown issue where Apache is locked down by PLESK to not allow symlinks between domains.

Does anyone know a simple way around this?  If so, are there serious security implications to your suggested change?

Thanks a lot!

Brendan
brendanwovAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Artysystem administratorCommented:
There is an option in httpd.conf to allow following symlinks:
Options FollowSymLinks
Without this option following symlinks is forbidden.
Read here: http://httpd.apache.org/docs/2.0/mod/core.html#options

What is the exact error text? Please provide the error line from apache error_log file.
0
brendanwovAuthor Commented:
Hey Nopius!

Thanks for your quick reply.  Here is how my httpd.conf file is currently configured...

<Directory />
    Options FollowSymLinks
    AllowOverride None
</Directory>

Can you give me the exact syntax of what I need to change in order to allow symlinks between domains?

I look forward to your reply.  Thanks!

Brendan
0
brendanwovAuthor Commented:
Hey Nopius!

Just to be sure you have all the information you need...

# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory />
    Options FollowSymLinks
    AllowOverride None
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "/var/www/html">

#
# Possible values for the Options directive are "None", "All",
# or any combination of:
#   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important.  Please see
# http://httpd.apache.org/docs-2.0/mod/core.html#options
# for more information.
#
    Options Indexes FollowSymLinks

#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
#   Options FileInfo AuthConfig Limit
#
    AllowOverride None

#
# Controls who can get stuff from this server.
#
    Order allow,deny
    Allow from all

</Directory>


I look forward to your reply.  Thanks!

Brendan
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

Artysystem administratorCommented:
It looks that you have required option. Now I need to see what Apache says in /var/www/logs/error_log (I belive it's correct path), just try to access symlinked domain then copy-paste the output from:

tail -20 /var/www/logs/error_log

0
brendanwovAuthor Commented:
Hey Nopius!

I triggered the error and then viewed the log files and there didn't seem to be any errors listed within the most recent 20 minutes.  So I don't think this error is registering.  To calrify, the log file you suggested I tail didn't exist so I used the command below.

tail -50 /var/log/httpd/error_log

Thanks for your help!  What do you suggest?  Let me know.

Brendan
0
Artysystem administratorCommented:
If you get 'forbidden' then _very_ likely there are some logs about your access attempt. Maybe not in this file. May be in /var/log/httpd/access_log (try tail that file).

Or you may have different logfiles for different domains. To check it, run
grep -i errorlog httpd.conf
and post results here.

If there is nothing either in access_log or in error_log (or in all logs for all domains if you have separate), then probably 'forbidden' comes not from Apache or your server, but from some kind of proxy between you and Apache. Please provide what exact error message your browser says.

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Apache Web Server

From novice to tech pro — start learning today.