# Unable to renew a standalone certificate

**URL:** <https://community.letsencrypt.org/t/unable-to-renew-a-standalone-certificate/42109>\
**Category:** Help\
**Created:** [September 13, 2017, 5:50am UTC](https://community.letsencrypt.org/t/unable-to-renew-a-standalone-certificate/42109 "2017-09-13T05:50:29Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Animesh\_Bulusu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/animesh_bulusu/32/16345_2.png) [@Animesh\_Bulusu](https://community.letsencrypt.org/u/Animesh_Bulusu)\
**Post date:** [September 14, 2017, 2:31am UTC](https://community.letsencrypt.org/t/unable-to-renew-a-standalone-certificate/42109/8 "2017-09-14T02:31:57Z")

</div>

Yes, my blog is a static blog deployed to gitlab servers automatically after every push. In gitlab settings, there is a page to add the .pem file manually

I just ran the following command and uploaded the acme challenge file as instructed and it renewed the certifcate successfully

```
sudo certbot certonly -a manual -d animesh.blog

Cert is due for renewal, auto-renewing...
Renewing an existing certificate
...
To non-interactively renew *all* of your certificates, run
"certbot renew"

```

So I guess this is the only way to renew for a cert created manually. Then to paste again the `.pem` files in gitlab settings manually is quite inconvenient. I will have to find a way to script the authentication process.

---

_[View the full topic](https://community.letsencrypt.org/t/unable-to-renew-a-standalone-certificate/42109)._