• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Search results

  1. H

    Erreur: Unable to open log file access_log: file should not be a symlink.

    Ok found a solution based on http://forum.parallels.com/showthread.php?81235-A-Simple-Follow-Symlinks-Apache-Solution&p=340666&viewfull=1#post340666 I had a symlink from /var/www/vhosts to <target_directory>, I replaced the symlink by a mount point in /etc/fstab ...
  2. H

    Erreur: Unable to open log file access_log: file should not be a symlink.

    I am running 11.0.9. And by looking into /var/log/sw-cp-server/error_log, I can't find any trace of the mentioned error :(
  3. H

    Erreur: Unable to open log file access_log: file should not be a symlink.

    There is no such folder in the machine
  4. H

    Erreur: Unable to open log file access_log: file should not be a symlink.

    Hi, That doesn't resolve the issue unfortunately.
  5. H

    Erreur: Unable to open log file access_log: file should not be a symlink.

    Hi, I have setup two server with the same config, but whenever I try to access log files on one server I get the error : "Unable to open log file access_log: file should not be a symlink." what would be causing that ? I checked the permissions, there are identical between the two...
Back
Top