• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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..
 
You must log in or register to reply here.

Similar threads

M
Issue {WEBSPACEROOT} is the wrong directory. How do we fix this?
Replies
10
Views
7K
MHC_1
M
Azurel
Resolved File Check scans every domain separately instead of checking unique vhost directories
Replies
5
Views
3K
Sebahat.hadzhi
Sebahat.hadzhi
M
Issue Cron Job can't "Run Now". Also Cron Job/Scheduled Tasks lacks documentation
Replies
3
Views
3K
Aleksei Fedorov
A
E
Issue Plesk backup / Could not back up all data from the directory
Replies
4
Views
3K
Sebahat.hadzhi
Sebahat.hadzhi
M
Issue PHP Cronjob in Plesk -- Lack of documentation. Lack of structure. Multiple Issues.
Replies
4
Views
4K
MHC_1
M
Back
Top