# Absense of favicon & 'force https'

**URL:** https://meta.discourse.org/t/absense-of-favicon-force-https/277467
**Category:** Support
**Created:** [September 1, 2023, 7:51am UTC](https://meta.discourse.org/t/absense-of-favicon-force-https/277467 "2023-09-01T07:51:01Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![lejeczek](https://avatars.discourse-cdn.com/v4/letter/l/edb3f5/32.png) [@lejeczek](https://meta.discourse.org/u/lejeczek)
#### Post date: [September 1, 2023, 7:51am UTC](https://meta.discourse.org/t/absense-of-favicon-force-https/277467/1 "2023-09-01T07:51:01Z")

</div>

Hi guys.

If it’s not a bug - why I needed to **on** ‘force https’ in order to have **favicon** work?

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [September 1, 2023, 10:15am UTC](https://meta.discourse.org/t/absense-of-favicon-force-https/277467/2 "2023-09-01T10:15:41Z")

</div>

I’m pretty sure that https has been required for some years now. I think that favicons are not the only thing that’s broken without https.

---

<div class="post-metadata">

### Author: ![lejeczek](https://avatars.discourse-cdn.com/v4/letter/l/edb3f5/32.png) [@lejeczek](https://meta.discourse.org/u/lejeczek)
#### Post date: [September 1, 2023, 11:46am UTC](https://meta.discourse.org/t/absense-of-favicon-force-https/277467/4 "2023-09-01T11:46:02Z")

</div>

I was being specific - or perhaps not enough? - 'force https’ in ‘settings’ I had to enable for favicon to appear, even with **https** protocol already set & used on the web server end.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [September 1, 2023, 4:24pm UTC](https://meta.discourse.org/t/absense-of-favicon-force-https/277467/6 "2023-09-01T16:24:47Z")

</div>

> [@lejeczek](#):
>
> If it’s not a bug - why I needed to **on** ‘force https’ in order to have **favicon** work?

Worth mentioning that every install following our [official install](https://meta.discourse.org/t/142537?silent=true) guide ends up with `force_https` enabled out of the box, making problems like this very rare and limited to custom installs.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [September 1, 2023, 5:00pm UTC](https://meta.discourse.org/t/absense-of-favicon-force-https/277467/7 "2023-09-01T17:00:58Z")

</div>

> [@Falco](#):
>
> Worth mentioning that every install following our [official install](https://meta.discourse.org/t/142537) guide ends up with `force_https` enabled out of the box, making problems like this very rare and limited to custom installs.

Maybe it should just be enabled by default? Maybe it’s better to just be broken if they somehow try not to use https.
