SSL installation on both GoDaddy and External server - ssl

We have a wildcard ssl for *.domain.com purchased from GoDaddy. domain.com is a managed wordpress website hosted in GoDaddy.
We also have couple of servers where other websites are hosted as subdomains, api-client1.domain.com, api-client2.domain.com
Currently only subdomains are loading without any errors on https. The main domain is throwing a warning that SSL is expired, though its not.
In order to make sure that the domain and subdomain all load on https, is the below sequence of steps correct?
1) Ask GoDaddy to rectify the problem mentioning that https is not working.
2) After 1 is resolved, Create a CSR from external server, download the certificate from GoDaddy and install it in the external server.
Will the certificate installed by 1 revoked after 2 is done?

Related

How to generate SSL only for subdomain without add domain?

I am pretty new with the domain configuration part. I want to know that can I generate SSL only for my subdomain I didn't want to add the root domain with CLOUDFLARE because my root domain already has SSL certificate. Is it possible to do that? I have purchased my domain from the GODADDY. I will add the generated SSL certificate to IIS.
Please help me out !!
Edit: I don't want to add my root domain to CLOUDFLARE because if I will do it I have to change my NAMESERVER for the same and my root domain already has SSL.
I believe what you're looking for is the CNAME setup on Cloudflare. This is the alternative method of Name Server setup. However, this setup requires a Business plan. With CNAME setup, you can have just a certain subdomains to be used with Cloudflare. With proxy turned on the subdomain, you'd get the usual Universal SSL certification from Cloudflare.

SSL certicicate not working in cpanel

Im using hostgator as my host.They do not provide free ssl certificate.So im using cloudflare free ssl certificate for my site.SSL certificate working everywhere except Cpanel.
I tried manually adding ssl through cpanel option.But not really working!Is there any way i can add it there?
Or it will be really good if my cpnael url cpanel.site.com won't just show up to that address.
If you want to use the CloudFlare SSL certificate then there is no need to add that SSL certificate to yoru cpanel nor to your site. Read the cloudflare documentation in order to see how to create and use Page Rules and their SSL certificate. cPanel has nothing to do with it. CF works just fine with cPanel/WHM and pretty much with any other related hosting panel. Your site can be http only in cPnel and then you do the HTTPS redirection from Clouflare using their Flexible SSL and page rules
cpanel.yourdomain.com ssl is related to server side. If your host allow autossl with Let's Encrypt (for example) then it will install ssl for all your necessary subdomains like webmail, cpanel, mail, www etc. If you are installing ssl manually, then you cannot install it for cpanel subdomain. However if you want to use cpanel securely and have enabled ssl with yourdomain.com the you can use it:
https://yourdomain.com:2083

1and1 SSL Certificate with Heroku App

Could someone walk me through how to set up the SSL Certificate that I bought through 1and1 with my Heroku application and my 1and1 domain?
I am able to set it up and it stays active for a few minutes but then goes back to saying unsecured.
Let's call my domain harrison.com. I have a subdomain www.harrison.com. Let's say my heroku app is harrison.herokuapp.com.
What i'm currently doing is changing harrison.com to redirect to www.harrison.com and then changing that cname to harrison.herokussl.com which is currently not working.
Any help would be appreciated.
I believe that I have finally solved this.
I continued to redirect my TLD to the subdomain www, then then set the CNAME of the subdomain to www.my_app_name.com.herokudns.com. After that, I combined the server certificate (obtained from my DNS, 1and1), with the immediate certficate (also from 1and1) into 1 file with a .pem extension.
Finally, I uploaded the .pem certificate and the .key key to Heroku.

Forwarding https://example.com to https://www.example.com

Trying to get
https://example.com
To not refuse the connection, to show my website, and to redirect to:
https://www.example.com
Without having to switch my DNS hosting to DNSimple or adding another service provider.
My domain was purchased on GoDaddy. DNS is on GoDaddy as well, set up as shown below.
My app is hosted on Heroku, using a Let's Encrypt certificate, that I installed following this answer.
Currently using Helmet+express-enforces-ssl to force hsts.
I have read the following info:
Heroku SSL on root domain ; Heroku SSL Endpoints ; The Limitations of DNS A-Records
The last of which states:
(...) applications requiring SSL encryption should use the
ALIAS/ANAME configuration on the root domain. Subdomain redirection
will cause a browser error when the root domain is requested over SSL
(i.e. https://example.com).
Which seems to be my problem (?).
How do I set this up on GoDaddy?

Installing SSL for sub domain which pointing to another server

I have domain www.xyz.com with dedicated IP,SSL for www.xyz.com is already installed and working fine.
now through plesk panel i am able to create 10 sub domains.
I have created one sub domain named subdomain.xyz.com which is pointing to totaly different server.
I want to add SSL certificate for subdomain.xyz.com.
where i have to add SSL certificate, on the the server that sub domain is pointing or i can add SSL for subdomain.xyz.com from xyz.com plesk panel.
the subdomain is pointing to solaris server
You will need to install the SSL certificate on the actual server that is responding to your HTTPS requests (meaning, the one the subdomain points to). However, keep in mind that if you have a regular SSL certificate, then the certificate would have to be issued to the specific subdomain. For example, a regular SSL certificate for example.com does not validate against sub.example.com.
As an alternative, you can purchase a wildcard SSL certificate for your domain that will cover the new subdomain and any others you add later. More info on that here: https://www.digicert.com/wildcard-ssl-certificates.htm