So … I got the top site and put it on it’s on IP and setup the wildcard cert…
But where do I go from here…
It’s not a real sub-server for each need it’s own passwords… what IP would the other sites go on the same shared IP everyone else or SSL one ?
So a top level server on the shared IP or the one the SSL with the private IP. ?
So can you have more than one SSL site per IP … No … but all these have the same TLD so I just copy the ssl file from site to site ?
Then any thought on making how to really setup the sub-domain name setup…
First thought was made a link from /home/rocks/public_html/atlanta to the other user public_html folder… /home/atlanta/public_html … It looks like it almost works… Seems okay on html pages, scripts seems to have a permission problem… Makes sense it doesn’t work… but it was a thought…
So what the best way to make this mess… so I don’t need to go edit the httpd.conf file my hand to get it to work ?
Seems like every where I look, I just make more questions…
what IP would the other sites go on the same shared IP everyone else or SSL one ?
That’ll be up to you – but you can certainly put them all on the same shared IP, which would allow you to use a wildcard SSL cert with each domain on that IP address.
but all these have the same TLD so I just copy the ssl file from site to site ?
You don’t need to copy anything. If you have a domain on an IP that contains a wildcard SSL cert, just go into Edit Virtual Server -> Enabled Features, and enable the “SSL Cert” feature.
If I try to add Top severs to the SSL ip can not be done if IP is not shared… Try to share that IP …
Failed to save shared IP addresses : ‘209.235.xxx.xxx’ is a private IP address for virtual server …
Try to enable SSL on the site and get …
The following potential problems were detected with the modification of this virtual server :
SSL is being enabled for more than one domain on the IP address xxx.xxx.xxx.xxx. Apache on your system supports SNI, which will allow modern browsers to get the correct certificate in this situation. However, older browsers may see the first certificate for the IP, which is only valid for : mymainsite.com, www.mymainsite.com
SO is set it on the shared systems ip and the site works but no SSL … http://atl.somename.com works but the https://atl.somename.com give a ssl warning page and then shows the systems ssl website…
Failed to save shared IP addresses : ‘209.235.xxx.xxx’ is a private IP address for virtual server
That error means that the IP address is private, rather than shared. So long as it’s private, it can only be used for one Virtual Server.
So what you would need to do is first convert it to shared.
To do that, select the Virtual Server with the private IP address, go into Server Configuration -> Change IP Address, and click the “Convert Private Address to Shared” button.
Nope, it shouldn’t be hard at all once that IP is shared – so, convert the IP to shared, move your Virtual Servers to that IP, and then enable SSL on those Virtual Servers.