Secure certificate for dedicated server

[smallwebsolutions]

Sorry, another dumb question from someone who is still trying to get a handle on all of the dedicated server requirements.

Do most of you have a secure certificate installed on your dedicated servers for global use (i.e., https://yourserver.com).

If so, I'm assuming that this would be so your clients can use a secure connection for email, etc.

Pros and cons for or against a secure certificate?

Thanks,

Jackie

[kobra]

A shared Cert, one that allows shared SSL for customers domains is a "WildCard SSL" and expensive. You can setup and use "Self Signed" certs and probably already have one or more as part of your configuration that were setup for you, for the internal secure sessions like SSH.

What a purchased cert is basically, is a cert issued by some trusted source and is paired with a level of insurance for fradulant transactions or the like.

A self signed is just as secure for data transmission just not from a "trusted" source nor "trusted" by shoppers

[smallwebsolutions]

If I bought a secure cert just for my server, i.e. server.myserver.net, I wouldn't need a wildcard cert for my clients to use the secure path of:

https://server.myserver.net/~accountname/

Or would I?

[kobra]

I am not configured this way and do not believe that you can have 2 certificates for the same domain/sub?? Maybe a ticket to H9 can get you an answer to this.

I run my portal/billing/support on a separate server for continuity reasons i.e. if a server goes down I still have my support portal up where clients can communicate and find out wht the issues might be (A lesson learned the hard costly way)