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

Upgraded to 11.5, wildcard issues solved with wildcard subdomain?!

jaketone

New Pleskian
We run a website where we use dynamic "subdomains" to determine/set a few variables within our codebase. The subdomains are not actual domain-entry subdomains, but just that -- dynamic. We validate them in our code and redirect to a homepage if they are invalid.

For example: https://test.domain.com

We grab "test" from the URI and confirm this is an actual "company name" in our database. If it is, we serve "test" company settings/variables accordingly and they browse our site via the test.domain.com root (even though there is no actual subdomain called "test").

ANYWAY, we have a Wildcard SSL certificate installed. We just upgraded to 11.5.30 and the wildcard SSL no longer worked and instead referenced the parallels root certificate. It worked with www and the root domain, but no longer worked on any wildcard subdomains. To further test, we created a test subdomain within Plesk, and the SSL wildcard cert validated but we can't go around creating meaningless subdomains(virtual hosts) in this regard because there is only 1 code base serving all pages.

The only way around this was to create a subdomain called "*". This works but it seems like a weak fix but I don't know what else to do.

Ideas?
 
Back
Top