Hi all...I was hoping to find out a little more about installing an SSL cert to secure a site I'm developing with https. From what I've read, the Go Daddy hosting package my client's site is on does not have a dedicated IP address, and such a dedicated ip is necessary - can this be resolved, and if so, how?
Thanks for any advice anyone can offer, it will be most appreciated! 🙂
Solved! Go to Solution.
@woodson You do not need a Dedicated IP to install an SSL Cert. The SSL Cert can be a self signed cert as the site is under development. You will get an error every time you try to connect but you can still access the site securely. Once site is out of development you will need to install a valid SSL Cert if you plan on allowing secure access to your site.
Here are the basic steps to get an SSL for the site
2. If the domain is not on your account you may need to Generate a CSR (certificate signing request)
Once the cert has been issued you will need to Install SSL certificate
When accessing a site using a secure connection (HTTPS) the cert is only used to encrypt the communication. The Domain, Cert signing, Revocation, and other stuff are primarily used in determining trust.
@oslinux Many thanks for your detailed response, really appreciate it.
So, just to confirm, even though the live site is on a shared server (and hence no dedicated IP) you are saying this won't be an issue when I go about setting up the SSL (don't need it yet, until I've added login functionality that I actually want to be secure)?
Hi, I'm trying to install an SSL on Plesk, but when downloading the options are "Apache, IIS, Other", the answers i've seen have a plesk option. What server should i choose?
I have received a email regarding SSL certificate. Can someone please tell me how this can be done. In the form provided to fill there are many fields which I don't know what to write. Will appreciate any help on this.
I am talking about below form:
When generating a certificate signing request, we can send a copy of the generated self-signed certificate, the private key and the certificate signing request. Depending on your mail service provider, your mail may be sent over an insecure channel. We do not recommend sending private keys if the email service provider you use does not support secure mail via SSL/TLS.
Private Key Options
When the system generates a self-signed certificate and CSR, the system also generates a new private key for the certificate and CSR. To protect the certificate, this key must be confidential. Do not send the private key through an insecure method.
4,096 bits Certificate Information
The information provided below is used to create a self-signed certificate and the corresponding certificate signing request. Since this is the information that users will see when they access a site via SSL, it is important to provide accurate and valid information.
Some certificate authorities may require CSRs to have a passphrase. The certificate authority can use a CSR passphrase to confirm the identity of the person or organization with whom you wish to communicate. CSR passphrases are stored unencrypted in the CSR. Because of this, and also because you will share this passphrase with a third party, do not use an important password here.