Hello i have recently changed domain successfully thanks to this Howto:
This guide is for self-hosted Discourse instances that were installed using our installation guide on GitHub . If you are hosted by Discourse , please see Configure your domain name for hosted Discourse for specific instructions.
You may eventually want to change the domain name of your Discourse instance, from say
=BEFORE= → =AFTER=
Let’s get started.
Set the TTL for your DNS low, and in advance
You need to let everyone know that the domain is about to change, so change the TTL f…
Changed the Domain from https://animeforums.me
to https://discuss.moe
When i go to https://animeforums.me for a redirect i get this error.
Imgur: The magic of the Internet
Both had Lets-encrypt certs
Though https://discuss.moe works perfectly. Anyway i could redirect it discuss.moe without cert errors?
pfaffman
(Jay Pfaffman)
March 17, 2016, 7:20pm
2
You need to have the old cert for the old domain name still configured since the redirect happens after the ssl connection is made. If you still have the old cert keys you could configure a web server (probably easiest to make it a different container or even a separate site) to be the old name and redirect to the new one.
I have a backup of old certs, by uploading them to the existing ones or how do i configure that?
pfaffman
(Jay Pfaffman)
March 17, 2016, 7:42pm
4
This is far from a copy-and-paste solution, and not for the faint of heart, but here are some pieces of the puzzle:
./launcher enter app
cd /etc/nginx/conf.d
Then create a animeforums.conf that points to the new keys. Start on step 5 of these instructions at Digital Ocean
and add:
rewrite (.*) https://discuss.moe$1 permanent;
I applied another dirty trick to solve this without touching nginx config of discourse or host.
Solved.
This is what I did. Moved animeforums.me dns to cloudflare and enabled ssl over there. It solved the problem
3 Likes
This topic was automatically closed after 3004 days. New replies are no longer allowed.