I'm trying to install a SSL on my EC2 instance but I'm having issues.
I've uploaded it via CLI, and when I do list-server-certificates I see that it's been installed correctly.
But when I check the SSL info, it still shows the info from the old expired certificate.
Does anyone know what step I might have missed?
Related
I recently installed a new self managed certificate on the Google Cloud Platform. This is be cause the old one was out of date. I believe that I have done this correctly.
sgnapper#cloudshell:~ (tactical-curve-284112)$ gcloud compute ssl-certificates list \
--global
NAME: eris-sypro
TYPE: SELF_MANAGED
CREATION_TIMESTAMP: 2022-06-23T06:32:33.689-07:00
EXPIRE_TIME: 2023-06-22T16:59:59.000-07:00
MANAGED_STATUS:
Yet I get:
Your connection isn't private
Attackers might be trying to steal your information from syproltd.co.uk (for example, passwords, messages or credit cards).
NET::ERR_CERT_REVOKED
When I try and connect to the site.
I am not familiar with Google Cloud and I wonder if there is a step I have missed.
If anybody can help, I would be grateful.
gcloud compute ssl-certificates create does not automagically provision the SSL certificate to any services, but only adds it to the infrastructure. NET::ERR_CERT_DATE_INVALID expired 9 days ago. And the new one likely isn't provisioned to the load balancer. This is being explained here: Step 3: Associate an SSL certificate with a target proxy. When the certificate is installed on a VM instance (no load balancer), you may run gcloud compute ssl-certificates delete eris-sypro --global and instead replace the SSL certificate installed on the VM instance.
I've installed bitnami WordPress on GCP and issued SSL certificate via SSH. and was everyting ok till today.
Could anyone help and advice..
what shall I do
https://www.careersar.com/
Thank you
Remaz
I have a client site set up on AWS with multiple servers running HTPPS behind an Elastic Load Balancer. At some point, someone from the client's team attempted to update the SSL Cert by installing a new one directly on one of the servers (instead of in the ELB).
I was able to upload a new cert to the ELB, but when traffic is directed towards the server with the improperly installed cert, it triggers a security warning.
No one can seem to answer who attempted this install, how they went about, or where they installed it.
What's the best way to go about finding and removing it?
Thanks,
ty
If it's installed on the server, it has very little to do with AWS. I see you tagged the question with apache so I assume the server is running Apache Web Server. You will have to connect into that server and remove the SSL settings from the Apache Web Server configuration, just like you would with an Apache Web Server install anywhere else.
I've setup and been managing a Puppet (enterprise 2016.1) instance with over 50 nodes. PE console uses self-signed certificate (https://<fully-qualified-domain-name>/) which is starting to get flagged down by the security audits and forcing me to update the cert. I'm trying to overwrite the self-signed certificate with a CA cert and also do a DNS binding so the URL is more user-friendly. I tried to follow Puppet article here (https://docs.puppet.com/pe/latest/custom_console_cert.html) but it broke my environment and made the console inaccessible. It's since been recovered using Azure backup.
If anybody ever carried out this activity, please would you let me know how I can go about it? Thanks.
I'm not the most advanced AWS user there is, and have come across a bit of a roadblock.
I've got 2 Elastic Beanstalk Environments, each with a Load Balancer, 2 EC2 instances and they share a RDS instance. One environment is for Development and the other for Production.
I have purchased a wildcard SSL certificate from Thawte, and would like to install it on both the Development and Production environments. I've gone through other threads about adding SSL certificates in AWS, but the admin interface has changed since they were written so I've been going round in circles trying to figure it out.
Also, do I install the same SSL certificate on both Load Balancers? Or is it a case of only having one load balancer and redirecting traffic depending on the domain?
Thanks
You will need two load balancers, one for each environment. For uploading the certificate, it sounds like you are creating your Beanstalk environment through the console. In that case, after you create the environment, go to the EC2 tab, then 'Load Balancers', then 'Listeners'. Edit that, change the protocol to https. You'll see there is a place to change the certificate:
That will give you a place to upload the certificate:
Now that the cert is there, you can use the Elastic Beanstalk configuration to change future environments to use that cert: