I own a domain name from godaddy.
Now, I want to host the domain with SSl support.
Is it possible to get hosting and ssl certificate from two different vendors and then integrate them with my domain as i am going to have shared hosting.
Please check answer here
https://serverfault.com/questions/405750/godaddy-ssl-on-shared-hosting
Yes, you can buy domain name and SSL from two different vendors.
Note: Please must mentioned the exact domain name when buying the SSL certificate.
Please check the following also,
http://www.webhostinghero.com/install-godaddy-ssl-certificate-on-cpanel/
Related
this one is driving me mad - hopefully anyone of you can help.
I ordered a cloud server with intention of running multiple customer sites on one server/one ip. Everything is working fine so far, but Im having troubles with SSL.
I added 2 Domains (Domain a, Domain b) via Plesk Panel and installed basic ssl certificates which are working perfectly fine. Both Domains can be accessed via https:// and in the broswer both certificates are shown as valid / secure
Problem: Im getting SSL Issues / Warnings when connecting to the domains mailboxes -> to secure the Plesk Panel a self-signed Certificate was pre-installed.
When I exchange the Plesk self-signed certificate to a certificate for Domain a, Domain a mailboxes are working perfectly fine - but not for Domain b. (obviously). What certificate do I need to install to secure the Plesk Panel and which does not cause any problems with all underlying Domains & their mailboxes?
Will creating a certificate for the servers IP address will do the trick? Is this accepted, even possible or will it result in another warnings? If yes, do I need to create a certificate for xx.xxx.xxx.xxx or xx.xxx.xxx.xxx:8443?
Or is there any other option for running multiple domains on one shared ip?
Any help/guidance is very much appreciated!
Thanks!
Did you mean something like mail.domainb.com or autodiscover.domainb.com for mailbox? Then make sure you have valid SSL certificate for them also not only for mail domain. As far as I know you would not be able to get third-party certificate on IP addresses.
Sorry if I have guessed wrong.
There seems to be two places in PLESK to add SSL certificates. One location is under Domains
and another under Tools and Settings.
What is the purpose of the first versus the second location?
Both locations in PLESK (v12) accomplish the exact same thing. The one added benefit to adding the SSL under the domain name is accessing the IP address via HTTPS (answer from hosting company).
I hope it helps someone in the future.
I have a https web app running on my aws ec2 instance.
https://ec2-52-91-100-69.compute-1.amazonaws.com/
I need to get a ssl certificate for the same so that the scary warnings do not appear.
How can I do this? I tried to buy a ssl from clickssl.com but their helpdesk emailed me with the following:
"You completed enrollment process for domain name
ec2-52-91-100-69.compute-1.amazonaws.com.
I believe you cannot get SSL for this domain name because root domain
name amazonaws.com is Amazon property."
If this is the case is there no way to get a ssl certificate for my application? I dont believe thats the case.
Any help will be appreciated.
First you need to register a domain through a registrar (e.g. GoDaddy or Amazon Route 53). Next you assign an Elastic IP to your EC2 instance and use your registrar's DNS tool to make your domain point to the Elastic IP address. Then you can request an SSL certificate for your own domain.
You do need to register a domain, or use a subdomain of a domain you already have registered. You do NOT need to use an Elastic IP - they are limited and eventually (if you use multiple domains in your AWS account) you will run out. Instead, you can use a CNAME to point to the AWS name (e.g., ec2-52-91-100-69.compute-1.amazonaws.com).
Once you have that set, use Let's Encrypt to get a free widely accepted certificate. There are plenty of tutorials on the installation process - try:
https://ivopetkov.com/b/let-s-encrypt-on-ec2/
Just noticed the original question is OLD - which means (among other things) that Let's Encrypt wasn't even an option at the time. But for anyone who stumbles across this question now, it is a great solution.
I am using a VPS which doesn't host any website, or domain name. I need to remote-access that VPS using Remote Desktop.
To be sure no one is eavesdropping my traffic with the VPS, I need to setup an SSL certificate on the server. But the first thing they ask is a Fully Qualified Domain Name. Is there any way I can skip creating a domain that I don't need in order to buy the certificate? Since I will only need it for my remote desktop sessions?
Here are the facts:
1- You need a fully qualified domain name to request a certificate.
2- You don't have to bind the domain to the server in case you don't want to.
3- After installing the certificate, if the server address is not the same as the domain associated with the certificate, you will get a warning that the address doesn't match the certificate.
Hope this will help anyone who has case similar to mine.
Maybe it is just impossible but I have the following question :
I own an domain for example : mydomain.com . On that domain I take a wildcard SSL. So far no problem. And that domain is running on a server with online software on a sub domain for example soft.mydomain.com.
Now I have customers for that software, and I want to customize the software to their subdomains for example soft.customer1.com and soft.customer2.com.
I can do this by letting them make a DNS A record pointing to my servers IP and I park then the domains onto my subdomain soft.mydomain.com (Tested that and it works).
The question is now : Can I also take a SSL certificate on soft.customer1.com and soft.customer2.com. So that at least I also have a secure connection when for example soft.customer1.com/login.php is used.
If possible who has to request the actual SSL certificate in that case.
Also I have full access to WHM and cpanel, running a VPS.
I understand that I could use customer1.mydomain.com/login.php , but I wonder if it just would be possible to do what I suggest.
And also it recommended to work in this way ?
Thanks upfront.
Regards,
Peter
Different domains can exist on a single SAN/UC certificate. Take a look at http://www.ssl.com/certificates/ucc to learn more about this certificate type.
It sounds like you have all the pieces except for this particular certificate. I hope it helps.