# About force www to non www

**URL:** <https://meta.discourse.org/t/about-force-www-to-non-www/105433>\
**Category:** Product Support\
**Created:** [1월 1, 2019, 11:58오후 UTC](https://meta.discourse.org/t/about-force-www-to-non-www/105433 "2019-01-01T23:58:42Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [1월 2, 2019, 9:42오후 UTC](https://meta.discourse.org/t/about-force-www-to-non-www/105433/8 "2019-01-02T21:42:38Z")

</div>

Correct, because Discourse is registered to [http://fstdesk.com/](http://fstdesk.com/) as seen in your certificate:

`common name: fstdesk.com`

Your certificate doesn’t include a subject alternate name for [https://www.fstdesk.com](https://www.fstdesk.com) so the webserver can’t honor that request without first issuing a certificate with a SAN including the WWW entry.

Google Chrome will handle root redirects, but only in the case of @ → www and www → @ - if you try the same URLs in Safari you will note that [https://www.fstdesk.com](https://www.fstdesk.com) also returns the error.

In short this isn’t an error, it wouldn’t work at all if you weren’t using Chrome, which tries to correct mistyped root domains.

Your options are:

- Reconfigure your let’s encrypt to include the subject alternate name [www.fstdesk.com](http://www.fstdesk.com) - this will mean changes to the configuration of your Discourse installation, guides already exist here to achieve this.
- Manage your redirects outside of Discourse

The simplest option is the second one, services such as Cloudflare can catch and redirect all traffic in this way with no Discourse configuration changes whatsoever.

---

_[View the full topic](https://meta.discourse.org/t/about-force-www-to-non-www/105433)._