The discussion addresses concerns about a domain using HTTP while its Discourse subdomain operates over HTTPS. anon23840344 questions how Discourse can use HTTPS without their main domain being converted to HTTPS, and whether this discrepancy could cause issues. Falco clarifies that Discourse automatically handles HTTPS via Let’s Encrypt, and there should be no problems for users. RGJ explains that HTTPS can be enabled on subdomains independently of the main domain. anon23840344 confirms understanding and notes that this HTTP/HTTPS mismatch is unlikely to be the cause of a user-reported issue, referencing a separate thread for error logs here.
I have a domain that loads over HTTP. It being a single-page, static website, conversion to HTTPS hasn’t been a priority. I have now added a subdomain for discourse, and curiously it loads over HTTPS.
How can Discourse use HTTPS, when I’ve not invested the time to convert my domain to HTTPS?
Could this HTTP/HTTPS disparity cause problems for my Discourse users?
Discourse handles everything you need for a functional website, HTTPS included. We handle provisioning a certificate, renewing and updating the configuration of the web server.
You don’t convert your domain to HTTPS, you can configure the different web sites / web applications on hostnames within your domain to HTTPS. So what happens on discourse.example.com is totally unrelated to what happens on www.example.com or example.com.
So it appears from the two replies so far above that if I’m troubleshooting a user-reported issue, the situation of my public, static website being on a domain with an HTTP scheme, and my private Discourse app serving HTTPS, despite being a subdomain of my HTTP-schemed domain, isn’t a likely cause of error.