# Forwarding from https:// to https://www

**URL:** https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416
**Category:** Self-hosting
**Tags:** hosting
**Created:** [September 13, 2024, 7:02pm UTC](https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416 "2024-09-13T19:02:07Z")
**Posts on this page:** 17
**Page:** 1

<div class="post-metadata">

### Author: ![Taxick](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/taxick/32/448996_2.png) [@Taxick](https://meta.discourse.org/u/Taxick)
#### Post date: [September 13, 2024, 7:02pm UTC](https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416/1 "2024-09-13T19:02:07Z")

</div>

Hi.

I’m new to discourse! I’m hosting discourse on my Ubuntu 24.04 server 🙂

But I need help with domain forwarding..

If I go to this site: **https:// mysite** - It doesn’t work..

If I go to this site: **[https://www](https://www). mysite** it works fine..

So now to my question. Can I forward all traffic from https:// to [https://www](https://www)

I hope someone can help me out, in a noob friendly way 😛

Regards

Thomas

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [September 13, 2024, 7:11pm UTC](https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416/2 "2024-09-13T19:11:51Z")

</div>

Others have suggested [https://www.forcewww.com/](https://www.forcewww.com/) in similar questions

---

<div class="post-metadata">

### Author: ![Taxick](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/taxick/32/448996_2.png) [@Taxick](https://meta.discourse.org/u/Taxick)
#### Post date: [September 13, 2024, 7:40pm UTC](https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416/3 "2024-09-13T19:40:46Z")

</div>

Hi.

Thanks 🙂

Are this safe??? Point my server to a random place.. ???

Are there other ways to do it?

Where is the nginx configuration located?

---

<div class="post-metadata">

### Author: ![MikeNolan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mikenolan/32/297597_2.png) [@MikeNolan](https://meta.discourse.org/u/MikeNolan)
#### Post date: [September 13, 2024, 7:58pm UTC](https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416/4 "2024-09-13T19:58:35Z")

</div>

Is there a DNS entry for mysite or just for www.mysite?

Does your web server show any log entries for the mysite hits with an indication of why it failed?

---

<div class="post-metadata">

### Author: ![Taxick](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/taxick/32/448996_2.png) [@Taxick](https://meta.discourse.org/u/Taxick)
#### Post date: [September 13, 2024, 8:00pm UTC](https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416/5 "2024-09-13T20:00:25Z")

</div>

Hi @MikeNolan

IPV4 - mysite.dk  
IPv4 - www.mysite.dk

IPV6 - mysite.dk  
IPv6 - www.mysite.dk

---

<div class="post-metadata">

### Author: ![MikeNolan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mikenolan/32/297597_2.png) [@MikeNolan](https://meta.discourse.org/u/MikeNolan)
#### Post date: [September 13, 2024, 8:01pm UTC](https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416/6 "2024-09-13T20:01:15Z")

</div>

What web engine are you using, it needs to know the equivalence as well.

I assume ping mysite and ping www.mysite both work.

What happens if you try to curl to the mysite URL locally?

---

<div class="post-metadata">

### Author: ![Taxick](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/taxick/32/448996_2.png) [@Taxick](https://meta.discourse.org/u/Taxick)
#### Post date: [September 13, 2024, 8:02pm UTC](https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416/7 "2024-09-13T20:02:14Z")

</div>

Hi

Thanks for the reply..

I’m not sure what web engine I have used.

I just have followed this guide: [discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md)

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [September 13, 2024, 8:18pm UTC](https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416/8 "2024-09-13T20:18:20Z")

</div>

> [@Taxick](#):
>
> Are this safe??? Point my server to a random place… ???

Communiteq is a [Discourse partner](https://discourse.org/partners) and I also trust the people who recommend it here at Meta

> [@DNS Settings for Digital Ocean Droplet - Root Domain?](https://meta.discourse.org/t/dns-settings-for-digital-ocean-droplet-root-domain/218903/10):
>
> The easy solution is [forcewww.com](http://forcewww.com). A harder solution is [Setting up Let’s Encrypt with Multiple Domains](https://meta.discourse.org/t/setting-up-let-s-encrypt-with-multiple-domains/56685).

---

<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: [September 13, 2024, 8:34pm UTC](https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416/9 "2024-09-13T20:34:28Z")

</div>

`forcewww.com` is the most noob-friendly way. I use it, and I have been a full-time consultant on Discourse since 2016.

The harder, and slightly more elegant way, is to add a second domain as described in [Set up Let’s Encrypt with multiple domains / redirects](https://meta.discourse.org/t/set-up-let-s-encrypt-with-multiple-domains-redirects/56685).

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [September 14, 2024, 6:26am UTC](https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416/10 "2024-09-14T06:26:16Z")

</div>

> [@Taxick](#):
>
> Are this safe??? Point my server to a random place… ???

I can say [forcewww.com](http://forcewww.com) is reasonably safe. it is built and operated by Communiteq (communiteq is a trusted discourse hosting provider).

---

<div class="post-metadata">

### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [September 14, 2024, 8:27am UTC](https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416/11 "2024-09-14T08:27:57Z")

</div>

Is there some reason why this redirention can’t be done using Nginx?

---

<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: [September 14, 2024, 10:05am UTC](https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416/12 "2024-09-14T10:05:54Z")

</div>

It already does the redirects. The issue is that it doesn’t have a cert for the other site so if you visit the non www sir you get a certificate error

---

<div class="post-metadata">

### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [September 14, 2024, 10:13am UTC](https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416/13 "2024-09-14T10:13:12Z")

</div>

I see. But… that is just matter of so many times mentioned two -d flags when getting sertificates 🤔

What the heck I don’t understand now… I have to re-read this topic.

---

<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: [September 14, 2024, 10:15am UTC](https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416/14 "2024-09-14T10:15:53Z")

</div>

> [@Jagster](#):
>
> that is just matter of so many times mentioned two -d flags

That’s not a simple matter for a novice.

---

<div class="post-metadata">

### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [September 14, 2024, 10:19am UTC](https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416/15 "2024-09-14T10:19:27Z")

</div>

Quite few thing is easy and clear for novices \[1\]

* * *

1. it is guided almost every 101-helps, though, including Lets Encrypt. But it looks like Discourse is considered different than every other sites, I fell in that rabbit hole

---

<div class="post-metadata">

### Author: ![Taxick](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/taxick/32/448996_2.png) [@Taxick](https://meta.discourse.org/u/Taxick)
#### Post date: [September 14, 2024, 11:00am UTC](https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416/16 "2024-09-14T11:00:03Z")

</div>

> [@Moin](#):
>
> [https://www.forcewww.com/](https://www.forcewww.com/)

Hi,

Thanks for all the replies. I did go with this solution: [https://www.forcewww.com/](https://www.forcewww.com/)

It seems to work fine 🙂

Thanks.

---

<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: [October 14, 2024, 11:00am UTC](https://meta.discourse.org/t/forwarding-from-https-to-https-www/326416/17 "2024-10-14T11:00:22Z")

</div>

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