Since Cpanel thinks this old thread is outdated:
http://forums.cpanel.net/f5/ssl-acc...96-signed-wildcard-hostservercert-227211.html
When using e.g. www.customermail.tld/webmail you can get a screen:
"Connection Selection ..."
If you are not behind a firewall that blocks port 2096
Enter Here https://host.whmdomain.tld
If you are behind a firewall and can not connect to port 2096
Enter Here https://webmail.customerdomain.tld
Problem is that if the port is blocked you are redirected to the local domain with https.
So without the port there is no proxydomain for the hostdomain which would use the wildcard ssl cert.
That situation is unchanged for years.
What missing is a way to redirect to a account which just provides proxydomains covered by the wildcard cert of the host.
Since the same problem is with cpanel webdisk etc. I wonder why nobody seems to have a problem with this. Are customers eager to pay for their own ssl cert but to get told EXIM,Courier,Dovecot are not accessible via your cert. You have to use the host cert.
Accessing controlpanel and webmail without special ports is important. SSL a must. If you get your customer to pay for a cert they don't want to use or remember a different domainname as mailserver.
The current situation is incoherent in more than one way.
Subdomains are not able to use SSL. See feature request
http://features.cpanel.net/response...ain-to-hostname-instead-of-origin-domain-name
But since EXIM,Dovecot,Courier are not currently able to use customer domains as proxy with certs of customers it is a long way to go. To provide a way to access webmail via standardport and SSL via a wildcardcert of the host looks like a shorter way to get a least one way consitent.
http://forums.cpanel.net/f5/ssl-acc...96-signed-wildcard-hostservercert-227211.html
When using e.g. www.customermail.tld/webmail you can get a screen:
"Connection Selection ..."
If you are not behind a firewall that blocks port 2096
Enter Here https://host.whmdomain.tld
If you are behind a firewall and can not connect to port 2096
Enter Here https://webmail.customerdomain.tld
Problem is that if the port is blocked you are redirected to the local domain with https.
So without the port there is no proxydomain for the hostdomain which would use the wildcard ssl cert.
That situation is unchanged for years.
What missing is a way to redirect to a account which just provides proxydomains covered by the wildcard cert of the host.
Since the same problem is with cpanel webdisk etc. I wonder why nobody seems to have a problem with this. Are customers eager to pay for their own ssl cert but to get told EXIM,Courier,Dovecot are not accessible via your cert. You have to use the host cert.
Accessing controlpanel and webmail without special ports is important. SSL a must. If you get your customer to pay for a cert they don't want to use or remember a different domainname as mailserver.
The current situation is incoherent in more than one way.
Subdomains are not able to use SSL. See feature request
http://features.cpanel.net/response...ain-to-hostname-instead-of-origin-domain-name
But since EXIM,Dovecot,Courier are not currently able to use customer domains as proxy with certs of customers it is a long way to go. To provide a way to access webmail via standardport and SSL via a wildcardcert of the host looks like a shorter way to get a least one way consitent.
Last edited: