We’re moving to a new DigitalOcean droplet and tried using the marketplace image. When running the setup script, it fails early on because our domain name is still pointing to our current instance in production. I need to get this new installation up and running so I can restore its backup and then…

Hey Matt, We (the Discourse team) don’t manage the DO marketplace image, so I’m afraid we’re going to be of limited help resolving that specific issue.

But you do manage this, yes? discourse-setup master ## connect_to_port () { HOST="$1" PORT="$2" VERIFY=$(date +%s | sha256sum | base64 | head -c 20) if ! [ -x "$(command -v nc)" ]; then ech…

Yes, we do manage that. I did not look at the code, I assumed the check was coming from the marketplace image. ./discourse-setup is intended as a simple way of setting up Discourse - avoiding the need to manually edit a text file when spinning up a new Discourse site. Your use case isn’t a “typical…

Where can I find the default app.yml? I want to start with a fresh default installation. Also, how do I get the server up and running without the setup script? Accessing the IP address is still unresponsive since I can’t run the setup script.

Default can be found at samples/standalone.yml. Also on GitHub . Assuming you’re following the official install guide, after the commands in “Install Discourse”, you’ll want to do the following: Copy the default yaml file from samples to containers: cp samples/standalone.yml containers/app.yml Ed…

Thank you, that gets me closer. But now I cannot import the backup because I cannot activate my temporary admin account: (6) Refused to load the script ‘’ because it violates the following Content Security Policy directive: “script-src ”. Note that ‘script-src-elem’ was not explicitly s…

[afbeelding] mholt: Is there a direct way to restore from a backup [afbeelding] Restore a backup from the command line Self-Hosting bookmark This guide explains how to restore a Discourse backup from the command line without using the Discourse web UI. p…

Thanks for the pointers. Running restore, I get: ERROR: could not create unique index "index_incoming_referers_on_path_and_incoming_domain_id" DETAIL: Key (path, incoming_domain_id)=(/s/free+proxy+hideip.me, 1009) is duplicated. EXCEPTION: psql failed: DETAIL: Key (path, incoming_domain_id)=(/s…

Looks like you have a corrupt index. Have you run an upgrade on the existing instance? There’s a chance that help. There is a topic somewhere with instructions for copying over the raw database (and let’s encrypt) files from the old instance. That’s probably what I would do.

[afbeelding] pfaffman: Have you rub run an upgrade on the existing instance? What’s rub run? Upgrades on the existing instance keep having errors (different errors than this one) so that’s why I’m moving to a new instance.

Discourse migreren van de ene DigitalOcean droplet naar de andere zonder downtime

Ondersteuning Installatie

pfaffman (Jay Pfaffman) 30 december 2020 om 00:50 13

Transferring backups via rsync and cronperhaps

Topic		Antwoorden	Weergaven
Move Discourse to a new server without setting up the web UI first? Self-hosting	11	2839	3 september 2022
Starting Over with Old Database Support	18	2727	3 februari 2019
Move your Discourse Instance to a Different Server Self-Hosting migrations , how-to	10	293441	16 oktober 2025
How to migrate Discourse from one server to another with the same DNS name Self-hosting	11	3490	12 april 2024
Can't upload backup Support	33	2858	27 december 2021

Discourse migreren van de ene DigitalOcean droplet naar de andere zonder downtime

Gerelateerde topics