Hi, after rebuilding / updating to ‘3.6.0.beta3-latest’ my dashboard advises that ‘force_https’ is not yet enabled in your site settings
This setting name is formatted as a link, but clicking the link attempts a settings search for which no results are found:
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.
@hugh Do you know the answer here?
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 numbering system?
If you upgraded recently, I’d expect the version to be 2025.12.0 or 2025.11.0
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.
I think this setting is not available via admin dashboard. To set it you need access to rails console.
If you have access to the server you can:
./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.
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.
