• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

New subdomain generates 'too many redirects' error message

E

elR

Guest
Hello kind souls. =)

After reading the Apache docs describing the ServerAlias directive, I'm still having trouble understanding how it functions. I've got a WordPress Network (Multisite) setup that requires I add ' ServerAlias "*.domain.tld" ' to the /var/www/vhosts/domain.tld/conf/vhost.conf file. This works fine.

However, I just created a new subdomain via the plesk control panel, which placed a directory for it here: /var/www/vhosts/domain.tld/(subdomain) - and in /var/www/vhosts/domain.tld/subdomains/(subdomain) - and attempting to visit subdomain.domain.tld in my browser generates a 'too many redirects' error.

My question is:
Is the ' ServerAlias "*.domain.tld" ' causing this problem, or am I missing a step somewhere in getting the subdomain to load in the browser?

UPDATE:
Here's the httpd.conf content auto-generated by Plesk:
http://pastebin.com/gzJ9TChq
 
Last edited by a moderator:
Hi Amin - thanks for the reply!
All I have as far as .htaccess goes is a basic WordPress .htaccess file in the /var/www/vhosts/domain.tld/httpdocs directory: http://pastebin.com/fLaTEDMT

There's likely some other sorcery going on with WordPress that lets it manage subdomains that it manages, but I don't imagine that it would interfere with another subdomain not in its list...

Perhaps you know better?
 
Just to rule it out can you rename the file or comment out the lines in it and then re-test? Worst case no change but at least we can rule it out.
 
Back
Top