My domain is: vpscloud.biz I ran this command: generate_ssl admin vpscloud.biz It produced this output: Failed authorization procedure. vpscloud.biz (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: The key authorization file from the server did not match this…

@cpu also looping you in could this be something to do with encoding? and the client not following the Base64 guidelines as strictly as they should? Andrei

Ok, tell me if i can run some tests or do something to help you guys :\

Having the exact same problem Steph. Very frustrating (especially seeing as a few domains have worked fine on the same server, and it just seems to be this one having issues) Cheers Andy

Hello again, @ahaw021 @StephDotNet @steampunkjnkies I hope this may help someone that knows what they are looking at? I have the full debug log from the domain that fails and an example domain that works on the same server. Failed domain (complete log): 2017-04-26 20:40:05,429:DEBUG:certbot.log:R…

It seems like something on vpscloud.biz is set up to auto-respond to HTTP-01 by echoing the provided token, but with a specific account key thumbprint. See, for instance: curl http://vpscloud.biz/.well-known/acme-challenge/this-is-not-a-challenge this-is-not-a-challenge.ggSx6hy43AXM901bwJ_Dr4mYLANe…

Hello, thank you for that. Yes VestaCP does have its own plugin now, which is working fine on 3 domains on that server - vpscloud.biz being the base domain of the server. When the plugin failed to create the certs, I went to the command line and it still would not work, however 2 others that I teste…

An update for you @StephDotNet @ahaw021 @steampunkjnkies @jsha , I have had some success that may relate to all or some of our problems. Thank you @jsha for the guidance, I did indeed find a nginx config file that was creating the reply - nginx.vpscloud.biz.conf_letsencrypt: location ~ "^/\.well-k…

Thank you very much for that, I was aware of that thread and had cited it above.

Thanks @ontheslab . Unfortunately that still didn’t do it for me. It just re-created the _letsencrypt config file, but still failed. Mmm :frowning:

Letsencrypt-vesta Client Error - The key authorization file from the server did not match

Help

jsha April 27, 2017, 1:50am 15

For your NetRegistry problems, see DNS problem: query timed out looking up CAA (using Netregistry).

Topic		Replies	Views
The key authorization file from the server did not match - Vesta Help	4	3136	September 9, 2017
Error when requesting certificate Help	2	493	January 30, 2019
Letsencrypt-vesta - Potential Bug - Miscalculating the Key Authorization Help	3	1590	May 1, 2017
Need help, The key authorization file from the server did not match this challenge Help	1	1824	August 15, 2017
Certbot - The key authorization file from the server did not match error Help	10	26828	April 26, 2017

Letsencrypt-vesta Client Error - The key authorization file from the server did not match

Related topics