# Update on Node-RED SSL using Letsencrypt & Certbot

**URL:** <https://discourse.nodered.org/t/update-on-node-red-ssl-using-letsencrypt-certbot/77208>\
**Category:** General\
**Tags:** http-request, security\
**Created:** [3 April 2023 16:00 UTC](https://discourse.nodered.org/t/update-on-node-red-ssl-using-letsencrypt-certbot/77208 "2023-04-03T16:00:51Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew4891](https://avatars.discourse-cdn.com/v4/letter/a/34f0e0/32.png) [@Andrew4891](https://discourse.nodered.org/u/Andrew4891)\
**Post date:** [3 April 2023 16:00 UTC](https://discourse.nodered.org/t/update-on-node-red-ssl-using-letsencrypt-certbot/77208/1 "2023-04-03T16:00:51Z")

</div>

Hi there,  
I used so far for more than 1 year the following solution to automatically create certificate for NodeRed access over Let's Certificate

> [@Node-RED SSL using Letsencrypt & Certbot](https://discourse.nodered.org/t/node-red-ssl-using-letsencrypt-certbot/17606/58):
>
> Yes Just follow the guide, it explains what certificates to use. The fullchain.pem contains the cert.pem and the chain.pem which is needed for correct validation. See [Letsencrypt chain.pem or trusted root list cert? - #10 by JuergenAuer - Help - Let's Encrypt Community Support](https://community.letsencrypt.org/t/letsencrypt-chain-pem-or-trusted-root-list-cert/105921/10)

Unluckly even if the certificate update is supposed to be renews on a 30 days before the current certificate is going to expire, it is now since 2,5 months the certificate is not being changed.  
Forcing the certificate creation it is working properly but always creating a file elapsing on April, 2023 (on the 18th).  
Do you have any idea why this is happening?  
I wanted to write on the above mentioned post but it is quite old and have been closed 2years ago.  
Any help would be really appreciated.  
Andrea

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [3 April 2023 19:27 UTC](https://discourse.nodered.org/t/update-on-node-red-ssl-using-letsencrypt-certbot/77208/2 "2023-04-03T19:27:22Z")

</div>

If you are using certbot, it appears to have a systemd service which means that you should be able to check its logs.

Some more info here: [Cerbot cron job? - Help - Let's Encrypt Community Support](https://community.letsencrypt.org/t/cerbot-cron-job/23895)

---

<div class="post-metadata">

**Author:** ![Andrew4891](https://avatars.discourse-cdn.com/v4/letter/a/34f0e0/32.png) [@Andrew4891](https://discourse.nodered.org/u/Andrew4891)\
**Post date:** [4 April 2023 15:19 UTC](https://discourse.nodered.org/t/update-on-node-red-ssl-using-letsencrypt-certbot/77208/3 "2023-04-04T15:19:02Z")

</div>

Hi there  
I did actually checked the log file comparing the last time the certification got renewed correctly and when it is failing.  
The first difference i can found is the invalid status that you can see in the screenshot here attached.  
Seems there is error in validating the data.  
Any idea which could be the reason?  
Thank you so much for any help.  
Andrea

> Blockquote
> 
> ![IMG_20230404_171536~2](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/2/329b9f03f498a5daabf0ea39bb768fb5069d0dae.jpeg)

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [4 April 2023 15:33 UTC](https://discourse.nodered.org/t/update-on-node-red-ssl-using-letsencrypt-certbot/77208/4 "2023-04-04T15:33:32Z")

</div>

Sorry, that doesn't mean anything to me - I don't use certbot but rather the simpler `acme.sh` on a cron shedule that I've had set up for years now with no hicups.

Hopefully someone who does use certbot can help further.

---

<div class="post-metadata">

**Author:** ![Andrew4891](https://avatars.discourse-cdn.com/v4/letter/a/34f0e0/32.png) [@Andrew4891](https://discourse.nodered.org/u/Andrew4891)\
**Post date:** [4 April 2023 20:54 UTC](https://discourse.nodered.org/t/update-on-node-red-ssl-using-letsencrypt-certbot/77208/5 "2023-04-04T20:54:18Z")

</div>

I was trying to change the topic title since this is not related specifically to nodered but to certbot.  
By the way seems i cannot change it.  
If a moderator can change it to Certbot and let's encypt issue on periodical release, that would be perfect and mote understandable for other people as well.  
Thanks  
Andrea

---

<div class="post-metadata">

**Author:** ![Andrew4891](https://avatars.discourse-cdn.com/v4/letter/a/34f0e0/32.png) [@Andrew4891](https://discourse.nodered.org/u/Andrew4891)\
**Post date:** [11 April 2023 20:18 UTC](https://discourse.nodered.org/t/update-on-node-red-ssl-using-letsencrypt-certbot/77208/6 "2023-04-11T20:18:33Z")

</div>

Hi All,  
Seems I solved.  
The problem I had deactivated a port forwarding rule on the router necessary to get the inbound connection necessary for the certificate renewal.  
Hope this can be of help for someone else in the future.  
Andrew

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [25 April 2023 20:19 UTC](https://discourse.nodered.org/t/update-on-node-red-ssl-using-letsencrypt-certbot/77208/7 "2023-04-25T20:19:26Z")

</div>

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