Let's Encrypt alt names for panel cert?

@Catscrash

Based on your requirements, This is how the new interfaces (client and admin sides) will look:

Admin side
letsencrypt_interface_admin.png

Client side
letsencrypt_interface_client.png

I hope that this will make you happy

BTW:

After re-reading your requirements, I think that your way of doing is not the best. i-MSCP provides a feature allowing your clients to redirect requests to other server transparently (in your case, that would be Nginx instance of i-MSCP server). How to process:

Admin side

• Enable Let's Encrypt for the panel.hosting8.example control panel domain

Customer side

• Create the webmail.custdomain1.de subdomain with the following options:
  
  
  • URL forwarding: Yes
  • Forward URL: https://panel.hosting8.example:4443/webmail/
  • Forward type: PROXY
• Enable Let's Encrypt for the webmail.custdomain1.de subdomain

Then your customer could access the webmail through the https://webmail.custdomain1.de URL transparently, without having to enter any path nor specific port. Requests would be proxied transparently.

you're welcome

Envoyé de mon SM-A510F en utilisant Tapatalk

on 19th

Envoyé de mon SM-A510F en utilisant Tapatalk

@Catscrash

You're welcome Thanks for your feedback.
Thread closed.