# About force www to non www

**URL:** https://meta.discourse.org/t/about-force-www-to-non-www/105433
**Category:** 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:** 11
**Page:** 2

<div class="post-metadata">

### Author: ![Gulshan\_Kumar](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gulshan_kumar/32/119562_2.png) [@Gulshan\_Kumar](https://meta.discourse.org/u/Gulshan_Kumar)
#### Post date: [1월 4, 2019, 6:09오후 UTC](https://meta.discourse.org/t/about-force-www-to-non-www/105433/21 "2019-01-04T18:09:43Z")

</div>

In my browser, there is no issue. I can easily browse over HTTPS non-www version.  
Did I missed anything?

---

<div class="post-metadata">

### Author: ![ufukayyildiz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ufukayyildiz/32/217157_2.png) [@ufukayyildiz](https://meta.discourse.org/u/ufukayyildiz)
#### Post date: [1월 4, 2019, 6:21오후 UTC](https://meta.discourse.org/t/about-force-www-to-non-www/105433/22 "2019-01-04T18:21:19Z")

</div>

The problem is with [https://www.fstdesk.com](https://www.fstdesk.com)

On 4 Jan 2019, Fri 21:19, Ultra Noob via Discourse Meta [meta@discoursemail.com](mailto:meta@discoursemail.com) wrote:

---

<div class="post-metadata">

### Author: ![Gulshan\_Kumar](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gulshan_kumar/32/119562_2.png) [@Gulshan\_Kumar](https://meta.discourse.org/u/Gulshan_Kumar)
#### Post date: [1월 4, 2019, 8:47오후 UTC](https://meta.discourse.org/t/about-force-www-to-non-www/105433/23 "2019-01-04T20:47:08Z")

</div>

As a normal user, everything seems fine to me.

What exactly are you expecting to achieve? Sorry, I didn’t get anything.

 ![itkLANnpOb](https://global.discourse-cdn.com/meta/original/3X/4/1/417deced8153b8dba593f7d7c227b9615a7cb95e.gif)

---

<div class="post-metadata">

### Author: ![ufukayyildiz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ufukayyildiz/32/217157_2.png) [@ufukayyildiz](https://meta.discourse.org/u/ufukayyildiz)
#### Post date: [1월 5, 2019, 11:48오후 UTC](https://meta.discourse.org/t/about-force-www-to-non-www/105433/24 "2019-01-05T23:48:44Z")

</div>

try below link please. still there is problem

> **[Brix Mühendislik | Gıda Mühendisliği Hizmetleri](https://brix.tr/)**
>
> Brix Mühendislik, Gıda Mühendisliği Hizmetleri. Gıda ürün geliştirme, proses eğitimleri, danışmanlık hizmetleri ve blog yazılarına ulaşın.

---

<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월 5, 2019, 11:52오후 UTC](https://meta.discourse.org/t/about-force-www-to-non-www/105433/25 "2019-01-05T23:52:02Z")

</div>

Use something other than Chrome

---

<div class="post-metadata">

### Author: ![ufukayyildiz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ufukayyildiz/32/217157_2.png) [@ufukayyildiz](https://meta.discourse.org/u/ufukayyildiz)
#### Post date: [1월 5, 2019, 11:56오후 UTC](https://meta.discourse.org/t/about-force-www-to-non-www/105433/26 "2019-01-05T23:56:28Z")

</div>

same on Pale Moon…

---

<div class="post-metadata">

### Author: ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)
#### Post date: [1월 6, 2019, 12:05오전 UTC](https://meta.discourse.org/t/about-force-www-to-non-www/105433/27 "2019-01-06T00:05:25Z")

</div>

You have a typo in the URL. (the ! exclamation point before the “l” in login).

Also, even with the correct URL, Safari is giving an invalid certificate warning.

---

<div class="post-metadata">

### Author: ![ufukayyildiz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ufukayyildiz/32/217157_2.png) [@ufukayyildiz](https://meta.discourse.org/u/ufukayyildiz)
#### Post date: [1월 6, 2019, 12:15오전 UTC](https://meta.discourse.org/t/about-force-www-to-non-www/105433/28 "2019-01-06T00:15:03Z")

</div>

it is an old link which used before discourse with another script.

How can i solve this issue ? Must i install letsencrypt again with www version of my domain ? or …

---

<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월 6, 2019, 12:23오전 UTC](https://meta.discourse.org/t/about-force-www-to-non-www/105433/29 "2019-01-06T00:23:03Z")

</div>

Personally I would use a registrar redirect for either @ or www and forget about the https edge case.

Just pick whichever you have used in the past or publicised and stick with it.

You can go to the trouble of editing the yml, issuing a SAN cert and configuring redirects but it’s rarely truly necessary.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [1월 6, 2019, 12:35오후 UTC](https://meta.discourse.org/t/about-force-www-to-non-www/105433/30 "2019-01-06T12:35:49Z")

</div>

> [@ufukayyildiz](#):
>
> How can i solve this issue ? Must i install letsencript again with www version of my domain ? or …

Yes. If you want https to work for multiple host names you have to reconfigure let’s encrypt as I suggested above.

I’ve done it before but as suggested above unless you have published another https address that you now want to change it’s largely unnecessary.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [12월 10, 2021, 6:02오후 UTC](https://meta.discourse.org/t/about-force-www-to-non-www/105433/31 "2021-12-10T18:02:46Z")

</div>



[이전 페이지](https://meta.discourse.org/t/about-force-www-to-non-www/105433.md?page=1)
