# Problems with renew SSL. Error 400 pending - HESTIA Control Panel

**URL:** <https://community.letsencrypt.org/t/problems-with-renew-ssl-error-400-pending-hestia-control-panel/161916>\
**Category:** Ayuda (en Español)\
**Created:** [October 4, 2021, 10:49am UTC](https://community.letsencrypt.org/t/problems-with-renew-ssl-error-400-pending-hestia-control-panel/161916 "2021-10-04T10:49:08Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![nomopo](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/nomopo/32/54114_2.png) [@nomopo](https://community.letsencrypt.org/u/nomopo)\
**Post date:** [October 4, 2021, 10:49am UTC](https://community.letsencrypt.org/t/problems-with-renew-ssl-error-400-pending-hestia-control-panel/161916/1 "2021-10-04T10:49:08Z")

</div>

Por favor, complete los campos del siguiente formulario para que podamos ayudarle de la mejor forma posible. Nota: debe proporcionar su nombre de dominio para obtener ayuda. Los nombres de dominio de los certificados emitidos se hacen públicos en los registros de Transparencia de Certificados (por ejemplo, [crt.sh | example.com](https://crt.sh/?q=example.com)), por lo que esconder aquí su nombre de dominio no sirve de nada, únicamente nos dificulta prestarle la ayuda solicitada.

Puedo leer las respuestas en Inglés (sí o no): SI

Mi dominio es: servicio-tecnico-autorizado.pro, pero quiero instalar certificado en mail.servicio-tecnico-autorizado.pro

Ejecuté este comando: hestia cp -\> v-update-letsencrypt-ssl

Produjo esta salida: NADA

Mi servidor web es (incluya la versión): WP 5.8

El sistema operativo en el que se ejecuta mi servidor web es (incluya la versión): ubuntu 20

Mi proveedor de alojamiento web (si aplica) es: [webuphosting.com](http://webuphosting.com)

Puedo iniciar una sesión en una shell root en mi servidor (sí, no o no lo sé): SI

Estoy usando un panel de control para administrar mi sitio (no o proporcione el nombre y la versión del panel de control): SI . Hestia CP

La versión de mi cliente es (por ejemplo, si usa certbot, muestre la salida de `certbot --version` o `certbot-auto --version`):

Ahora mismo en el dominio principal servicio-tecnico-autorizado.pro tiene un certificado de Redalia.

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [October 4, 2021, 12:22pm UTC](https://community.letsencrypt.org/t/problems-with-renew-ssl-error-400-pending-hestia-control-panel/161916/2 "2021-10-04T12:22:32Z")

</div>

Hi @nomopo welcome to the LE community forum 🙂  
[And please excuse my use of English.]

How did you get the other cert?  
[servicio-tecnico-autorizado.pro]

Is this new cert only going to be used for encrypting mail?  
Or also for [https://mail.servicio-tecnico-autorizado.pro/](https://mail.servicio-tecnico-autorizado.pro/) [like for webmail type access] ?

---

<div class="post-metadata">

**Author:** ![nomopo](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/nomopo/32/54114_2.png) [@nomopo](https://community.letsencrypt.org/u/nomopo)\
**Post date:** [October 5, 2021, 4:46am UTC](https://community.letsencrypt.org/t/problems-with-renew-ssl-error-400-pending-hestia-control-panel/161916/3 "2021-10-05T04:46:52Z")

</div>

The other certificate was bought from Comodo, because since it stopped working, it has been the fastest way to restore the system.  
The idea is to use an SSL of yours for the mail. Just for the mail. or failing that, if I can renew everything, change it throughout the domain.

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [October 5, 2021, 4:56am UTC](https://community.letsencrypt.org/t/problems-with-renew-ssl-error-400-pending-hestia-control-panel/161916/4 "2021-10-05T04:56:10Z")

</div>

> [@nomopo](#):
>
> The idea is to use an SSL of yours for the mail. Just for the mail.

Good, then that simplifies things [no need to install the cert into any web service].  
So we only have to obtain the cert.  
The simplest way is via HTTP authentication.  
Since "mail.servicio-tecnico-autorizado.pro" resolves to an IP that has a working web service:

```nohighlight
curl -Iki http://mail.servicio-tecnico-autorizado.pro/
HTTP/1.1 200 OK
Server: nginx

```

we can use that web service to get the cert.

Let's start by reviewing the `nginx` configuration with:  
`sudo nginx -T`

---

<div class="post-metadata">

**Author:** ![nomopo](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/nomopo/32/54114_2.png) [@nomopo](https://community.letsencrypt.org/u/nomopo)\
**Post date:** [October 6, 2021, 6:10am UTC](https://community.letsencrypt.org/t/problems-with-renew-ssl-error-400-pending-hestia-control-panel/161916/5 "2021-10-06T06:10:34Z")

</div>

It doesn't work. i have this error always,  
Error: Let's Encrypt validation status 400 (mail.servicio-tecnico-autorizado.pro). Details: Unable to update challenge :: authorization must be pending

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [October 6, 2021, 6:26am UTC](https://community.letsencrypt.org/t/problems-with-renew-ssl-error-400-pending-hestia-control-panel/161916/6 "2021-10-06T06:26:04Z")

</div>

Sorry, I don't know enough about `hestia cp` to help with that error:

> [@nomopo](#):
>
> Details: Unable to update challenge :: authorization must be pending

Maybe someone will come by who knows more...

---

<div class="post-metadata">

**Author:** ![nomopo](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/nomopo/32/54114_2.png) [@nomopo](https://community.letsencrypt.org/u/nomopo)\
**Post date:** [October 6, 2021, 8:15am UTC](https://community.letsencrypt.org/t/problems-with-renew-ssl-error-400-pending-hestia-control-panel/161916/7 "2021-10-06T08:15:14Z")

</div>

the problem is that always are in pending.... And if i renew it a lot of times i have a 429 Error from you.

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [October 6, 2021, 8:28am UTC](https://community.letsencrypt.org/t/problems-with-renew-ssl-error-400-pending-hestia-control-panel/161916/8 "2021-10-06T08:28:47Z")

</div>

I see the problem.  
You should STOP using the production system to TEST.  
There is a staging system for that.

“_The definition of insanity is doing the same thing over and over again and expecting different results._"  
-Albert Einstein

---

<div class="post-metadata">

**Author:** ![nomopo](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/nomopo/32/54114_2.png) [@nomopo](https://community.letsencrypt.org/u/nomopo)\
**Post date:** [October 6, 2021, 8:42am UTC](https://community.letsencrypt.org/t/problems-with-renew-ssl-error-400-pending-hestia-control-panel/161916/9 "2021-10-06T08:42:00Z")

</div>

the problem is that this servers has been worked fine since 1 october…. And i don’t know why it has been crashed!!!! And i don’t know if really it’s crashed...

---

<div class="post-metadata">

**Author:** ![eva2000](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/eva2000/32/289_2.png) [@eva2000](https://community.letsencrypt.org/u/eva2000)\
**Post date:** [October 6, 2021, 8:44am UTC](https://community.letsencrypt.org/t/problems-with-renew-ssl-error-400-pending-hestia-control-panel/161916/10 "2021-10-06T08:44:22Z")

</div>

Probably best to ask at [https://forum.hestiacp.com/](https://forum.hestiacp.com/) i.e. [Search results for 'status 400 order:latest' - Hestia Control Panel - Discourse](https://forum.hestiacp.com/search?q=status%20400%20order%3Alatest)

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [November 19, 2021, 5:54pm UTC](https://community.letsencrypt.org/t/problems-with-renew-ssl-error-400-pending-hestia-control-panel/161916/11 "2021-11-19T17:54:49Z")

</div>

Split this topic on November 19, 2021, 5:54pm UTC

A post was merged into an existing topic: [Certificates wont renew, 400 Unable to update](https://community.letsencrypt.org/t/certificates-wont-renew-400-unable-to-update/165867/9)
