The error message "Symbolic link not allowed or link target not accessible" typically indicates an issue with symbolic links on your server. Here are steps you can take to address this issue:
-
Check Permissions:
- Verify the permissions of both the symbolic link and its target. The target should be accessible by the web server user (usually
www-data
on Linux systems).
- Verify the permissions of both the symbolic link and its target. The target should be accessible by the web server user (usually
-
Verify the Symbolic Link:
- Ensure that the symbolic link is set up correctly. The link should point to a valid target. You can use the
ls -l
command to view the link and its target.
Example:
bashls -l /path/to/symlink
- Ensure that the symbolic link is set up correctly. The link should point to a valid target. You can use the
-
Check for Broken Links:
- Verify that the target of the symbolic link exists. If the target has been moved or deleted, the link will be broken.
-
Update Apache Configuration:
- If you're using Apache, check the configuration files for the domain in question. Make sure that the
FollowSymLinks
option is enabled.
Example Apache configuration:
Mathematica<Directory /path/to/directory> Options +FollowSymLinks </Directory>
- If you're using Apache, check the configuration files for the domain in question. Make sure that the
-
Enable
Options
in.htaccess
:- If you're using an
.htaccess
file in the directory, ensure that theOptions
directive allowsFollowSymLinks
.
Example
.htaccess
:MathematicaOptions +FollowSymLinks
- If you're using an
-
Check for SELinux or AppArmor:
- If you're using SELinux (Security-Enhanced Linux) or AppArmor, they may be preventing Apache from following symbolic links. Adjust the security policies accordingly.
-
Ensure the Target Path is Correct:
- Make sure that the target of the symbolic link is correct and that the web server user has appropriate permissions to access it.
-
Verify PHP Settings:
- If PHP is involved in serving the page, ensure that
open_basedir
or similar restrictions are not preventing access to the target of the symbolic link.
- If PHP is involved in serving the page, ensure that
-
Check Logs:
- Review the Apache error logs for any specific error messages related to symbolic links or file access.
-
Recreate the Symbolic Link:
- If all else fails, you can try recreating the symbolic link. Remove the existing link and create a new one using the
ln -s
command.
- If all else fails, you can try recreating the symbolic link. Remove the existing link and create a new one using the
Example:
rm /path/to/symlink
ln -s /path/to/target /path/to/symlink
- Contact Plesk Support:
- If the issue persists and you're unable to resolve it, consider reaching out to Plesk support for further assistance. They can provide specific guidance based on your setup.
Always exercise caution when working with symbolic links, especially in production environments, as incorrect configurations can potentially lead to security vulnerabilities or broken functionality.