• 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.

Standard domain forwarding does not forward https connections

IDFarm

New Pleskian
Hi there,

I have researched this issue but couldn't find a satisfying answer.
The following thread/FAQ topic is what I found, but neither gives a proper solution:
http://kb.odin.com/en/119558
http://talk.plesk.com/threads/standard-forward-doesnt-redirect-https.84684/

We are running Plesk 12 on a Linux VPS where we have multiple domains running.
Multiple of these domains should redirect from www.domainname.ext to https://ext.domainname.com.
This is configured with the Domain forwarding in Plesk, with hosting type Forwarding.
But as described in the 2 links provided above, whenever you go to https://www.domain.ext, it does not redirect, and actually shows a Security error, since the domain doesn't have the SSL-certificate installed (because it should redirect to the https://ext.domainname.com).

Clearly we don't want visitors on the website to receive the (incorrect) Security error, and we want all traffic to http(s)://www.domain.ext to be redirected to the appropriate subdomains.

Hopefully there is a solution which allows us to redirect both the https/http connections to the domains, without forcing us to have the domains have a Website hosting and redirect them manually with (for example) .htaccess.

If anyone knows a solution to this, I would love to hear it.

Thanks in advance

Rowan
 
I have no idea if bumping is allowed, but I'm just gonna bump this :)
Hopefully someone has an idea how to solve/configure this so it can be set up as described above.

Rowan
 
Back
Top