• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Subdomains and Protected Directories

iainh

Basic Pleskian
I am using psa v7.5.4_build75050824.12 os_RedHat el4

How can I create a protected directory in a subdomain?

Creating a subdomain is no issue. Creating a protected directory is no issue. Creating a protected directory in a subdomain seems impossible.

Protected directories only seem to be created from a root of [vhostRoot]/httpdocs/ (or httpsdocs)

Subdomains have their docroot in [vhostRoot]/subdomains/subdomainName/httpdocs/ (or httpsdocs)

It is not permitted when defining a protected directory location to cut back and define something like:

../subdomains/subdomainName/httpdocs/myProtectedDir/

and there seem no other way to pointed the protected directory creator to anything other than the main domain docroot.

Likewise, if you go into subdomain management there is no subdomain management options beyond creating the subdomains and setting admin rights to each.

I've even tried File Maintenance and while I can navigate into the subdomain docroot and create directories, there's no protected directory option!

Do I need to resort to creating my own .htaccess file or creating a new vhost in the name of the subdomain?

Many thanks.../Iain

PS: One further thought...

Creating a new vhost in the subdomain name would seem one solution, but not really what's wanted - a bit overkill? Might another option be to alter the domain to the subdomain name...but would that then affect Email? e.g.

The domain name is currently set as 'www' UNchecked, domain.co.uk

If the domain name were altered to 'www' UNchecked, subdomain.domain.co.uk, would that force all Email to change from <name@domain.co.uk> to <name@subdomain.co.uk> - not a desired result!

Note the vhost is running Email for the domain but is not current the www host and so the www CNAME points to a different host...
 
Back
Top