# Site icon not using https but everything else does

**URL:** <https://forum.ghost.org/t/site-icon-not-using-https-but-everything-else-does/51669>\
**Category:** Self-hosting\
**Created:** [October 14, 2024, 11:25pm UTC](https://forum.ghost.org/t/site-icon-not-using-https-but-everything-else-does/51669 "2024-10-14T23:25:04Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![kahuxtable](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kahuxtable/32/32557_2.png) [@kahuxtable](https://forum.ghost.org/u/kahuxtable)\
**Post date:** [October 14, 2024, 11:25pm UTC](https://forum.ghost.org/t/site-icon-not-using-https-but-everything-else-does/51669/1 "2024-10-14T23:25:04Z")

</div>

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](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](http://kathrynhuxtable.org), so I tried doing

ghost config set url [https://kathrynhuxtable.org](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.)

---

<div class="post-metadata">

**Author:** ![kahuxtable](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kahuxtable/32/32557_2.png) [@kahuxtable](https://forum.ghost.org/u/kahuxtable)\
**Post date:** [October 14, 2024, 11:32pm UTC](https://forum.ghost.org/t/site-icon-not-using-https-but-everything-else-does/51669/2 "2024-10-14T23:32:54Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Raki](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/raki/32/40808_2.png) [@Raki](https://forum.ghost.org/u/Raki)\
**Post date:** [October 15, 2024, 12:07am UTC](https://forum.ghost.org/t/site-icon-not-using-https-but-everything-else-does/51669/3 "2024-10-15T00:07:25Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![kahuxtable](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kahuxtable/32/32557_2.png) [@kahuxtable](https://forum.ghost.org/u/kahuxtable)\
**Post date:** [October 15, 2024, 12:37am UTC](https://forum.ghost.org/t/site-icon-not-using-https-but-everything-else-does/51669/4 "2024-10-15T00:37:17Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![kahuxtable](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kahuxtable/32/32557_2.png) [@kahuxtable](https://forum.ghost.org/u/kahuxtable)\
**Post date:** [October 15, 2024, 12:40am UTC](https://forum.ghost.org/t/site-icon-not-using-https-but-everything-else-does/51669/5 "2024-10-15T00:40:40Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Raki](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/raki/32/40808_2.png) [@Raki](https://forum.ghost.org/u/Raki)\
**Post date:** [October 15, 2024, 1:12am UTC](https://forum.ghost.org/t/site-icon-not-using-https-but-everything-else-does/51669/6 "2024-10-15T01:12:27Z")

</div>

> 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`.

---

<div class="post-metadata">

**Author:** ![kahuxtable](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kahuxtable/32/32557_2.png) [@kahuxtable](https://forum.ghost.org/u/kahuxtable)\
**Post date:** [October 15, 2024, 1:16am UTC](https://forum.ghost.org/t/site-icon-not-using-https-but-everything-else-does/51669/7 "2024-10-15T01:16:46Z")

</div>

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

> [@HTTPS & Proxy problems on AWS Lightsail (Bitnami)](https://forum.ghost.org/t/https-proxy-problems-on-aws-lightsail-bitnami/40507/1):
>
> I’m running a self-hosted instance of Ghost on AWS Lightsail (Bitnami). I’ve diligently followed the Quick Start guide provided (accessible here: [https://lightsail.aws.amazon.com/ls/docs/en\_us/articles/amazon-lightsail-quick-start-guide-ghost](https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-quick-start-guide-ghost)). However, upon executing the bncert-tool to establish an SSL certificate and enable the HTTPS protocol, I encountered an issue. Specifically, any new image I include in a post appears as disabled, with the “alt” attribute being displayed instead. Additiona…

---

<div class="post-metadata">

**Author:** ![kahuxtable](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kahuxtable/32/32557_2.png) [@kahuxtable](https://forum.ghost.org/u/kahuxtable)\
**Post date:** [October 15, 2024, 1:37am UTC](https://forum.ghost.org/t/site-icon-not-using-https-but-everything-else-does/51669/8 "2024-10-15T01:37:12Z")

</div>

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

> <https://stackoverflow.com/questions/73268081/vm81-mixed-content-issue-with-ghost>
