Confused about SSL with a Ghost Cms on Digital Ocean
Hi, I spent today setting up and integrating a single click droplet of ghost.
However, I've run into problems as my droplet doesn't have an SSL certificate.
I use AWS for most of my work. I created an SSL certificate using the certificate manager and added it to Route 53 record. Which then points to the ipv4 of the ghost droplet.
Is this correct or am I missing something? Because it still says site is insecure.
Is AWS proxying connections to your DO droplet?
I have a super simple setup: My domains points to a DO droplet. I run nginx on the droplet and have LetsEncrypt certificates auto-setup/renewed. nginx on my droplet reverse proxies to apps on the instance (non-encrypted).
It sounds like you have something installed to load balance/proxy requests that has SSL enabled, but you need to point your DNS records at that instead of your droplet. If you're just pointing DNS directly to your droplet, you need SSL setup on the droplet itself.
But the info in your post is a bit lacking, so I'm pretty sure I'm not understanding your setup fully :)
Hi @AndrewV I was being an idiot.
Thank you for the explanation!
I ended up using LetsEncrypt.
My mistake was not pointing the DNS A record in Route53 to the digital ocean droplet.
Thanks for the help.