Free SSL (sort of)

[slips]

Someone may want to clean this post up and "sticky" it.

After creating my SSL to make cp secure (https://cp.mydomain.com:8443), I was contemplating if I should spend the extra money to make my base domain secure.

On a hunch, I created a Subdomain of cp.mydomain.com, used the same SSL cert I created for H-Sphere, and dropped my control panel custom images and secure information pages into that subdomain.
Since it calls up on port 8080 by default there is no conflict with the H-Sphere call-up on port 8443.

So now that I have cp.mydomain.com secured I can just do redirects when I want to deliver secured content to my customers.

The H-Sphere is secure, the subdomain cp.mydomain.com is secure all with one SSL cert.

Under the no free lunch policy, you have to use one control panel and one dedicated IP for cp.yourdomain.com.

Did all that make sense to anyone, or do I need to rewrite it?

Well, technically, things may break. The control panel IP and the subdomain IP are different, so in effect, you've created two A records for 'cp' with two different IPs... May or may not work well :/

[slips]

hmmm, it's working for me but maybe you should pull this post before someone screws up their settings and you all blame ME for making more work for tech support......... :tongue: