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.
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
When I change the document root served websites, occasionally and whenever I reboot the server Plesk reconfigures them to be /var/www/vhosts/domain-name/httpdocs. How do I keep Plesk from doing this?
Since the psa.conf file I am guessing is a Plesk configuration file, then probably not. Is that where I should set the document roots in the psa.conf file?
I believe that this will only change the vhost directories for all virtual sites. Not specific ones. Currently Plesk has the directory set for /var/www/vhosts then within that, the document root is set to domain-name/httpdocs, although I am not sure what sets that as it is not in the httpd.conf file. Webmin actually allows you to change document root of each virtual host to anything within that virtual host directory. So I could change the root to /var/www/vhosts/<domain-name>/httpdocs/joomla. I can't figure out where Webmin is getting this information from though. When I change the document root here it stays for a "period of time". Usually until I upgrade Plesk or physically restart the server then everything reverts back to /var/www/vhosts/<domain-name>/httpdocs. Plesk is a nice interface for the end user who wants to manage their domain settings and it is "okay" for administering web services, but there are too many things that you just can't get to with it. And if you make a change outside of Plesk then you have to deal with the consequences of how Plesk reacts.
Now you can change that and it will take effect once you restart apache. But the problem is that a lot of the times when psa restarts, reboots, or the domain has a change that occurs in plesk the httpd.include file gets overwritten each time - so all changes are lost.
You will need to put the changes into a vhost.conf file there instead and then do the reconfigure command
Actually I was thinking " to make it overly simple wouldn't it be great if Plesk allowed me to change my document root on a virtual host basis"? It is strange because I "rent" my server from 1and1 and if you use 1and1's shared hosting you can actually do this from within their control panel, which is home grown not cpanel not plesk. But you are probably right, might be easier in the long run to move the site up one level. Thanks for trying though.
Okay, here is an interesting discovery. None of the domains that I am hosting has a vhost.conf file in the <domain-name>/conf folder. The only file in that folder is an httpd.include file which makes reference to the vhost.conf in the comments section and says that it should be in this same folder.
no domain has one by default unless you create it in the skeleton directory. You need to create one manually for any domain you wish to have a permanent server setting change