"Domains with the “Forwarding” hosting type now support HTTPS. The support for securing such domains with Let’s Encrypt certificates via the Let’s Encrypt extension will be added later. (PPP-42238)"

Waiting for Let's Encrypt extension update then...

Finally! Thanks!
Please, keep up implementing requests from users on a regular basis! Some of the less known suggestions would be very valuable too. :)

enabling SSL on source domain is becoming a common request these days and I'm sick of doing it manually.

It is a shame that this is not implemented yet. I wrote a script which is rewriting the nginx vhostfiles to make it possible. To implement this a programmer needs 2 hours. Wouldnt plesk has encrypted source i would have done it already just to circumvent thia stupid cronjobs... OMG i switched already to a different software which is not better but at least ssl implemented correctly, including mailman.

This is more than important! For proper forwards (without quirky workarounds) it is absolutely necessary to assign certificates!

As Plesk won't move a finger for this, I would suggest two simple workarounds:
1) Avoid using frame forwarders. I don't see many scenarios where it's actually a good idea to use them. Also it's horrible for SEO.
2) If you're in a scenario where it's actually a good idea, then make an actual domain (with very small storage if you want), then secure it, then just make an index.html with an iframe inside. Takes 3 minutes.

Would require this feature due to an increased need of SSL for websites. Thus when a domain is used as a forwarding type but lack the required SSL functionality, this results in the behaviour of the forwarding website facing "This site can’t be reached" error when accessed through https.

Would appreciate this to be implemented soon.

Please please consider adding this feature.

It would be very useful aslo for mail SNI

Hosting type "No hosting" also needs this feature. Nice to have for parked domains.

I need it for my customers.

Please!

2 and a half year later and nothing happened... i really think we will never get these feature... thats sad

Yes, it should be dead simple and it's basic functionality that everybody needs!

it's very useful

Yes I need it too..

Let's go !

If I'm not wrong, you can do this as follow:
- don't use the "forwarding", but just keep the "type hosting" on "website".
- Add this line to the nginx settings: rewrite ^/$ https://www.yourdomain.com permanent;
- Now you can add a let's encrypt certificate to the domain

This function should absolutely be implemented

This is a MUST !