# Letsencrypt-vesta - Potential Bug - Miscalculating the Key Authorization

**URL:** <https://community.letsencrypt.org/t/letsencrypt-vesta-potential-bug-miscalculating-the-key-authorization/33152>\
**Category:** Help\
**Created:** [May 1, 2017, 11:21am UTC](https://community.letsencrypt.org/t/letsencrypt-vesta-potential-bug-miscalculating-the-key-authorization/33152 "2017-05-01T11:21:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![fabianborg](https://avatars.discourse-cdn.com/v4/letter/f/b77776/32.png) [@fabianborg](https://community.letsencrypt.org/u/fabianborg)\
**Post date:** [May 1, 2017, 11:21am UTC](https://community.letsencrypt.org/t/letsencrypt-vesta-potential-bug-miscalculating-the-key-authorization/33152/1 "2017-05-01T11:21:02Z")

</div>

Hello

I am aware that there are other posts on this issue, tried all the remedies suggested but none worked for me.

I have a server running Ubuntu 16.04.02 LTS with VESTACP and installed letsencrypt-vesta following this guide [here](https://github.com/interbrite/letsencrypt-vesta) on apache2.

When I run this code `letsencrypt-vesta admin example.com` ([example.com](http://example.com) replaces a real domain name) I get the following error

```
root@server:~# letsencrypt-vesta admin example.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for example.com
http-01 challenge for www.example.com
Using the webroot path /etc/letsencrypt/webroot for all unmatched domains.
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. www.example.com (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: The key authorization file from the server did not match this challenge [SpF5RYoAUL7KwL2wcS-vsrJb53pmeIKKn6U9SmMyMYU.beYaC8qzUM_StuviLZkDy-IMn7twZbTthcdtLGvfv_Y] != [SpF5RYoAUL7KwL2wcS-vsrJb53pmeIKKn6U9SmMyMYU.JZBgjnhAN-WRJGBziNjLkVP-uvfOXwX_XDx2tUx1rEs], example.com (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: The key authorization file from the server did not match this challenge [t4jqnRu-wXy57VMjdx0mzNdBpSTGvWLvh645hGcYC6c.beYaC8qzUM_StuviLZkDy-IMn7twZbTthcdtLGvfv_Y] != [t4jqnRu-wXy57VMjdx0mzNdBpSTGvWLvh645hGcYC6c.JZBgjnhAN-WRJGBziNjLkVP-uvfOXwX_XDx2tUx1rEs]

IMPORTANT NOTES:
 - The following errors were reported by the server:

   Domain: www.example.com
   Type: unauthorized
   Detail: The key authorization file from the server did not match
   this challenge
   [SpF5RYoAUL7KwL2wcS-vsrJb53pmeIKKn6U9SmMyMYU.beYaC8qzUM_StuviLZkDy-IMn7twZbTthcdtLGvfv_Y]
   !=
   [SpF5RYoAUL7KwL2wcS-vsrJb53pmeIKKn6U9SmMyMYU.JZBgjnhAN-WRJGBziNjLkVP-uvfOXwX_XDx2tUx1rEs]

   Domain: example.com
   Type: unauthorized
   Detail: The key authorization file from the server did not match
   this challenge
   [t4jqnRu-wXy57VMjdx0mzNdBpSTGvWLvh645hGcYC6c.beYaC8qzUM_StuviLZkDy-IMn7twZbTthcdtLGvfv_Y]
   !=
   [t4jqnRu-wXy57VMjdx0mzNdBpSTGvWLvh645hGcYC6c.JZBgjnhAN-WRJGBziNjLkVP-uvfOXwX_XDx2tUx1rEs]

   To fix these errors, please make sure that your domain name was
   entered correctly and the DNS A record(s) for that domain
   contain(s) the right IP address.
Let's Encrypt returned an error status. Aborting.
root@server:~#
```

DNS A record is properly set to direct to the server’s fixed public ip address.

How can I fix this error.

---

<div class="post-metadata">

**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\
**Post date:** [May 1, 2017, 2:40pm UTC](https://community.letsencrypt.org/t/letsencrypt-vesta-potential-bug-miscalculating-the-key-authorization/33152/2 "2017-05-01T14:40:45Z")

</div>

> [@fabianborg](#):
>
> I have a server running Ubuntu 16.04.02 LTS with VESTACP and installed letsencrypt-vesta

Has anyone tried reporting this as a bug to the maintainers of Vestacp? It seems like it is miscalculating the key authorization.

---

<div class="post-metadata">

**Author:** ![fabianborg](https://avatars.discourse-cdn.com/v4/letter/f/b77776/32.png) [@fabianborg](https://community.letsencrypt.org/u/fabianborg)\
**Post date:** [May 1, 2017, 3:12pm UTC](https://community.letsencrypt.org/t/letsencrypt-vesta-potential-bug-miscalculating-the-key-authorization/33152/3 "2017-05-01T15:12:35Z")

</div>

@cpu I have filed a bug report on the git of the letsencrypt-vesta dev team [here](https://github.com/interbrite/letsencrypt-vesta/issues/51)

---

<div class="post-metadata">

**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\
**Post date:** [May 1, 2017, 3:13pm UTC](https://community.letsencrypt.org/t/letsencrypt-vesta-potential-bug-miscalculating-the-key-authorization/33152/4 "2017-05-01T15:13:51Z")

</div>

Great thank you! I will subscribe to the repo.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [May 31, 2017, 3:24pm UTC](https://community.letsencrypt.org/t/letsencrypt-vesta-potential-bug-miscalculating-the-key-authorization/33152/5 "2017-05-31T15:24:35Z")

</div>

Closed on May 31, 2017, 3:24pm UTC

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