SSL certificate(Virginia region ) not working - apache

Hi Everyone I am using aws Ec2 instance for magento site and trying to install ssl certificate .I have get issued ssl successfully using ACM and its showing status deployed but when i use https for domain, its not working with error "This site can’t provide a secure connection".here is the screenshots
Questions: Is there need to configure apache too?
SSL is issued in Virginia region.
Please anyone help & guide me for the same.Thanks a lot

Related

cloud run, custom domain, and ssl termination

I'm using cloud run behind a load balancer. However, it's simply a passthrough that performs ssl termination of my own certificate and exposes the cloud run service(s).
I read this and thinking of trying it out.
https://cloud.google.com/run/docs/mapping-custom-domains#run
In the Firebase docs, it says:
"After we verify domain ownership, we provision an SSL certificate for
your domain and deploy it across our global CDN within 24 hours after
you point your DNS A records to Firebase Hosting.
Your domain will be listed as one of the Subject Alternative Names
(SAN) in the FirebaseApp SSL certificate. "
For Cloud Run, it says something similar. It will generate and manage my SSL certificates. Does anybody have experience with this?
Will this newly generated certificate invalid my current cert? I assume so, and that's ok. I'm only using cloud run for subdomains like api-prod.example.io for my API and app-prod.example.io for my frontend nginx static webserver.
Is their any other considerations of why I should not move over? If I do move over, should I do Firebase instead? I supposed it's:
Firebase + Cloud Run
vs
Cloud Run
vs
GCP LB + Cloud Run + Own Managed Certificate (Current)
Thanks in advance!

GCP managed SSL certificate stuck at FAILED_RATE_LIMITED?

I am trying to issue a SSL certificate for my loadbalancer, which serves traffic to an application hosted on GKE cluster in the backend. I have reserved a static IP for the loadbalancer, and I am able to access the application over HTTP.
Early this week, I had managed to generate SSL certificates and attached it to the load balancer using the GCP managed SSL certificates, and my domain was working on HTTPS network. However I had to delete the loadbalancer and launch it again using the Kubernetes Ingress. But now I am not able to apply the certificates to the loadbalancer. The certificates fail to provision with the error: FAILED_RATE_LIMITED.
Now I have deleted all the previously generated certificates on my account, and there is a single certificate now. According to the error, I have exhausted the number of GCP managed SSL certificates on my account. But I have deleted all the previously generated certs and I have almost waited for 10-11 hours, but the issue still exists. Is there a solution to this?

How can I make my HTTP website become HTTPS?

I have a website called http://jobdirecto.com/ that I want to turn into HTTPS.
The site is hosted in Heroku and the domain I got from Namecheap.
I got the paid version of Heroku since that lets me configure the SSL (and I think that's what I have to configure to make it HTTPS). They ask me for a "public certificate" that I don't have though.
I also bought a SSL from SSLs.com and they gave me a private key but no public certificate.
I am lost in what I have to do now to make my website secure.
There's no need to purchase anything. Use Heroku's Automated Certificate Management, which is powered by Let's Encrypt:
Run heroku domains and make note of the .herokudns.com domain it lists
Set up a CNAME record for your custom domain pointing to the .herokudns.com domain from the previous step
Run heroku certs:auto:enable to start the certficate provisioning process
Run heroku certs:auto to see your certificate's status
Please note that
It usually takes between 45 and 60 minutes to generate a TLS certificate for your app’s custom domains
This will let your site run over HTTPS, but it won't automatically redirect requests from HTTP to HTTPS. To do that we'll need to know more about your application.

Working with let's encrypt ssl certificate and OVH VPS

I'm trying to set up https connection in one of my API.
I normally make requests to my API through this address: http://vps234602.ovh.net:8090
I'd like to be able to make https requests.
I tried to make a redirection in OVH panel, from api.uphair.fr to http://vps234602.ovh.net:8090.
Then I used the zerossl certificate wizard to build the certificate.
In the "domains" field, I typed
www.api.uphair.fr api.uphair.fr
Then I builded the certificate and the DNS verification went well (I was able to add new TXT entries in my DNS zone according to what zerossl was asking).
Then I followed the steps to add this certificate in IIS for my API.
When I'm trying to connect to https://api.uphair.fr the redirection is good but I got the error:
:ERR_CERT_COMMON_NAME_INVALID
I did this for another site in IIS, https://partenaires.uphair.fr and it works well.
Does Anybody know what I'm missing here ? Do I just have to wait for the DNS propagation ?
Thanks for your help.

Getting ssl certificate issue

I have a site which is hosted using godaddy and heroku and it has issued SSL certificate fro the godaddy.
Right now I am facing issue as, I (including all my friends and family) can see site very well (It means I can see green color HTTPS on the address bar.)
But for my client getting the SSL error(red cross on HTTPS).
First I thought SSL certificate is not properly installed so I online check the SSL certificate error. For this I used following sites
https://www.sslshopper.com
https://www.digicert.com
but all the sites showing that the certificate is perfectly issued and applied.
Can any one please help me what is actual cause behind this. Is there any firewall issue. Please let me know your thoughts.