Wildcard SSL problem

[alpiroom]

hi,
my server using cPanel Build 10.9.0-STABLE 119 Theme cPanel X v2.6.0
and Apache version 1.3.37 (Unix)
and i buy wildcard SSL from godaddy. in my cpanel
ssl manager > Certificate Signing Requests (CSR) menu i am generating csr but godaddy didnt like my csr and error is " when generating a csr for a wildcard certificate, please add asteriks (*) on the left side of the common name (e.g. "*.domainnamegoes.com") " but in cpanel csr menu havent got any domain naim input it have got only domain name option menu (drop down menu) what can i do
please help me

[cpanelnick]

hi,
my server using cPanel Build 10.9.0-STABLE 119 Theme cPanel X v2.6.0
and Apache version 1.3.37 (Unix)
and i buy wildcard SSL from godaddy. in my cpanel
ssl manager > Certificate Signing Requests (CSR) menu i am generating csr but godaddy didnt like my csr and error is " when generating a csr for a wildcard certificate, please add asteriks (*) on the left side of the common name (e.g. "*.domainnamegoes.com") " but in cpanel csr menu havent got any domain naim input it have got only domain name option menu (drop down menu) what can i do
please help me

You'll need to park *.domain.com first or generate the crt in whm.

[alpiroom]

hi,
how can *.domainname.com
cpanel giving thid error
"Error from park wrapper: The domain you have specified does not conform to domain name rules"

[cpanelnick]

hi,
how can *.domainname.com
cpanel giving thid error
"Error from park wrapper: The domain you have specified does not conform to domain name rules"

Sorry about that.. I should have said 'subdomain'.

[alpiroom]

i tryed but i took this error
"Error from domain wrapper: .crmbrc.com could not be modified because it does not resolve to a valid IP address. Please ask the system admin to check their resolv.conf and their dns trust relationship Ignore any messages of success this can only result in failure!"

i am thinking i must do differnt think.

[searchenginepro]

I am having an issue with https working properly on my subdomains.

I know I have purchased and installed *.wildcard.com correctly, but when I enter an https://subdomain.domain.com it displays the index page for https://domain.com

I generated SSL for *.domain.com as outlined in several other forums, but installed in WHM as domain.com and then applied same crt / key to subdomain.domain.com - Everything applies fine with no errors, but index page for each subdomain will not display.

[skina]

I am getting the same problems as searchenginepro, any ideas?

[Polyack]

Did you purchase the following domain: *.mydomain.com ?
Or did you purchase a a wildcard certificate for the following domain: *.mydomain.com?

In case you're trying to make a wildcard certificate manually, I'm experiencing the same issue.

This seems to be an issue with WHM 11.

The following thread states this problem. In that thread they also mention that the hosting provider had to do some "manual changes". I'm wondering what these changes are. Anyone knows?
Any alternative workarounds that don't require unique accounts and IPs?

"Ref: http://www.jaguarpc.com/forums/showthread.php?p=135507

Yes that is weird. Jag support have been in touch with cPanel support and have now reached the conclusion that the only way to get a wildcard certificate working is to create the 'subdomains' as stand-alone accounts (so they aren't subdomains at all), dedicate an IP to each, manually create the entry and then rebuild Apache. That's convenient then.

It is now working, but support had to make changes manually. We no longer have subdomains, however - each 'subdomain' has to have it's own account and dedicated IP. Below is support's 'how to' guide:

1.
Copy the file for one of already installed certs e.g. in this case I copied file '/var/cpanel/userdata/myusername1/mysubdomain1.mydomain.net_SSL' to '/var/cpanel/userdata/myusername2/' .

/var/cpanel/userdata/ is the path where each account has a folder with its apache and cpanel configuration files. The _SSL file is the one which contains the entries for ssl vhost for any domain.

2.
Rename that according to subdomain i.e. in this case rename '/var/cpanel/userdata/myusername2/mysubdomain1.mydomain.net_SSL' to '/var/cpanel/userdata/myusername2/mysubdomain2.mydomain.net_SSL'.

3.
Edit the file '/var/cpanel/userdata/myusername2/mysubdomain2.mydomain.net_SSL' and update user name to myusername2 where there is old username and update IP, viewing this file will clear any confusion.

4.
Run : /usr/local/cpanel/bin/build_apache_conf
to rebuild apache configuration from the newly created file.

5.
Then restart apache to make it load newly built configuration."

[Polyack]

I'm experiencing issues when creating Wildcard SSL Certificates on my VPS. The VPS runs WHM 11.

I've heard that it can't be done using the WHM-GUI and must be done using the command-line.

However there are still some issues appearing after creating the
the Certificate in the SSH-commandline.

The following thread states this problem. In that thread they also mention that the hosting provider had to do some "manual changes". I'm wondering what these changes are, since I have to apply this changes as well. Anyone knows?
Any alternative workarounds that don't require unique accounts and IPs?
"Ref: http://www.jaguarpc.com/forums/showthread.php?p=135507

Yes that is weird. Jag support have been in touch with cPanel support and have now reached the conclusion that the only way to get a wildcard certificate working is to create the 'subdomains' as stand-alone accounts (so they aren't subdomains at all), dedicate an IP to each, manually create the entry and then rebuild Apache. That's convenient then.

It is now working, but support had to make changes manually. We no longer have subdomains, however - each 'subdomain' has to have it's own account and dedicated IP. Below is support's 'how to' guide:

1.
Copy the file for one of already installed certs e.g. in this case I copied file '/var/cpanel/userdata/myusername1/mysubdomain1.mydomain.net_SSL' to '/var/cpanel/userdata/myusername2/' .

/var/cpanel/userdata/ is the path where each account has a folder with its apache and cpanel configuration files. The _SSL file is the one which contains the entries for ssl vhost for any domain.

2.
Rename that according to subdomain i.e. in this case rename '/var/cpanel/userdata/myusername2/mysubdomain1.mydomain.net_SSL' to '/var/cpanel/userdata/myusername2/mysubdomain2.mydomain.net_SSL'.

3.
Edit the file '/var/cpanel/userdata/myusername2/mysubdomain2.mydomain.net_SSL' and update user name to myusername2 where there is old username and update IP, viewing this file will clear any confusion.

4.
Run : /usr/local/cpanel/bin/build_apache_conf
to rebuild apache configuration from the newly created file.

5.
Then restart apache to make it load newly built configuration."

[daveformerlyof]

Please update cPanel. You can add *.domain.com certs without adding a wildcard subdomain in the latest versions:

Stable 24255
2008-05-09 11:08:03

Fixes
Allow installation of wildcard SSL certs onto matching non-wildcard virtualhosts

Current 24083
2008-05-06 06:24:35

Allow installation of wildcard SSL certs onto matching non-wildcard virtualhosts

[jdlightsey]

As Dave said, installing a wildcard cert on a non-wildcard subdomain was recently addressed.

If you're wanting to install two subdomains using the same cert though, you will run into the problem of cPanel/WHM only allowing a single SSL VirtualHost per IP address. I believe that's what JPC was working around with those extensive changes.

You can accomplish the same thing in a much easier fashion by creating a SSL wildcard subdomain *.domain.com and using mod_rewrite to serve files from the correct subdirectory based on the subdomain name.

[cpanelnick]

Note: Threads Merged

[Polyack]

As Dave said, installing a wildcard cert on a non-wildcard subdomain was recently addressed.

If you're wanting to install two subdomains using the same cert though, you will run into the problem of cPanel/WHM only allowing a single SSL VirtualHost per IP address. I believe that's what JPC was working around with those extensive changes.

You can accomplish the same thing in a much easier fashion by creating a SSL wildcard subdomain *.domain.com and using mod_rewrite to serve files from the correct subdirectory based on the subdomain name.

If I understand correctly, does this mean that using that method will remove the need of a unique account and IP for every subdomain that are to be protected by the wildcard SSL certificate?

Do you have an example of some mod_rewrite code that you can confirm works?

[brondsem]

I am running WHM 11.15.0 cPanel 11.18.6-R24654 but I'm getting this error, too. In WHM, I go to "Install a SSL Certificate and Setup the Domain", paste in my cert, change the domain to "sample.cornerstone.edu", and set the IP address, but it gives me this error:

Attempting to verify your certificate..... Cerificate verification passed!
Verifcation Result [/C=us/ST=Michigan/L=Grand Rapids/O=Cornerstone University/OU=Information Systems/CN=*.cornerstone.edu]
The supplied certificate does not match the specified domain
SSL Install aborted due to error.

[jdlightsey]

Do you have an example of some mod_rewrite code that you can confirm works?

I have a *.lolkitten.cat subdomain with a wildcard SSL cert and a document root of /home/lolkitte/public_html

I have aaba.lolkitten.cat subdomain with a document root of /home/lolkitte/public_html/aaba

So I want the https://www.lolkitten.cat to go to /home/lolkitte/public_html and https://aaba.lolkitten.cat to go to /home/lolkitte/public_html/aaba

I can accomplish that with these mod_rewrite rules in /home/lolkitte/public_html/.htaccess

RewriteCond %{SERVER_PORT} ^443$
RewriteCond %{HTTP_HOST} ^aaba\.lolkitten\.cat$ [NC]
RewriteCond %{REQUEST_URI} !^/aaba/
RewriteRule ^(.*) /aaba/$1