Page 1 of 1
letsencrypt error
Posted: Fri Nov 25, 2016 6:51 pm
by pium
After the update to V17 if i enable ssl with letsencrypt i get the following error:
Error: Invalid response from
http://domain.tld/.well-known/acme-challenge/BKRU......
Re: letsencrypt error
Posted: Mon Nov 28, 2016 2:18 pm
by arharp
I am also getting this error. I was able to use the CLI commands before the update, but now I'm getting the same invalid response both in the GUI and CLI.
Re: letsencrypt error
Posted: Mon Nov 28, 2016 7:08 pm
by BBuchanan1013
make it another person to this list. Ubuntu 16 fresh install.
Gone back to the letsencrypt-vesta from github
Re: letsencrypt error
Posted: Tue Dec 06, 2016 4:46 am
by huloza
Me too, Debian 8.6 same error
Re: letsencrypt error
Posted: Thu Dec 08, 2016 2:32 pm
by donat
me too,
same error also on subdomains after updating to version .17.
On Debian 7.
Re: letsencrypt error
Posted: Fri Dec 09, 2016 11:29 am
by donat
I just checked out, if there is a problem with the rewrite conditions. But I can't find any error, but must say, that I'm not very familiar with it. So help or hints are still very apreciated.
Re: letsencrypt error
Posted: Tue Dec 13, 2016 4:13 am
by KuJoe
I was running into this same problem and then I noticed that all of the accounts reporting this error had the nginx proxy disabled (I'm not sure why because it should be enabled by default for all new accounts have it disabled). I enabled the nginx proxy and was able to get the LetsEncrypt SSL working for the domains.
Re: letsencrypt error
Posted: Wed Dec 14, 2016 4:48 pm
by donat
Maybe, that there is a proxy problem. But in my case, the nginx is enabled and it doesn't work both ways (nginx disabled and enabled). So there must be another solution and I would really appreciate a solution over gui, because I had in the past several problems with letsencrypt ssl. So any help is still very welcome, since we have several subdomains there.
Don
Re: letsencrypt error
Posted: Thu Dec 29, 2016 7:21 am
by donat
Re: letsencrypt error
Posted: Mon May 08, 2017 3:55 pm
by huloza
KuJoe wrote:I was running into this same problem and then I noticed that all of the accounts reporting this error had the nginx proxy disabled (I'm not sure why because it should be enabled by default for all new accounts have it disabled). I enabled the nginx proxy and was able to get the LetsEncrypt SSL working for the domains.
i have SSL redirection enabled on nginx on all accounts with that problem, i disabled it and now it works.
Regards!