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.
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.
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.
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?
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.