# Oct 2024 Cannot update Letsencrypt Certs

**URL:** <https://discourse.mailinabox.email/t/oct-2024-cannot-update-letsencrypt-certs/12400>\
**Category:** Help with Unusual Circumstances\
**Created:** [October 16, 2024, 2:17pm UTC](https://discourse.mailinabox.email/t/oct-2024-cannot-update-letsencrypt-certs/12400 "2024-10-16T14:17:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dlwhitehurst](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/d/ed8c4c/32.png) [@dlwhitehurst](https://discourse.mailinabox.email/u/dlwhitehurst)\
**Post date:** [October 16, 2024, 2:17pm UTC](https://discourse.mailinabox.email/t/oct-2024-cannot-update-letsencrypt-certs/12400/1 "2024-10-16T14:17:38Z")

</div>

I’ve been running MIAB on Ubuntu 22.04 at DigitalOcean for some time now and certs have been being updated as expected. The server has an expired cert now as I tried to place a file in the webroot and could not establish SSL. Anyhow, I tried a --force update with certbot but could not authenticate. I also tried two webroots: I think it’s home/user-data/www/default but I also tried home/user-data/www . Neither one worked. Still can’t authenticate.

Can someone help point me in a direction where I might understand this?

David

---

<div class="post-metadata">

**Author:** ![stylnchris](https://discourse.mailinabox.email/user_avatar/discourse.mailinabox.email/stylnchris/32/2189_2.png) [@stylnchris](https://discourse.mailinabox.email/u/stylnchris)\
**Post date:** [October 16, 2024, 10:46pm UTC](https://discourse.mailinabox.email/t/oct-2024-cannot-update-letsencrypt-certs/12400/2 "2024-10-16T22:46:21Z")

</div>

did you check this out?

> [@Got a problem with a cert not working/renewing properly](https://discourse.mailinabox.email/t/got-a-problem-with-a-cert-not-working-renewing-properly/8818/8):
>
> I had a similar problem and wanted to share what I did to fix it. My issue: My certificates expired today and did not automatically renew. When I tried to provision new ones automatically through the admin panel, nothing seemed to happen. I looked at the feedback a little closer on the screen where I tried to do the provision and noticed something suggesting there was more than one account, and it gave the location of the Let’s Encrypt log: /var/log/letsencrypt/letsencrypt.log It’s a prett…

---

<div class="post-metadata">

**Author:** ![dlwhitehurst](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/d/ed8c4c/32.png) [@dlwhitehurst](https://discourse.mailinabox.email/u/dlwhitehurst)\
**Post date:** [October 17, 2024, 1:35pm UTC](https://discourse.mailinabox.email/t/oct-2024-cannot-update-letsencrypt-certs/12400/3 "2024-10-17T13:35:55Z")

</div>

I did and it’s not the same issue. The duplicate accounts don’t exist in my LE log. I just tried to `sudo mailinabox` and I get …

```auto
usr/local/bin/mailinabox: line 2: cd: /root/mailinabox: No such file or directory
/usr/local/bin/mailinabox: line 3: setup/start.sh: No such file or directory

```

This is very concerning! Any thoughts? I don’t want to lose all my mail and server.

David

---

<div class="post-metadata">

**Author:** ![dlwhitehurst](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/d/ed8c4c/32.png) [@dlwhitehurst](https://discourse.mailinabox.email/u/dlwhitehurst)\
**Post date:** [October 17, 2024, 1:46pm UTC](https://discourse.mailinabox.email/t/oct-2024-cannot-update-letsencrypt-certs/12400/4 "2024-10-17T13:46:03Z")

</div>

Someone has messed with me via `root` I think. I allowed root login for sftp of web files. The /usr/local/bin does contain `mailinabox` but the second line says `cd root/mailinabox` and that’s not there anymore. I certainly hope there’s a github where maybe I can put this stuff back. I’m working now but I’ll be back to check.

---

<div class="post-metadata">

**Author:** ![Player](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/p/e19b73/32.png) [@Player](https://discourse.mailinabox.email/u/Player)\
**Post date:** [October 21, 2024, 12:59am UTC](https://discourse.mailinabox.email/t/oct-2024-cannot-update-letsencrypt-certs/12400/5 "2024-10-21T00:59:15Z")

</div>

The error just looks like they are using a different folder from your setup, nothing immediately concerning.

The output of `certbot renew --dry-run` would be the first step, it’s unclear what is even failing here.