The discussion revolves around forcing a non-www domain to redirect to a www domain on a Discourse installation. Matheeus initially reports an issue where, despite configuring Discourse to use www.domain.it, accessing the non-www domain results in an SSL error. He notes that the redirect works for HTTP requests but not HTTPS.
Matheeus later observes that the redirect only works for HTTP requests (http://domain.it) and not HTTPS requests (https://domain.it). pfaffman suggests that the issue might be related to Let’s Encrypt supporting multiple domains and points to a potential solution at https://www.forcewww.com/. However, michaeld from forcewww.com responds, stating that their service should redirect both HTTP and HTTPS requests, and asks Matheeus to PM him for further assistance.
Hello,
I have a site with only a Discourse installation on it (don’t plan to have anything more than the forum).
Now I want to redirect the non-www domain to www.domain.it but also if I reconfigured Discourse via ./discourse-setup changing hostname to www.domain.it if I go to non-www I don’t get redirected but I get an SSL error (Chrome’s NET::ERR_CERT_COMMON_NAME_INVALID).
How I can resolve this?
I’m on a DigitalOcean Discourse Droplet with Discourse 2.2.0 beta1 on Ubuntu 18.04.
If the request comes to http (not https) it works right now. It’s possible to search here and find some topics about having let’s encrypt support multiple domains.
The easy way is https://www.forcewww.com/
Now I noticed that http://domain.it redirects to https://www.domain.it but https://domain.it doesn’t.
Is there another way than forcewww?
Can you please PM me with the name of your domain? forcewww should be redirecting https as well.