# Changing Domains

**URL:** https://meta.discourse.org/t/changing-domains/111681
**Category:** Support
**Created:** [March 15, 2019, 10:36am UTC](https://meta.discourse.org/t/changing-domains/111681 "2019-03-15T10:36:31Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![DigitalStartup](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/digitalstartup/32/118242_2.png) [@DigitalStartup](https://meta.discourse.org/u/DigitalStartup)
#### Post date: [March 15, 2019, 10:36am UTC](https://meta.discourse.org/t/changing-domains/111681/1 "2019-03-15T10:36:31Z")

</div>

I currently have 2 websites across 2 servers:

- [example.com](http://example.com) (Wordpress)
- [forum.example.com](http://forum.example.com) (Discourse)

I plan to discontinue the Wordpress site and update my Discourse Domain to take its place, resulting in:

- [example.com](http://example.com) (Discourse)
- [forum.example.com](http://forum.example.com) (Redirect to [example.com](http://example.com))

I’ve done a little experiment to see how this will all work out on the day:

- Update Discourse settings to use `example.com` Domain
- Update DNS record of `example.com` to point to Discourse server

And here is where I run into an issue:

- Load the old domain of `forum.example.com` redirects to `example.com` _(as expected)_
- Load the old domain of `https://forum.example.com` displays “Your connection is not private” instead of redirecting.

I appreciate this is related to SSL Certificates but not having worked with Docker or Let’s Encrypt before, I’m not sure what to do next.

---

<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: [March 15, 2019, 11:21am UTC](https://meta.discourse.org/t/changing-domains/111681/2 "2019-03-15T11:21:45Z")

</div>

The easiest solution (besides redirecting the apex domain to forum) is to have another server do the redirection. Many dns services will do that for you.

The harder way is to search here for “multiple let’s encrypt” and modify those instructions.

---

<div class="post-metadata">

### Author: ![DigitalStartup](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/digitalstartup/32/118242_2.png) [@DigitalStartup](https://meta.discourse.org/u/DigitalStartup)
#### Post date: [March 15, 2019, 11:43am UTC](https://meta.discourse.org/t/changing-domains/111681/3 "2019-03-15T11:43:25Z")

</div>

Do you have any recommendations for such a service?

---

<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: [March 15, 2019, 11:46am UTC](https://meta.discourse.org/t/changing-domains/111681/4 "2019-03-15T11:46:20Z")

</div>

I’d start by checking your registrar.

---

<div class="post-metadata">

### Author: ![DigitalStartup](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/digitalstartup/32/118242_2.png) [@DigitalStartup](https://meta.discourse.org/u/DigitalStartup)
#### Post date: [March 15, 2019, 2:06pm UTC](https://meta.discourse.org/t/changing-domains/111681/5 "2019-03-15T14:06:45Z")

</div>

I ended up spinning up a server and redirecting with Nginx 👍

---

<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: [April 14, 2019, 2:06pm UTC](https://meta.discourse.org/t/changing-domains/111681/6 "2019-04-14T14:06:49Z")

</div>

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