Question How to forward a https domain without certificate warning ??

[AndreasY]

Hi, firstly both of these do not offer a solution

How to allow HTTPS and configure certificates with a domain that has Hosting type set as Forwarding?

How to allow HTTPS and configure certificates with a domain that has Hosting type set as Forwarding?

(yeah same titles different URLs........................)

Anybody who uses Plesk regularly knows that once we enable

Hosting type: Forwarding

For a given domain, then no 'File Manager' is available

So why the second set of instructions for this 'How to' for Windows says

"Navigate to Domains > example.com > File Manager"

I do not know ...................................................

So could someone please offers us Windows users a solution.

To make this specific

https://oxayianapa.com/ is using forwarding type "Moved permanently (code 301)" to https://omilosxyloraketasayianapa.com

Web.config already has the values we are asked to designate in step 3 (I checked via IIS)

Thanks

 

[AndreasY]

Alright, seems nobody can answer.

At least and hope that the official Plesk volunteers would amend the articles that have been publicly posted that are clearly incorrect (or inform those who published them).
** Err I got this wrong please dismiss, the Plesk workaround is correct, my own workaround is below, dont know if it will work indefinately **

Also, hopefully, we can get a clear and concise answer to the following question (ive asked this before but am still unsure if the answer that was given is correct as the answer did not come from an official Plesk representative.)

So.......

In the Plesk CP

Home --> Tools & Settings --> SSL/TLS Certificates --> Certificates currently in use for securing Plesk server and mail server --> +Lets Encrypt button

Are certificates that are added via pressing the +Lets Encrypt button automatically renewed ??

** IMPORTANT **
When this is done one must remember to re-assign the correct certificate for securing Plesk as this section is actually meant to create the certificate to secure Plesk.

Because if they do automatically renew, we can use the +Lets Encrypt button to create a LetsEncrypt certificate for the domain that is then available to us in IIS and from there we can manually create the bindings for the domain.

This workaround will work, and will work 'permanently' but only if the certificate is auto renewed.

On a side note,

Can someone please explain if expired LetsEncrypt certificated should automatically be removed from the Windows certificate store as in this moment in time if ones goes to add a https binding for a domain, in the dropdown list for ssl certificates there are multiple duplicate entries for each domain.

These are all the OLD certificates, I dont know if this is by 'design' or something that the developers of Plesk have missed.

Thanks