No `force_https` setting?

balupton · February 5, 2024, 7:39pm

Has the force_https setting been removed? Or is does it not show up if certain templates are used. Here are the templates I’m using:

templates:
  - "templates/postgres.template.yml"
  - "templates/redis.template.yml"
  - "templates/web.template.yml"
  - "templates/cloudflare.template.yml"
  - "templates/web.ssl.template.yml"  # https
  - "templates/web.letsencrypt.ssl.template.yml"  # https
  # - "templates/web.ratelimited.template.yml" # not needed

Arkshine · February 5, 2024, 8:24pm

I don’t think so. I see no changes around force_https and I can still see the setting

`

JammyDodger · February 5, 2024, 8:39pm

I think there is some magic that hides it if you meet certain criteria:

pfaffman · February 5, 2024, 8:57pm

Without finding the code, I think what happens is that if you have a certificate, DISCOURSE_FORCE_HTTPS gets set to true, so it’s hidden from the UX.

JammyDodger · February 5, 2024, 9:16pm

I was looking for this the other day. Is it this bit:

github.com

discourse/discourse_docker/blob/1964d1737a36b4f46ed3c0bc8b25db24e1a9a0c2/templates/web.letsencrypt.ssl.template.yml#L104


      
              fi
          
              LE_WORKING_DIR="${LETSENCRYPT_DIR}" $$ENV_LETSENCRYPT_DIR/acme.sh \
                --installcert --ecc \
                -d $$ENV_DISCOURSE_HOSTNAME \
                --fullchainpath /shared/ssl/$$ENV_DISCOURSE_HOSTNAME_ecc.cer \
                --keypath /shared/ssl/$$ENV_DISCOURSE_HOSTNAME_ecc.key \
                --reloadcmd "sv reload nginx"
          
              if cert_exists "" || cert_exists "_ecc"; then
                grep -q 'force_https' "/var/www/discourse/config/discourse.conf" || echo "force_https = 'true'" >> "/var/www/discourse/config/discourse.conf"
              fi
          
              /usr/sbin/nginx -c /etc/nginx/letsencrypt.conf -s stop
          
          - replace:
             filename: "/etc/nginx/conf.d/discourse.conf"
             from: /ssl_certificate.+/
             to: |
               ssl_certificate /shared/ssl/$$ENV_DISCOURSE_HOSTNAME.cer;
               ssl_certificate /shared/ssl/$$ENV_DISCOURSE_HOSTNAME_ecc.cer;

pfaffman · February 5, 2024, 9:18pm

That’s it! The other way to get stuff into config/discourse.conf is setting an ENV variable, which results in something writing those out to that file just like that.

system · March 6, 2024, 9:18pm

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

Topic		Replies	Views
Can't find force https setting anymore support	3	1560	May 16, 2019
Couldn't find force https support unsupported-install	3	637	May 15, 2018
Changing force_https does not update the url of uploaded images causing a mixed content warning bug	7	1165	December 14, 2020
Insecure fonts requests support	10	978	May 28, 2023
Make auto-linked URLs use HTTPS support	17	554	November 20, 2023

No `force_https` setting?

Related Topics