Keywords: Ghost - AWS - Technical issue - Secure Connections (SSL/HTTPS)
bnsupport ID: 2eecb7fe-4bff-0633-724d-2be65477eabf
Description:
I have an AWS ec2 instance running ghost, and I am now trying to enable SSL.
This only allows me to post two URLs as a new user, so for the rest of this, {domain} stands in for "domain.com"
I have an amazon Elastic IP set up pointing at my instance. For DNS records: I have an A record pointing {domain} to the Public IP, and a C-NAME pointing www. {domain} to the Public DNS.
I have checked using whatsmydns that these records are set up correctly and have propagated to DNS servers.
I've ssh'd into my instance and am running bncert-tool. I get: "Warning: The domain 'www. {domain}' resolves to a different IP address than the one detected for this machine, which is {PUBLIC IP}."
From the command line (still over ssh): if I do "host {domain}" I get the correct Public IP. But if I do "host www. {domain}" it resolves the Public DNS to my PRIVATE IP. From my own computer (no longer ssh'd into the instance) I do get the PUBLIC IP for both {domain} and www. {domain}.
So it looks like bncert-tool might be seeing the addresses resolve to different IPs (maybe because the Public DNS resolves to the Private IP when bncert-tool is run on the instance).
How can I get bncert-tool to see {domain} and www. {domain} resolve to the same Public IP?
