# Invalid response from acme-challenge when setting up SSL

**URL:** <https://forum.ghost.org/t/invalid-response-from-acme-challenge-when-setting-up-ssl/10167>\
**Category:** Installation\
**Created:** [November 11, 2019, 8:13am UTC](https://forum.ghost.org/t/invalid-response-from-acme-challenge-when-setting-up-ssl/10167 "2019-11-11T08:13:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![lavascript](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/lavascript/32/5092_2.png) [@lavascript](https://forum.ghost.org/u/lavascript)\
**Post date:** [November 11, 2019, 8:13am UTC](https://forum.ghost.org/t/invalid-response-from-acme-challenge-when-setting-up-ssl/10167/1 "2019-11-11T08:13:02Z")

</div>

Trying to set up SSL for [http://www.codymi.ms/](http://www.codymi.ms/) and I get this ProcessError:

> Message: Command failed: /bin/sh -c sudo -S -p ‘#node-sudo-passwd#’ /etc/letsencrypt/acme.sh --issue --home /etc/letsencrypt --domain codymi.ms --webroot /var/www/ghost/system/nginx-root --reloadcmd “nginx -s reload” --accountemail _[redacted]_  
> [Mon Nov 11 01:02:32 MST 2019] codymi.ms:Verify error:Invalid response from [http://codymi.ms/.well-known/acme-challenge/h3ppt4\_TXjL2Y13jIedQQYv0V8pp4NXvtDszS\_h3nDI](http://codymi.ms/.well-known/acme-challenge/h3ppt4_TXjL2Y13jIedQQYv0V8pp4NXvtDszS_h3nDI) [45.79.47.115]:  
> [Mon Nov 11 01:02:32 MST 2019] Please add ‘–debug’ or ‘–log’ to check more details.  
> [Mon Nov 11 01:02:32 MST 2019] See: [How to debug acme.sh · acmesh-official/acme.sh Wiki · GitHub](https://github.com/Neilpang/acme.sh/wiki/How-to-debug-acme.sh)
> 
> [Mon Nov 11 01:02:28 MST 2019] Single domain=‘codymi.ms’  
> [Mon Nov 11 01:02:28 MST 2019] Getting domain auth token for each domain  
> [Mon Nov 11 01:02:29 MST 2019] Getting webroot for domain=‘codymi.ms’  
> [Mon Nov 11 01:02:29 MST 2019] Verifying: codymi.ms
> 
> Exit code: 1
> 
> Debug Information:  
> OS: Ubuntu, v18.04.3 LTS  
> Node Version: v10.17.0  
> Ghost Version: 3.0.2  
> Ghost-CLI Version: 1.13.1  
> Environment: production  
> Command: ‘ghost setup ssl --debug’

I currently don’t have anything at codymi.ms/ghost/ and I suspect it’s because I don’t have SSL so any help would be appreciated.

---

<div class="post-metadata">

**Author:** ![mskian](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/mskian/32/4973_2.png) [@mskian](https://forum.ghost.org/u/mskian)\
**Post date:** [November 11, 2019, 1:20pm UTC](https://forum.ghost.org/t/invalid-response-from-acme-challenge-when-setting-up-ssl/10167/2 "2019-11-11T13:20:12Z")

</div>

if you facing a similar issue  
then Check this post

> [@Let's Encrypt Expiry Bot](https://forum.ghost.org/t/lets-encrypt-expiry-bot/9708/3):
>
> Well I talked to myself in this topic, I update it for someone who may have the same problem. Update acme.sh like this: "/etc/letsencrypt"/acme.sh --upgrade --home "/etc/letsencrypt" Then update the certificates: "/etc/letsencrypt"/acme.sh --cron --home "/etc/letsencrypt" \> /dev/null Certificates should be updated.

---

<div class="post-metadata">

**Author:** ![lavascript](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/lavascript/32/5092_2.png) [@lavascript](https://forum.ghost.org/u/lavascript)\
**Post date:** [November 11, 2019, 3:27pm UTC](https://forum.ghost.org/t/invalid-response-from-acme-challenge-when-setting-up-ssl/10167/3 "2019-11-11T15:27:28Z")

</div>

Updating Acme didn’t help.

---

<div class="post-metadata">

**Author:** ![lavascript](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/lavascript/32/5092_2.png) [@lavascript](https://forum.ghost.org/u/lavascript)\
**Post date:** [November 13, 2019, 1:57am UTC](https://forum.ghost.org/t/invalid-response-from-acme-challenge-when-setting-up-ssl/10167/4 "2019-11-13T01:57:50Z")

</div>

Can’t delete so I’ll just say what happened: I had done my own server configuration (installing Fail2Ban and the like) and set up all the prerequisites _before_ going through the install article, some with different commands than what was listed. I wiped the server and tried again following the prerequisite instructions exactly and it worked great. If I had to guess what the exact error was I think I was probably using the default “localhost” MySQL hostname after I had already changed my server’s hostname.