• 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Protect directories for 'host header' sites

B

brundle

Guest
I have a site setup in Plesk and the site has several additional domains setup via Host Headers in IIS.

We set it up this way so that there would not be an additional 10 sites setup in Plesk when all the domains do is point to the main website.

however, now when we add directory protection to the main site - it does not work when the other domains are used to browse to the site.

Any work arounds?

In Plesk 7, how is the authentication enforced when a Protected Directory is added?

Can the additonal host header domains be added to a list or somthing - maybe an .htaccess - like file?
 
.htaccess does not work with iss
you have set the hostheader names in the proberty field for this web.

start iis manger, open "your web" Properties dialog
open advanced and type in your hostheader names.


have you also examined the appropriate Prermission with the file explore in this directory (Sharing and Security)

c:\inetpub\www\vhosts\" your directory"
 
Yeah the perms are right - a username/password works when browsing to the domain of the main site - just not when browsing to a domain that exists in the host headers config in IIS for that site.
 
Back
Top