# Let's Encrypt acc registration failed

**URL:** <https://community.letsencrypt.org/t/lets-encrypt-acc-registration-failed/102811>\
**Category:** Help\
**Created:** [September 25, 2019, 1:56pm UTC](https://community.letsencrypt.org/t/lets-encrypt-acc-registration-failed/102811 "2019-09-25T13:56:02Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![alokazay](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/alokazay/32/36665_2.png) [@alokazay](https://community.letsencrypt.org/u/alokazay)\
**Post date:** [September 25, 2019, 1:56pm UTC](https://community.letsencrypt.org/t/lets-encrypt-acc-registration-failed/102811/1 "2019-09-25T13:56:02Z")

</div>

My domain is: [hh-help.com](http://hh-help.com) i use vesta panel, i try add SSL Support, and panel return error Error: Let’s Encrypt acc registration failed - pls help me

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [September 25, 2019, 2:18pm UTC](https://community.letsencrypt.org/t/lets-encrypt-acc-registration-failed/102811/2 "2019-09-25T14:18:20Z")

</div>

Hi @alokazay

VestaCP is a closed world. Is it possible to share a screenshot?

Perhaps you have used something that isn’t a correct mail address.

---

<div class="post-metadata">

**Author:** ![alokazay](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/alokazay/32/36665_2.png) [@alokazay](https://community.letsencrypt.org/u/alokazay)\
**Post date:** [September 25, 2019, 2:24pm UTC](https://community.letsencrypt.org/t/lets-encrypt-acc-registration-failed/102811/3 "2019-09-25T14:24:06Z")

</div>

![image](https://global.discourse-cdn.com/letsencrypt/original/3X/a/4/a4ea591c26638bdcdfaec45c4fae3f9c1258d450.png)

---

<div class="post-metadata">

**Author:** ![alokazay](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/alokazay/32/36665_2.png) [@alokazay](https://community.letsencrypt.org/u/alokazay)\
**Post date:** [September 25, 2019, 2:24pm UTC](https://community.letsencrypt.org/t/lets-encrypt-acc-registration-failed/102811/4 "2019-09-25T14:24:39Z")

</div>

![image](https://global.discourse-cdn.com/letsencrypt/original/3X/6/6/6647473ba2fed3ddfdf92d68a13975489172c328.png)

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [September 25, 2019, 2:28pm UTC](https://community.letsencrypt.org/t/lets-encrypt-acc-registration-failed/102811/5 "2019-09-25T14:28:32Z")

</div>

That looks bad.

Perhaps you should ask in a VestaCP forum.

There was a change:

> [@New CDN for the Production API](https://community.letsencrypt.org/t/new-cdn-for-the-production-api/102629):
>
> T…

Some clients have problems. Perhaps VestaCP doesn't work with the new environment.

Checking your domain the main configuration is ok.

But your error is one step earlier - creating an account, not a certificate. There is only a mail address required. If that doesn't work, it's critical.

---

<div class="post-metadata">

**Author:** ![alokazay](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/alokazay/32/36665_2.png) [@alokazay](https://community.letsencrypt.org/u/alokazay)\
**Post date:** [September 25, 2019, 2:35pm UTC](https://community.letsencrypt.org/t/lets-encrypt-acc-registration-failed/102811/6 "2019-09-25T14:35:57Z")

</div>

thanks i will ask Vesta forum.

---

<div class="post-metadata">

**Author:** ![quacos](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/quacos/32/34239_2.png) [@quacos](https://community.letsencrypt.org/u/quacos)\
**Post date:** [September 26, 2019, 7:41am UTC](https://community.letsencrypt.org/t/lets-encrypt-acc-registration-failed/102811/7 "2019-09-26T07:41:45Z")

</div>

Here’s the fix for VestaCP fellows

It’s about HTTP2 instead of HTTP1

```
wget https://raw.githubusercontent.com/serghey-rodin/vesta/master/bin/v-add-letsencrypt-domain -O $VESTA/bin/v-add-letsencrypt-domain
wget https://raw.githubusercontent.com/serghey-rodin/vesta/master/bin/v-add-letsencrypt-user -O $VESTA/bin/v-add-letsencrypt-user
chmod +x $VESTA/bin/v-add-letsencrypt-domain
chmod +x $VESTA/bin/v-add-letsencrypt-user

```

Source: [https://github.com/serghey-rodin/vesta/issues/1886](https://github.com/serghey-rodin/vesta/issues/1886)

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [September 26, 2019, 8:02am UTC](https://community.letsencrypt.org/t/lets-encrypt-acc-registration-failed/102811/8 "2019-09-26T08:02:12Z")

</div>

Hi @quacos

> [@quacos](#):
>
> Here’s the fix for VestaCP fellows

ah, thanks. So it's a problem of the http/2 switch.

Good to know 👍

---

<div class="post-metadata">

**Author:** ![alokazay](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/alokazay/32/36665_2.png) [@alokazay](https://community.letsencrypt.org/u/alokazay)\
**Post date:** [September 26, 2019, 3:49pm UTC](https://community.letsencrypt.org/t/lets-encrypt-acc-registration-failed/102811/9 "2019-09-26T15:49:23Z")

</div>

Hi @quacos thank you. It is work!!!

---

<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:** [October 26, 2019, 3:49pm UTC](https://community.letsencrypt.org/t/lets-encrypt-acc-registration-failed/102811/10 "2019-10-26T15:49:35Z")

</div>

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