Keywords: Ghost - AWS - Technical issue - Domain Name (DNS)
bnsupport ID: 98a7e782-d22f-c645-bbb7-bbcd17d79e94
I’ve installed Ghost 3.0.2 in AWS EC2 using the latest Bitnami AMI. Everything is good configured URL with ghost config URL, got SSL up with Bitnami cert tool, etc. I am using a VPN and the instance has an elastic IP as public IP and a private IP, 10.0.x.y.
The problem is that ghost uses private IP of the instance, 10.0.x.y, when posting, “view post” wants to open http:/10.0.x.y/post-name. This fails since the public IP is the elastic IP assigned to the instance.
I spent some time poking around apache2 directory and ghost one and don’t see the private IP hardcoded anywhere. How does ghost determine the URL for “view post” link after publishing, and how can it be fixed? Same is with the View site from admin, shows nothing. It was also added in the navigation URLs in Design but I edited those.
The blog is visible on public IP and editing works. So the private IP is getting some use somewhere. I see localhost and 127.0.0.1 used in config.production.json for talking to node. ifconfig is showing the private IP of course. There’s an alias updateip pointing to bnconfig on Birnami, which was renamed bnconfig.disabled but I renamed it back. So where is the private IP found and used?