SSL with subdomains, wildcard problem

[vivekan]

Hello community of CWP,

I am new user of this software. I am not so much experienced user, so do not judge me if i have silly question.

Problem that i have met useing at the moment this software was mainly as for installing SSL and specifically wildcard ssl with option of keep sub-domain on ssl.

Example:

my website is:  www.example.com
and my sub is: cp.example.com

I want both of them to be SSL secured, when i apply for SSL certification company of SSL request from me application in style like

*.example.com

So it can include all subdomain for ssl.

Problem comes when i am trying to create a request, i generate the codes over
Security > SSL Generator >

Common Name [Domain] : *.example.com
Country: Code of my country
State: State of my country
Locality Name [City] : My City
Organization Name: Organization of my company
Organization Unite Name: Same as previous
Email Address: my email of the domain
Valid Days: 365
Key size: i prefer the defaults 2048.

Sincei get the 2 codes, request and key.

I am going to

Apache Setting > SSL Cert Manager > Install SSL Certificate

Certificate: *.example.com
user: user of the domain
Path: Path of the website
Domain: [here is the tricky part] if i add it as "example.com" it will take it without any problem
if i add *.example.com [it wont take it either but will crash my Apache.] and then i will need to fix all the problems that come with the "asterisc problem"

Still have not managed to do it proper, should i leave it without asterisk? or what ?

[adrianofnatal]

Hi!

Im facing this problem too. It creates a file started with *.yourdomain.com.crt, but this *. have problems with linux filesystem.
Does anyone has installed a Wildcard on CWP before?

[adrianofnatal]

I think if you not use * in domain, when you generate a CSR, the ssl seller won't understand as Wildcard certificate, because there is no *. in domain.

In filesystem, some links was created wrong, I think.
Why dont replace the *. part of file by *-, fo example? This should work.

Another hint is to create a option to upload certificate, like cPanel do.

[studio4host]

or simply rename all your certificate files (crt, key and bundle) and install it for every domain/subdomain you need.

example:
rename: *.example.crt to wildcard.example.com

command example

Code Select Expand

mv \*.example.crt wildcard.example.com

... do the same for other files also

[adrianofnatal]

Yes, sure it works!

But is interesting that pannel do it automatically. How we can tell to developers about this issue?

[studio4host]

you can report any issue by using website contact form
http://centos-webpanel.com/contact