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

**URL:** <https://community.letsencrypt.org/t/letsencrypt-vesta-client-error-the-key-authorization-file-from-the-server-did-not-match/32822>\
**Category:** Help\
**Created:** [April 26, 2017, 2:36am UTC](https://community.letsencrypt.org/t/letsencrypt-vesta-client-error-the-key-authorization-file-from-the-server-did-not-match/32822 "2017-04-26T02:36:30Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![jsha](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jsha/32/12_2.png) [@jsha](https://community.letsencrypt.org/u/jsha)\
**Post date:** [April 26, 2017, 9:34pm UTC](https://community.letsencrypt.org/t/letsencrypt-vesta-client-error-the-key-authorization-file-from-the-server-did-not-match/32822/12 "2017-04-26T21:34:55Z")

</div>

It seems like something on [vpscloud.biz](http://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:

```auto
curl http://vpscloud.biz/.well-known/acme-challenge/this-is-not-a-challenge
this-is-not-a-challenge.ggSx6hy43AXM901bwJ_Dr4mYLANeJZ8AC4Xxg_N3Bgg

```

Note: The part after the “.” is supposed to be a thumbprint (aka fingerprint) of an account key. In this case, the “gg…” thumbprint doesn’t match the thumbprint of your account key, as shown in the keyAuthorization part of your logs.

I think the next step would be to figure out what is responsible for answering that query on your server. I would search your Nginx configs for “well-known” to see if there is any special rule catching such URLs.

Is it possible that Vesta is has its own builting Let’s Encrypt integration, and that is interfering with your attempted Certbot runs?

---

_[View the full topic](https://community.letsencrypt.org/t/letsencrypt-vesta-client-error-the-key-authorization-file-from-the-server-did-not-match/32822)._