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] This setting name is formatted as a link, but clicking the link attempts a settings search for which no results are found: [image] Does this mean th…

I think this setting is not available via admin dashboard. To set it you need access to rails console. config/site_settings.yml 539087671 area: "login" enforce_second_factor: client: true type: enum default: "no" …

See Can't find force https setting anymore and/or Couldn't find force https

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

Is this a standard install ? If so you should have the new numbering system.

As far as I know it was a standard install 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 numb…

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

[afbeelding] 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.

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.

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.

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…

Bogus Dashboard advice

Ondersteuning

chapoi 2 december 2025 om 07:40 2

@hugh Do you know the answer here?

Topic		Antwoorden	Weergaven
Can't find force https setting anymore Support	3	1854	16 mei 2019
Couldn't find force https Support unsupported-install	3	730	15 mei 2018
Prompt to enable Force HTTPS in the wizard Feature	13	3197	20 juli 2018
No `force_https` setting? Support	6	373	5 februari 2024
Http logo urls after enabling LetsEncrypt Self-hosting	15	1431	8 juni 2024

Bogus Dashboard advice

Gerelateerde topics