# Bogus Dashboard advice

**URL:** https://meta.discourse.org/t/bogus-dashboard-advice/390140
**Category:** Support
**Tags:** install
**Created:** [December 2, 2025, 7:39am UTC](https://meta.discourse.org/t/bogus-dashboard-advice/390140 "2025-12-02T07:39:05Z")
**Posts on this page:** 13
**Page:** 1

<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 2, 2025, 7:39am UTC](https://meta.discourse.org/t/bogus-dashboard-advice/390140/1 "2025-12-02T07:39:05Z")

</div>

Hi, after rebuilding / updating to ‘3.6.0.beta3-latest’ my dashboard advises that `‘force_https’ is not yet enabled in your site settings`

 ![image](https://global.discourse-cdn.com/meta/original/4X/e/8/c/e8c455d0ead881bbaf1051d465c94734e371a59e.png)

This setting name is formatted as a link, but clicking the link attempts a settings search for which no results are found:

 ![image](https://global.discourse-cdn.com/meta/original/4X/3/6/4/36440e2950fea3f560aa9078ba5fcd1dd53ddc3d.png)

Does this mean the setting has been removed, or has the name been changed?

I have not been able to find any obviously related setting by searching settings manually.

---

<div class="post-metadata">

### Author: ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [December 2, 2025, 7:40am UTC](https://meta.discourse.org/t/bogus-dashboard-advice/390140/2 "2025-12-02T07:40:56Z")

</div>

@hugh Do you know the answer here?

---

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [December 2, 2025, 7:49am UTC](https://meta.discourse.org/t/bogus-dashboard-advice/390140/4 "2025-12-02T07:49:30Z")

</div>

See [Can't find force https setting anymore](https://meta.discourse.org/t/cant-find-force-https-setting-anymore/115227) and/or [Couldn't find force https](https://meta.discourse.org/t/couldnt-find-force-https/87489)

---

<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 2, 2025, 9:00am UTC](https://meta.discourse.org/t/bogus-dashboard-advice/390140/5 "2025-12-02T09:00:35Z")

</div>

Thanks @RGJ

It seems like the advice wording needs to be updated to reflect that the setting is hidden and does not need to be changed for those using LetsEncrypt

---

<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: [December 2, 2025, 12:31pm UTC](https://meta.discourse.org/t/bogus-dashboard-advice/390140/6 "2025-12-02T12:31:56Z")

</div>

Is this a [standard install](https://meta.discourse.org/t/142537?silent=true)? If so you should have the new numbering system.

---

<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 2, 2025, 1:27pm UTC](https://meta.discourse.org/t/bogus-dashboard-advice/390140/7 "2025-12-02T13:27:19Z")

</div>

As far as I know it was a [standard install](https://meta.discourse.org/t/142537?silent=true) in the sense of being on a Digital Ocean droplet running Ubuntu 24.04.3, installed using `git pull`, although beyond that I would likely not notice if things had gone off-piste somehow.

Below is what I see on Dashboard - is the code in blue from the new numbering system?

 ![image](https://global.discourse-cdn.com/meta/original/4X/0/2/2/0220a6e5c29fad69c24a69483f520c24d7d549b0.png)

---

<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: [December 2, 2025, 1:44pm UTC](https://meta.discourse.org/t/bogus-dashboard-advice/390140/8 "2025-12-02T13:44:26Z")

</div>

If you upgraded recently, I’d expect the version to be 2025.12.0 or 2025.11.0

---

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [December 2, 2025, 3:04pm UTC](https://meta.discourse.org/t/bogus-dashboard-advice/390140/9 "2025-12-02T15:04:53Z")

</div>

> [@Paul\_King](#):
>
> It seems like the advice wording needs to be updated to reflect that the setting is hidden and does not need to be changed for those using LetsEncrypt

Hmm maybe the wording needs to be changed, but there is something up, this warning does not appear out of nowhere.

---

<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: [December 3, 2025, 10:49pm UTC](https://meta.discourse.org/t/bogus-dashboard-advice/390140/10 "2025-12-03T22:49:31Z")

</div>

~~Looks like I a bug, as I’m seeing this on a CDCK hosted site that’s running 63d923e144bbc46cf78efd686164938c5699209d (it just restored a backup, if that makes a difference).~~

But it went away when the backup finished restoring.

---

<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 8, 2025, 7:05am UTC](https://meta.discourse.org/t/bogus-dashboard-advice/390140/11 "2025-12-08T07:05:21Z")

</div>

Just updated, and now my version is showing ‘2025.12.0-latest’

However I still get the advice with the link to a setting that does not exist.

---

<div class="post-metadata">

### Author: ![italo](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/italo/32/315833_2.png) [@italo](https://meta.discourse.org/u/italo)
#### Post date: [December 8, 2025, 11:45am UTC](https://meta.discourse.org/t/bogus-dashboard-advice/390140/12 "2025-12-08T11:45:21Z")

</div>

I think this setting is not available via admin dashboard. To set it you need access to rails console.

> <https://github.com/discourse/discourse/blob/539087671e7a0eb71dbf7db05fb5dbb96e05538d/config/site_settings.yml#L2713>

If you have access to the server you can:

```bash
./launcher enter app # change app to your container name
rails c
SiteSetting.force_https = true

```

I do believe this should be true after a successful installation tho.

---

<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, 7:39am UTC](https://meta.discourse.org/t/bogus-dashboard-advice/390140/13 "2025-12-09T07:39:41Z")

</div>

Thanks @italo This solved another issue as well, with mixed http and https references to image assets on my login dialog.

In my case, app.yml had this set to false - editing app.yml and rebuilding, and the error is now gone from dashboard, and the site logo now appears on the login dialog.

 ![image](https://global.discourse-cdn.com/meta/original/4X/3/5/e/35e79913f0f948279b7048e171317847d00e66c8.png)

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [January 8, 2026, 7:39am UTC](https://meta.discourse.org/t/bogus-dashboard-advice/390140/14 "2026-01-08T07:39:41Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
