# Login dialog missing link to logo because DISCOURSE\_FORCE\_HTTPS set to ‘false’

**URL:** <https://meta.discourse.org/t/login-dialog-missing-link-to-logo-because-discourse-force-https-set-to-false/390744>\
**Category:** Product Support\
**Created:** [December 9, 2025, 5:46am UTC](https://meta.discourse.org/t/login-dialog-missing-link-to-logo-because-discourse-force-https-set-to-false/390744 "2025-12-09T05:46:08Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Paul\_King](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/paul_king/32/165426_2.png) [@Paul\_King](https://meta.discourse.org/u/Paul_King)\
**Post date:** [December 9, 2025, 6:47am UTC](https://meta.discourse.org/t/login-dialog-missing-link-to-logo-because-discourse-force-https-set-to-false/390744/4 "2025-12-09T06:47:15Z")

</div>

Thanks @NateDhaliwal, some good sugguestions.

Toggling that setting then reloading makes no difference.

I can’t seem to access safemode at all - [https://discourse.nzarchiture.net.nz](https://discourse.nzarchiture.net.nz) gives a dead link warning in my browser (as does [http://discourse.nzarchiture.net.nz](http://discourse.nzarchiture.net.nz))

There certianly are errors on that page - suggusting the login dialog is for some reason trying to reference a mixture of https and http based urls for its content.

```plaintext
(index):365 Mixed Content: The page at 'https://nzarchitecture.net.nz/' was loaded over HTTPS, but requested an insecure font 'http://nzarchitecture.net.nz/fonts/JetBrainsMono-Regular.woff2?v=0.0.19'. This request has been blocked; the content must be served over HTTPS.
(index):365 Mixed Content: The page at 'https://nzarchitecture.net.nz/' was loaded over HTTPS, but requested an insecure font 'http://nzarchitecture.net.nz/fonts/JetBrainsMono-Bold.woff2?v=0.0.19'. This request has been blocked; the content must be served over HTTPS.
app.js:297 ℹ️ Discourse v2025.12.0-latest — https://github.com/discourse/discourse/commits/4e84c286d6 — Ember v6.6.0
content.js:18 [Form Persistence] 初始化表单持久化扩展...
content.js:868 shouldRun: false
(index):1 Mixed Content: The page at 'https://nzarchitecture.net.nz/' was loaded over HTTPS, but requested an insecure favicon 'http://nzarchitecture.net.nz/uploads/default/optimized/1X/f194d3ff8870aa98f79a9aef41a5d954c243aef6_2_32x32.png'. This request has been blocked; the content must be served over HTTPS.
content.js:13 [Form Persistence] 从存储中获取的数据: Object
content.js:18 [Form Persistence] 当前页面未启用表单持久化
(index):1 Mixed Content: The page at 'https://nzarchitecture.net.nz/' was loaded over HTTPS, but requested an insecure element 'http://nzarchitecture.net.nz/uploads/default/original/1X/5d5ed6d82ef2bd08985655747ca1f2d08e94ac0e.png'. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html
(index):1 Mixed Content: The page at 'https://nzarchitecture.net.nz/' was loaded over HTTPS, but requested an insecure image 'http://nzarchitecture.net.nz/uploads/default/original/1X/5d5ed6d82ef2bd08985655747ca1f2d08e94ac0e.png'. This request has been blocked; the content must be served over HTTPS.
(index):1 Mixed Content: The page at 'https://nzarchitecture.net.nz/' was loaded over HTTPS, but requested an insecure element 'http://nzarchitecture.net.nz/uploads/default/optimized/1X/f194d3ff8870aa98f79a9aef41a5d954c243aef6_2_512x512.png'. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html
content.js:18 [Form Persistence] 收到状态检查指令
content.js:13 [Form Persistence] 从存储中获取的数据: Object
content.js:18 [Form Persistence] 页面状态更新: Object

```

I also don’t know where those chinese characters amongst the console warnings come from, and whether they are a cause for concern? The site itself was created in English, and has no other translations set up.

How do I tell Discourse to only load images over https?

---

_[View the full topic](https://meta.discourse.org/t/login-dialog-missing-link-to-logo-because-discourse-force-https-set-to-false/390744)._