Ghost Install SSL Error

Developer help Installation
1

I’m trying to install Ghost for the first time on a new Digital Ocean droplet but running into a problem during the “Setting up SSL” step.

Below is the debug information:

Debug Information:
OS: Ubuntu, v18.04
Node Version: v10.15.0
Ghost-CLI Version: 1.9.9
Environment: production
Command: ‘ghost install’
Message: Command failed: /bin/sh -c sudo -S -p ‘#node-sudo-passwd#’ /etc/letsencrypt/acme.sh --issue --home /etc/letsencrypt --domain [example].com --webroot /var/www/ghost/system/nginx-root --reloadcmd “nginx -s reload” --accountemail contact@[example].com
[Wed Jan 16 15:59:33 UTC 2019] [example].com:Verify error:Invalid response from http://[example].com/.well-known/acme-challenge/QwdHb…:
[Wed Jan 16 15:59:33 UTC 2019] Please add ‘–debug’ or ‘–log’ to check more details.
[Wed Jan 16 15:59:33 UTC 2019] See: How to debug acme.sh · acmesh-official/acme.sh Wiki · GitHub

[Wed Jan 16 15:59:30 UTC 2019] Single domain=‘[example].com’
[Wed Jan 16 15:59:30 UTC 2019] Getting domain auth token for each domain
[Wed Jan 16 15:59:30 UTC 2019] Getting webroot for domain=‘[example].com’
[Wed Jan 16 15:59:30 UTC 2019] Getting new-authz for domain=‘[example].com’
[Wed Jan 16 15:59:30 UTC 2019] The new-authz request is ok.
[Wed Jan 16 15:59:30 UTC 2019] Verifying:[example].com

Exit code: 1

--------------- stdout ---------------
[Wed Jan 16 15:59:30 UTC 2019] Single domain=‘[example].com’
[Wed Jan 16 15:59:30 UTC 2019] Getting domain auth token for each domain
[Wed Jan 16 15:59:30 UTC 2019] Getting webroot for domain=‘[example].com’
[Wed Jan 16 15:59:30 UTC 2019] Getting new-authz for domain=‘[example].com’
[Wed Jan 16 15:59:30 UTC 2019] The new-authz request is ok.
[Wed Jan 16 15:59:30 UTC 2019] Verifying:[example].com

--------------- stderr ---------------
[Wed Jan 16 15:59:33 UTC 2019] [example].com:Verify error:Invalid response from http://[example].com/.well-known/acme-challenge/QwdHb…:
[Wed Jan 16 15:59:33 UTC 2019] Please add ‘–debug’ or ‘–log’ to check more details.
[Wed Jan 16 15:59:33 UTC 2019] See: How to debug acme.sh · acmesh-official/acme.sh Wiki · GitHub

I cant seem to figure out how to resolve this issue. Can someone help?

2

Is your domain pointing to the correct DO IP? That’s the most likely culprit

4

Yes! I’ve made sure the DNS records on DigitalOcean are pointing to the correct DO IP. I can get to test nginx page via both [domain].com and www.[domain].com.

5

From the error output:

Verify error:Invalid response from http://[example].com/.well-known/acme-challenge/QwdHb…:

This is the error details we have so far. Your droplet didn’t return a valid response to the verification challenge for some reason. There isn’t enough detail to know exactly why…

Also from the error is the command that failed and some debug info:

Command failed:/bin/sh -c sudo -S -p ‘#node-sudo-passwd#’ /etc/letsencrypt/acme.sh [very long command much stuff here]
…
Please add ‘–debug’ or ‘–log’ to check more details.
See: How to debug acme.sh · acmesh-official/acme.sh Wiki · GitHub

Please checkout the link for some more gotchas (did you close port 80?) and if that doesn’t shed any light, can you manually rerun the full listed command with the additional --debug or --debug 2 flags, and if there’s no clarity in the output still post that back here maybe one of us will understand :)

6

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.