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 update the DNS records after that. Error is: Checking your domain name . . . WARNING: Port 443 of computer does not appear to be accessible using hostname: x WARNING: Connection to x (port 80) also fails. This suggests that x resolves to some IP address that does not reach this machine where you are installing discourse. The first thing to do is confirm that x resolves to the IP address of this server. You usually do this at the same place you purchased the domain. If you are sure that the IP address resolves correctly, it could be a firewall issue. A web search for "open ports YOUR CLOUD SERVICE" might help. The domain name does in fact respond on ports 80 and 443, so this error message appears to be in error as well.

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 echo "In order to check the connection to $HOST:$PORT we need to open a socket using netcat." echo However netcat is not installed on your system. You can continue without this check echo or abort the setup, install netcat and try again. while true; do read -p "Would you like to continue without this check? [yn] " yn case $yn in [Yy]*) return 2 ;; [Nn]*) exit ;; *) echo "Please answer y or n." ;; esac done else echo -e "HTTP/1.1 200 OK\n\n $VERIFY" | nc -w 4 -l -p $PORT >/dev/null 2>&1 & if curl --proto =http -s $HOST:$PORT --connect-timeout 3 | grep $VERIFY >/dev/null 2>&1; then return 0 Even the manual install instructions have this step. Surely I can’t be the first person to do this. How are people doing it?

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” one that the setup script handles. In your case, your best bet would likely be to copy containers/app.yml file from your current server to the new one. Alternatively you can manually edit the file yourself as suggested on lines 75/76: discourse-setup master return 0 else curl --proto =http -s localhost:$PORT >/dev/null 2>&1 return 1 fi fi } check_IP_match() { HOST="$1" echo if [ "$SKIP_CONNECTION_TEST" == 1 ] then echo "Setting EC to 2" ec=2 else echo Checking your domain name . . . connect_to_port $HOST 443; ec=$? fi case $ec in 0)

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 Edit the file by hand: nano containers/app.yml Bootstrap and start Discourse: ./launcher rebuild app

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 set, so ‘script-src’ is used as a fallback. Is there a direct way to restore from a backup or disable the CSP until then?

[image] mholt: Is there a direct way to restore from a backup [image] 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. person_raising_hand Required user level: Administrator wrench Console access required Here’s how to restore a Discourse backup from the command line, without ever booting the Discourse web UI. This is handy when you’re moving servers. Prerequisites Before you start, make sure you complete the following steps: Download the latest backup file from the source Disco… [image] mholt: disable the CSP until then? SSH to your server, then: cd /var/discourse sudo ./launcher enter app rails c SiteSetting.content_security_policy = false exit exit Note that I’d try the backup restore from CLI first - it solves the actual issue you have (restore a backup) vs the current roadblock (CSP).

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/free+proxy+hideip.me, 1009) is duplicated. /var/www/discourse/lib/backup_restore/database_restorer.rb:87:in `restore_dump' /var/www/discourse/lib/backup_restore/database_restorer.rb:26:in `restore' /var/www/discourse/lib/backup_restore/restorer.rb:51:in `run' script/discourse:143:in `restore' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/thor-1.0.1/lib/thor/command.rb:27:in `run' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/thor-1.0.1/lib/thor/invocation.rb:127:in `invoke_command' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/thor-1.0.1/lib/thor.rb:392:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/thor-1.0.1/lib/thor/base.rb:485:in `start' script/discourse:284:in ` ' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.3/lib/bundler/cli/exec.rb:63:in `load' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.3/lib/bundler/cli/exec.rb:63:in `kernel_load' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.3/lib/bundler/cli/exec.rb:28:in `run' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.3/lib/bundler/cli.rb:497:in `exec' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.3/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.3/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.3/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.3/lib/bundler/cli.rb:30:in `dispatch' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.3/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.3/lib/bundler/cli.rb:24:in `start' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.3/exe/bundle:49:in `block in ' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.3/lib/bundler/friendly_errors.rb:130:in `with_friendly_errors' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.3/exe/bundle:37:in ` ' /usr/local/bin/bundle:23:in `load' /usr/local/bin/bundle:23:in ` ' Trying to rollback... Rolling back... Cleaning stuff up... Dropping functions from the discourse_functions schema... Removing tmp '/var/www/discourse/tmp/restores/default/2020-12-29-214249' directory... Unpausing sidekiq... Marking restore as finished... Notifying 'system' of the end of the restore... Finished! [FAILED] Restore done.

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.

Migrating Discourse from one DigitalOcean droplet to another without downtime

Product Support Self-hosting

mholt (Matt) December 30, 2020, 12:46am 11

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.

Topic		Replies	Views
Move Discourse to a new server without setting up the web UI first? Self-hosting	11	3130	September 3, 2022
Move your Discourse Instance to a Different Server Self-Hosting migrations , how-to	11	294391	August 11, 2026
Starting Over with Old Database Product Support	18	2978	February 3, 2019
How to migrate Discourse from one server to another with the same DNS name Self-hosting	11	3770	April 12, 2024
Can't upload backup Product Support	33	3359	December 27, 2021

Migrating Discourse from one DigitalOcean droplet to another without downtime

Related topics