Bitnami AWS Ghost appliance behind Cloudfront - ghost config url directive redirects to 127.0.0.1

[phillhocking]

Keywords: Ghost - AWS - Technical issue - Secure Connections (SSL/HTTPS)
bnsupport ID: 78f6c099-d822-701b-9e5b-f44e8b88f48d
Description:
It appears that this appliance has difficulty behind Cloudfront as the ‘domain’ can only be set to an fqdn, not specifying http/https as the prefix. Whenever I use ghost config url https://phillhocking.com it wants to redirect to http://127.0.0.1:2368.

I understand this appliance is intended to allow for LetsEncrypt and running SSL natively, however, I need to be able to configure the base url for the Ghost install to be https://phillhocking.com even though the fqdn/Cloudfront origin is different from this.

How can I get the desired behavior for the Ghost installation to render pages that match the Cloudfront distribution so I don’t get mixed content?

[phillhocking]

Here is an example of the fault condition: https://imgur.com/a/d6v8Rdw

[phillhocking]

Hey @davidg I just saw you respond to someone else on a ticket, this has been open for days with no suggestions from Bitnami engineers so I figured I would ping you because I saw you were active. Do you have any suggestions?

[phillhocking]

@jota just figured I would ping you too? I haven’t gotten any Bitnami support on this particular issue.

[phillhocking]

This is the same issue occurring here, however, the steps are not remedying it:

How to get HTTPS working ( :80 & redirect loop issues resolved.) (Ghost/GCP)

Keywords: Ghost - Google Cloud Platform - How to - Secure Connections (SSL/HTTPS) Description: Here’s how to fix the HTTPS problems ( :80 and redirect loop) I spent some time troubleshooting a blocker that’s stopped me from using the Bitnami Ghost container in production. There are two issues after setting up your SSL certificate. You’ll notice your nav links have :80 appended to the end, and of course lack the S in https. First part - Fix Ghost URL Stop Ghost sudo /opt/bitnami/ctlscript.…

[fdepaz]

Hello @phillhocking,

Please keep in mind we offer support from Monday to Friday, so there may be cases where issues opened on Friday don’t get reviewed until Monday.

Regarding the use of ghost config url, are you restarting ghost afterward as such:

ghost config url https://yourdomain.com && ghost restart

Also, could you share a new bnsupportID with the updated changes you tried following?

Regards,
Francisco de Paz

[phillhocking]

a376c167-6adf-3df9-e720-88e7a0429437

I have been using sudo /opt/bitnami/ctlscript.sh restart to restart the services. I also used letsencrypt to ensure that ssl would work for the origin in case cloudfront was trying to hit it via ssl, but now it just redirects to 127.0.0.1:2368 regardless. I could hop on a Zoom or something if that’s helpful.

[fdepaz]

Hello @phillhocking,

We are sorry to tell you that we do not provide this kind of service. I have used a fresh ghost instance and was able to configure its domain and the use of https using our bncert-tool succesfully.

I have rechecked your site and it seems to be working properly, with the redirections in place and without any Mixed Content errors. Were you able to solve this?

Regards,
Francisco de Paz