Welcome to WebmasterWorld Guest from 54.158.165.135

Forum Moderators: bakedjake

Message Too Old, No Replies

requirements for a wildcard SSL cert

   
11:33 pm on Apr 4, 2011 (gmt 0)

WebmasterWorld Administrator httpwebwitch is a WebmasterWorld Top Contributor of All Time 10+ Year Member



I have a wildcard SSL certificate for one of my sites. So, it offers SSL happiness for all the subdomains of *.example.com

The site is currently on a VPS with about twenty other sites I own.
I'm working on migrating them all to a new server.

Back when the support crew at my current host set up the wildcard domain, they said that for it I'd need a dedicated IP. OK so mote it be. Now it's on a dedicated IP, and that's never a bad thing.

They also explained that to make it work, they had to create a new Linux User for it. So while all my other sites are hosted in /home/myusername/public_html/*, this one site with the wildcard is hosted in /home/example.com/public_html

Was that really necessary?

I mean, since I'm setting up this new server, do I need to do the same thing?
11:39 pm on Apr 4, 2011 (gmt 0)

WebmasterWorld Senior Member wheel is a WebmasterWorld Top Contributor of All Time 10+ Year Member



I'm pretty sure the answer is no, you don't need to do that. I've never set up a wildcard, but I've set up others. All it takes is the cert file located somewhere on the server, and then tell apache where the cert file is located.

Unless there's something unique about wildcard certificates.
7:08 pm on Apr 5, 2011 (gmt 0)

WebmasterWorld Administrator httpwebwitch is a WebmasterWorld Top Contributor of All Time 10+ Year Member



That's what I'm interested in knowing: is there something unique about wildcard certificates.

I suppose I'll just keep the site in /var/www/* with all the others, install the certificate, and see if it works.

the live site www.example.com is over on server A, but I've created a DNS entry for test.example.com that points to server B - I am assuming the wildcard certificate will work over on server B because it's hosting a subdomain of example.com

this is all pretty new to me. All the webmastery I've done on LAMP in the past has been managed with CPANEL and WHM, whereas now I'm forcing myself to learn how to administer all of this via Linux CLI