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.
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.
I am in process of changing server hosts ... the current server host is RHEL running Ensim control panel, and my new server is RHEL running Plesk. On my current server, my subdomains are accessible via http://domain/subdomain as long as I do not have folder subdomain in docroot folder. I am not sure if this was special setup they assisted in, but now all my links to a very large website are coded that way, and it will be a lot of work to find and replace them all.
I am hoping to set that up on new server as well.
Thanks for quick reply,
Jesse
Yes, I have not set this up yet and would like any help you could provide.
Do you want me to contact you directly, or will you just post here ??
Thanks again,
Jesse
This also assumes you create your subdomains using the Plesk GUI, not a 3rd party utility such as 4PSA's utilities (which stores subdomains in a different location.
I have created all my subdomains with the Plesk control panel and they are in the default ... /var/www/vhosts/domain.com/subdomains/subdomain/httpdocs
If I understand correctly ... I run this command:
/usr/local/psa/admin/bin/websrvmng -u --vhost-name=example.com
to generate a vhost.conf file if it does not already exist.
Then I add the following line to the vhost.conf:
Alias /plesksub /home/httpd/vhosts/example.com/subdomains/plesksub/httpdocs
Just making sure I understand, as I am not yet very familiar with Plesk or these setup procedures.
Thanks a ton,
Jesse
Other way around. First you must create the file and put the Alias statement into it, then run the websrvmng command which will integrate the changes in the vhost.conf file into the domain's apache config files. Then restart Apache service.