# Rocketchat not renew https after 3 months

**URL:** <https://forums.rocket.chat/t/rocketchat-not-renew-https-after-3-months/22852>\
**Category:** Community Support\
**Created:** [May 11, 2026, 9:37am UTC](https://forums.rocket.chat/t/rocketchat-not-renew-https-after-3-months/22852 "2026-05-11T09:37:11Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![minix](https://avatars.discourse-cdn.com/v4/letter/m/2bfe46/32.png) [@minix](https://forums.rocket.chat/u/minix)\
**Post date:** [May 11, 2026, 9:37am UTC](https://forums.rocket.chat/t/rocketchat-not-renew-https-after-3-months/22852/1 "2026-05-11T09:37:11Z")

</div>

### Description

After 3 months RC doesnt renew https certificate. How repair it? Help please!

### Server Setup Information

- Version of Rocket.Chat Server: 7.13.5
- Operating System: ubuntu
- Deployment Method: snap
- Number of Running Instances:
- DB Replicaset Oplog:
- NodeJS Version:
- MongoDB Version:
- Proxy: apache
- Firewalls involved:

### Any additional Information

 ![Immagine 2026-05-11 113629](https://us1.discourse-cdn.com/flex021/uploads/rocketchat/original/2X/c/cbf893db810ff1706ae2f43930be2208a5bf1c3b.jpeg)

---

<div class="post-metadata">

**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\
**Post date:** [May 11, 2026, 11:24am UTC](https://forums.rocket.chat/t/rocketchat-not-renew-https-after-3-months/22852/2 "2026-05-11T11:24:16Z")

</div>

First I can’t see what is broken with renewal - you need more logs.

Your ulimit error:

> <https://stackoverflow.com/questions/49632581/fix-with-ulimit-n-8192>

You should migrate off snaps as soon as possible - they are not a supported install anymore. Docker/Podman should be used.

> **[Deploy Rocket.Chat: Setup and Guide](https://docs.rocket.chat/docs/deploy-rocketchat)**
>
> Follow step-by-step instructions to deploy Rocket.Chat on your preferred environment with secure, scalable, and efficient collaboration setup

As per this:

> **Rocket.Chat provides no support for these additional deployment methods. Using them may lead to unexpected challenges or compatibility issues.**
> 
> - [Deploy with Snaps](https://docs.rocket.chat/v1/docs/deploy-with-snaps): Deploy Rocket.Chat with Snaps quickly for testing.

---

<div class="post-metadata">

**Author:** ![minix](https://avatars.discourse-cdn.com/v4/letter/m/2bfe46/32.png) [@minix](https://forums.rocket.chat/u/minix)\
**Post date:** [May 11, 2026, 1:44pm UTC](https://forums.rocket.chat/t/rocketchat-not-renew-https-after-3-months/22852/3 "2026-05-11T13:44:53Z")

</div>

Hi reetp, solved the ulimits but now dont know how generate the cert.

Here the snap logs caddy:

2026-05-11T15:38:00+02:00 rocketchat-server.rocketchat-caddy[1414]: {“level”:“info”,“ts”:1778506680.2406948,“logger”:“tls”,“msg”:“served key authentication certificate”,“server\_name”:“rocket.myserver.it”,“challenge”:“tls-alpn-01”,“remote”:“13.50.14.197:58348”,“distributed”:false}  
2026-05-11T15:38:00+02:00 rocketchat-server.rocketchat-caddy[1414]: {“level”:“info”,“ts”:1778506680.5527573,“logger”:“tls”,“msg”:“served key authentication certificate”,“server\_name”:“rocket.myserver.it”,“challenge”:“tls-alpn-01”,“remote”:“3.137.156.132:52668”,“distributed”:false}  
2026-05-11T15:38:00+02:00 rocketchat-server.rocketchat-caddy[1414]: {“level”:“info”,“ts”:1778506680.6158233,“logger”:“tls”,“msg”:“served key authentication certificate”,“server\_name”:“rocket.myserver.it”,“challenge”:“tls-alpn-01”,“remote”:“54.179.213.147:62418”,“distributed”:false}  
2026-05-11T15:38:00+02:00 rocketchat-server.rocketchat-caddy[1414]: {“level”:“info”,“ts”:1778506680.6475992,“logger”:“tls”,“msg”:“served key authentication certificate”,“server\_name”:“rocket.myserver.it”,“challenge”:“tls-alpn-01”,“remote”:“54.200.80.116:27528”,“distributed”:false}  
2026-05-11T15:38:01+02:00 rocketchat-server.rocketchat-caddy[1414]: {“level”:“error”,“ts”:1778506681.4214776,“logger”:“tls.issuance.acme.acme\_client”,“msg”:“challenge failed”,“identifier”:“rocket.myserver.it”,“challenge\_type”:“tls-alpn-01”,“status\_code”:403,“problem\_type”:“urn:ietf:params:acme:error:caa”,“error”:“While processing CAA for rocket.myserver.it: CAA record for myserver.it prevents issuance”}  
2026-05-11T15:38:01+02:00 rocketchat-server.rocketchat-caddy[1414]: {“level”:“error”,“ts”:1778506681.4215336,“logger”:“tls.issuance.acme.acme\_client”,“msg”:“validating authorization”,“identifier”:“rocket.myserver.it”,“error”:“[rocket.myserver.it] authorization failed: HTTP 403 urn:ietf:params:acme:error:caa - While processing CAA for rocket.myserver.it: CAA record for myserver.it prevents issuance”,“order”:“[https://acme-staging-v02.api.letsencrypt.org/acme/order/291274553/37715054123",“attempt”:1,"max\_attempts](https://acme-staging-v02.api.letsencrypt.org/acme/order/291274553/37715054123%22,%22attempt%22:1,%22max_attempts)”:3}  
2026-05-11T15:38:01+02:00 rocketchat-server.rocketchat-caddy[1414]: {“level”:“error”,“ts”:1778506681.4215693,“logger”:“tls.obtain”,“msg”:“could not get certificate from issuer”,“identifier”:“rocket.myserver.it”,“issuer”:“acme-v02.api.letsencrypt.org-directory”,“error”:“HTTP 403 urn:ietf:params:acme:error:caa - While processing CAA for rocket.myserver.it: CAA record for myserver.it prevents issuance”}  
2026-05-11T15:38:01+02:00 rocketchat-server.rocketchat-caddy[1414]: {“level”:“warn”,“ts”:1778506681.4217012,“logger”:“tls.issuance.zerossl”,“msg”:“missing email address for ZeroSSL; it is strongly recommended to set one for next time”}  
2026-05-11T15:38:01+02:00 rocketchat-server.rocketchat-caddy[1414]: {“level”:“error”,“ts”:1778506681.5729482,“logger”:“tls.obtain”,“msg”:“could not get certificate from issuer”,“identifier”:“rocket.myserver.it”,“issuer”:“acme.zerossl.com-v2-DV90”,“error”:“account pre-registration callback: failed getting EAB credentials: HTTP 422: caddy\_legacy\_user\_removed (code 2977)”}  
2026-05-11T15:38:01+02:00 rocketchat-server.rocketchat-caddy[1414]: {“level”:“error”,“ts”:1778506681.5730047,“logger”:“tls.obtain”,“msg”:“will retry”,“error”:“[rocket.myserver.it] Obtain: account pre-registration callback: failed getting EAB credentials: HTTP 422: caddy\_legacy\_user\_removed (code 2977)”,“attempt”:2,“retrying\_in”:120,“elapsed”:68.679704411,“max\_duration”:2592000}  
root@Linux127:/home/administrator#

---

<div class="post-metadata">

**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\
**Post date:** [May 11, 2026, 2:02pm UTC](https://forums.rocket.chat/t/rocketchat-not-renew-https-after-3-months/22852/4 "2026-05-11T14:02:35Z")

</div>

Not sure on your whole setup.

However your issue starts here - you should check your DNS.

> CAA record for myserver.it prevents issuance

You also should read here, and the caddy docs.

> **[Deploy Rocket Chat with Snaps for Secure Messaging](https://docs.rocket.chat/v1/docs/deploy-with-snaps#step-2-enable-https)**
>
> Install Rocket Chat using Snaps for fast, secure deployment. Enable reliable messaging, open source flexibility, and scalable collaboration in any environment.

---

<div class="post-metadata">

**Author:** ![minix](https://avatars.discourse-cdn.com/v4/letter/m/2bfe46/32.png) [@minix](https://forums.rocket.chat/u/minix)\
**Post date:** [May 12, 2026, 1:59pm UTC](https://forums.rocket.chat/t/rocketchat-not-renew-https-after-3-months/22852/5 "2026-05-12T13:59:32Z")

</div>

Hi Reept, we use RC community edition since Covid era, 2022. Caddy renew on every 90 days certificates. This until last week, when Caddy must renew certs. About 2 months ago we have upgrade (automatically) RC to 7.13.5 I think the problem is in this release because RC-Caddy seems thinking as Caddy V2. I’ve included my Caddfile (the same since 2022). Thanks

 ![Immagine 2026-05-12 155854](https://us1.discourse-cdn.com/flex021/uploads/rocketchat/original/2X/6/6f2c0bb59030c3185979abab6cf90170e484b9b6.jpeg)

---

<div class="post-metadata">

**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\
**Post date:** [May 12, 2026, 4:20pm UTC](https://forums.rocket.chat/t/rocketchat-not-renew-https-after-3-months/22852/6 "2026-05-12T16:20:30Z")

</div>

They look like the have prioritised v2 over v1 for some while.  
You really need to keep up to date.

> The Snap package includes both **Caddy v2** (preferred) and **Caddy v1** (end-of-life), with v2 prioritized.

> **[Deploy Rocket Chat with Snaps for Secure Messaging](https://docs.rocket.chat/docs/deploy-with-snaps#customizing-caddy-or-using-an-alternative-http-proxy)**
>
> Install Rocket Chat using Snaps for fast, secure deployment. Enable reliable messaging, open source flexibility, and scalable collaboration in any environment.

I suspect you should be using this in your config file now:

[`reverse_proxy`](https://caddyserver.com/docs/caddyfile/directives/reverse_proxy "Directive")

Not I have never used it - just read the docs.

If your certs have expired I think you will need to go back to http, get a new cert and then back to https. See the Rocket docs.

---

<div class="post-metadata">

**Author:** ![minix](https://avatars.discourse-cdn.com/v4/letter/m/2bfe46/32.png) [@minix](https://forums.rocket.chat/u/minix)\
**Post date:** [May 14, 2026, 9:40am UTC](https://forums.rocket.chat/t/rocketchat-not-renew-https-after-3-months/22852/7 "2026-05-14T09:40:20Z")

</div>

Hi all, SOLVED. Just missing a CAA record in DNS. Added CAA with [Letsencrypt.org](http://Letsencrypt.org) au

Thanks all

---

<div class="post-metadata">

**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\
**Post date:** [May 14, 2026, 3:16pm UTC](https://forums.rocket.chat/t/rocketchat-not-renew-https-after-3-months/22852/8 "2026-05-14T15:16:24Z")

</div>

> [@minix](#):
>
> Just missing a CAA record in DNS.

vvvvvvvvvvvvvvvvvvvvvvvvvvvvv

> [@reetp](#):
>
> However your issue starts here - you should check your DNS.

Glad you got it fixed, but I would check your Caddy setup and get up to date.
