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

Resolved Forward Domain - Problem with SSL

Wolfgang Giesel

New Pleskian
Hello,

I have this situation with Plesk 17.5.3:
I forward the domain shop.foam-tv.com to a other domain that I manage with plesk (foam.surf)
When I access http://shop.foam-tv.com I will forwarded to https://foam.surf as expected.
When I access to https://shop.foam-tv.com it opens the typical PHP Test site.

How can I forward both cases to the new website.

Thank you.

Best regards.
Wolfgang
 
There are two issues involved.

One is that you are missing the SSL certificate for the forwarded domain. This typically occurs with Let's Encrypt, because the token file cannot be written or read on a redirected domain. For a workaround, configure the domain as web space and place this .htaccess file into the document root directory of the domain:
Code:
RewriteEngine On
RewriteCond %{REQUEST_URI} ^/.well-known/acme-challenge [NC]
RewriteRule .* - [L]
RewriteRule ^(.*)$ https://foam.surf/$1 [L,R=301]
Then create the Let's Encrypt SSL certificate for the domain.

The second issue is that the redirect itself is not configured correctly. To solve that, I'd need to have a look at your panel, which obviously is not possible, nor can I provide this kind of individual support.

My suggest to solve both issues at the same time is to
1) Remove the shop.foam-tv.com domain.
2) Add the same domain as an alias with the "Add Alias" button to the main domain. When you add the alias, UNCHECK the 301 redirect checkbox. You do not want the 301 redirect, but a real alias. If the domain is configured as an alias, it will do two things: It will deliver the website content on the domain name AND when you use the Let's Encrypt function on the redirect target (the main domain), you can add the alias to the certificate so that it is covered by the same certificate.
 
Dear Peter,

Thank you very much for your help. I finally used the alias solution to create the alias and it works for me.

Thank you very much.

Best regards,
Wolfgang
 
Back
Top