Site icon not using https but everything else does

I am running a new Ghost installation on an AWS Bitnami instance, so it is using the Apache web server. My site is https://kathrynhuxtable.org, but the DNS records were pointed to this instance today, so you may get my old site. If the first article isn’t about migrating my site, you got the old site.

I have an SSL certificate set up, which I did with Bitnami’s instructions. Everything works fine except that my site icon, which is in a sidebar, has src=“http://…” instead of src=“https://…”. Not sure why {{@site.icon}} in default.hbs delivers the full URL instead of /content/images/…

Looking at other people’s issues, I looked at my config.production.json, which had the url set to http://kathrynhuxtable.org, so I tried doing

ghost config set url https://kathrynhuxtable.org

This set it, but when I restarted everything, the site directed me to

127.0.0.1:2368

Palpable nonsense, as Eric Idle said.

I’ve been a professional software developer for 40 years, and I’ve been doing web programming for as long as it’s been possible, and I’ve set up Apache servers before. In the node world, I’m more familiar with Angular, but I think I see how this all works. (I haven’t dug into the Ghost source.)

Any ideas on what I can do? (Other than edit my default.hbs file to plug in a working URL, which I don’t want to do for obvious reasons.)

I’ll add that it seems like it must be the apache config rewrite rules.

Try changing url to use https in the file config.production.json.

Thanks. As I said above, I tried that, and the site broke. I suspect the apache configs at this point.

My apologies, I had not said I’d edited the file manually. I’d used the config tool. But I did try both, and both behaved the same.

This set it, but when I restarted everything, the site directed me to 127.0.0.1:2368

The default port for Ghost is 2368, and it is expected to run at 127.0.0.1:2368. You can use a reverse proxy to route requests from your domain to 127.0.0.1:2368.

Thanks, I’ll try that. My issue is pretty much the same as this one:

Problem solved! I found it on this stackoverflow. The answer about adding a line to the https vhost conf file

1 Like