How do I disable https on a restore?
Before my restore, I was able to see my new Discourse instance (http://159.65.164.214), but after the restore I see:
Welcome to nginx!
If you see this page, the nginx web server is successfully installed and working. Further configuration is required.
Is this related to force https, or did I break something?
I haven’t changed DNS yet … because I’m trying to figure out how to get this restore to work.
You have some other web server running. Did you install acme and nginx to enable https? If so, you should remove them and search for something like #howto https
Thanks Jay, I did a one-click install from Digital Ocean for Discourse with Ubuntu 18.04. I didn’t install acme or nginx.
It’s brand new, and then the only thing I’ve done is to restore my backup.
I don’t have anything else setup on this new droplet. Is there a log where I should look for errors?
Does order matter when adding https and restoring backups? Or switching DNS for servers?
You want to get https configured first.
Do you have a hostname defined?
You should try
cd /var/discourse
./discourse-setup
I have an existing instance of Discourse running on 16.04, but I was trying to create a new instance on 18.04.
My original server is currently setup with DNS/https.
Now I’m trying to figure out when it’s safe to point DNS to new server … I’m confused on this transition step, and the impact https/letsencrypt has on it.
Yes. That’s confusing. Lots of chickens and eggs.
Maybe if you point your DNS to the new server and run discourse-setup you’ll be OK.
If you get tired or it’s an emergency, see Fix Your Broken Site – Literate Computing, LLC.
Do you have a floating IP address set up at DigitalOcean?
Assign a floating IP
A floating IP is a static IP address that points to one of your Droplets. It allows you to redirect network traffic to any of your Droplets in the same datacenter. For instance, if your primary Droplet goes offline, you can point your floating IP to a backup Droplet.
When your domain name points to the floating IP, then it becomes much easier to shift traffic from one instance to another as there is no wait for DNS info to propagate.
You probably need to speak to DigitalOcean about this, we can’t support their one-click installs here. They’re billed as being simpler, and that may be true if they’re willing to support it, but we can’t.
The only supportable configuration is from the Standard Install Guide which will incidentally bypass all of the issues you’re mentioning above.
One caveat to note is that due to the nature of enrollment for Let’s Encrypt you can’t set a certificate back up without first repointing DNS. Let’s Encrypt needs to connect to your server by the DNS record specified.
Another thing to be aware of is that accessing Discourse by IP is totally unsupported.
I would recommend doing the standard install, that way we can at least help you with the process.
That’s true, but the biggest problem with their one-click install is that it doesn’t tell people that they should
cd /var/discourse
./discourse-setup
If you do that, it’s pretty much a Standard Install. (And if you don’t, you don’t get swap enabled, which will cause problems for 1 & 2GB Droplets, among other problems.)
This problem is really about the difficulty of moving from one host to another when you have https on, and that you can’t run let’s encrypt if the DNS doesn’t point to the new server. The “simple” solution is to rsync over /var/discourse, but that involves a handful of tiny little things that can go wrong.
Which is all outside the scope of what we support here, and for good reason.
That’s the missing guide I’ve been searching for, thanks. I didn’t realize that information wasn’t on the meta.discourse site. I’ll do the standard install.
Following the guide seems to have worked, thank you!
After getting discourse installed, I followed the steps to load my backup that I made from my older server.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.