• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Lord have mercy!

W

weverette

Guest
CentOS 5; Plesk 8.3

I've been racking my head over why this won't work! It did at one time, then just stopped.

I need for a photos directory under one domain to be accessible and writeable to another domain on the same server. I created a symlink to the folder of the 1st domain as a folder on the second as such:

ln - s /var/www/vhosts/domainA.com/httpdocs/members/photos /var/www/vhosts/domainB.com/httpdocs/members/photos

Through wincp, I can see that the link was created (owned by root) and is functioning.

It worked. A week later, it doesn't. The only hint is "open_basedir restriction in effect" in the errorlog of domainB. The open_basedir directive is commented out in php.ini.

HELP!
 
I found the darn thing. httpd.include in the conf directory for the concerned domain in the 443 configuration. Just how many places does plesk use <virtualhost> for each host?
 
Yep

Saw that. That's what threw me. There is no vhost.conf on my server. Anywhere. It was a file named httpd.include in the "conf" folder of the domains home folder. It had the following warning:

"# ATTENTION!
# DO NOT MODIFY THIS FILE OR ANY PART OF IT. THIS CAN RESULT IN IMPROPER PLESK
# FUNCTIONING OR FAILURE, CAUSE DAMAGE AND LOSS OF DATA. IF YOU REQUIRE CUSTOM
# MODIFICATIONS TO BE APPLIED TO THE CONFIGURATION, PLEASE, PERFORM THEM IN THE
# FOLLOWING FILE(S):
# /var/www/vhosts/xxxxxxxxxxx.com/conf/vhost.conf
# /var/www/vhosts/xxxxxxxxxxx.com/conf/vhost_ssl.conf
# /var/www/vhosts/xxxxxxxxxxx.com/subdomains/<subdomain-name>/conf/vhost.conf"

None of those files existed. But the httpd.include was where they were supposed to be.
 
they do not exist by default but should be created manually if you want to add your custom config..
 
Back
Top