Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
We value your experience with Plesk during 2024 Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024. Please take this short survey: https://pt-research.typeform.com/to/AmZvSXkx
The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
When i remember right, it was possible ~ 1-5 yrs. ago when i worked on a Plesk Obsidian on Ubuntu 18.x... now i'm on Debian 10 "Buster" and it seems that it doesn't work anymore...
As long as both domains are in the same subscription, you can enter the same document root path in the "Hosting Settings" page for both. If the domains are not in the same subscription, this was neither possible then, nor is it possible now.
1. On Domain A click on "Hosting Settings" and write down the document root path of that domain.
2. Click on "Add Domain" and create domain B as "Webspace".
3. Click on "Hosting Settings" and change the document root path of domain B to the same like domain A.
- entering /httpdocs/HOST_A in domain config
- chown -R DOMAIN_Bsacln ./DOMAIN_A
- defining Options Indexes FollowSymLinks for both http and https for domain B as apache custom setting in plesk
-> it still does not work.. it seems entering /httpdocs/HOST_A in domain config will not be accepted becase of symlink. how to bypass?
-> Using /httpdocs/../../DOMAIN_A/httpdocs for domain B does also not work. That kind of string will be destroyed after saving - why??
-> mount --bind ... does also not work because i can't set permssions separetely
Short answer: You cannot access the documentroot of another domain. There's no point in trying to make this work with symlinks or other potentially dangerous methods.
DOMAIN_A will _only_ have access to files within /var/www/vhosts/DOMAIN_A
DOMAIN_B will _only_ have access to files within /var/www/vhosts/DOMAIN_B