# Absense of favicon & 'force https'

**URL:** <https://meta.discourse.org/t/absense-of-favicon-force-https/277467>\
**Category:** Product 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:** 1\
**Showing post:** 6

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

---

_[View the full topic](https://meta.discourse.org/t/absense-of-favicon-force-https/277467)._