Issue Let's encrypt error Domain Forward

[GunFood]

Hey,

I try to set up a frame forward for a subdomain using https. I have the option to start let's encrypt but I get the following error message:

Fehler: Domain with id=13 not found

If I switch to Webhosting, I'm able to generate a certificate. After switching back to frame forward the certificate is no longer associated with the subdomain.

Bug or feature? Any idea?

 

[Bitpalast]

This is a known bug. However, it does not make any sense to equip a forwarding-domain with an SSL certificate, because in forwarding there is no content that can by encrypted or decrypted.

 

[Frank.P]

I have the same iused but with alias domain

 

[GunFood]

hi.

I think this is important, especially if you use a frame forward. In this case the ssl handshake will be done before the content has been loaded. So without a valid certificate, you her an error from your browser.

In my scenario: I have a customer running an Exchangeserver behind one static IP. He uses different certificates for the main domain on his iis server and one for the autodiscover Records. To forward the mail clients to the autodiscovery, he defined a different https port on the iis and assigned the autodiscover certificate to this setting. I've set up the autodiscover subdomain in plesk using frame forward the the ip and the seperate https port. The communication doesn't work without a valid certificate in plesk for the subdomain. For testing we configured the frame forwarding as a nginx proxy directlly on the plesk box, which works fine with a Let's Encrypt certificate.

And yes, I her the same error for Let's Encrypt using

 

[Frank.P]

I use https://www.sslforfree.com to create manualy certificate.

 

[Bitpalast]

Frame redirect is not a web server redirect, but a one-page-website, the frame, in which another URL is loaded. It is the same as web space, so you need to create a certificate for that and you can create one for it. In a frame redirect real content is transported, the frame page. In a web server redirect no content is delivered, but only a header that tells the browser to load a different url. There is no need to encrypt such data, because it is insensitive.

If you prefer a frame redirect, you can configure your domain as web space and put a single frame into it. You can create your cert for that w,Web space so that the frame page will be encrypted.