# \[ANNOUNCE\] node-red-contrib-ui-web-push: beta version

**URL:** https://discourse.nodered.org/t/announce-node-red-contrib-ui-web-push-beta-version/24553
**Category:** Share Your Nodes
**Created:** [9 April 2020 21:46 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-web-push-beta-version/24553 "2020-04-09T21:46:15Z")
**Posts on this page:** 1
**Showing post:** 76

<div class="post-metadata">

### Author: ![Jean-Luc](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jean-luc/32/89996_2.png) [@Jean-Luc](https://discourse.nodered.org/u/Jean-Luc)
#### Post date: [16 April 2020 10:32 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-web-push-beta-version/24553/76 "2020-04-16T10:32:56Z")

</div>

Hello Bart,  
To be able to use **letsencrypt** as described in this post below and then **forget about it afterwards** is probably the best way for the user.  
Keep in mind that certificates have an expiry date and must be renewed before that date or nothing works anymore.

Focus on that, I'll try to use letsencrypt to be recognized by the CAs loaded in the browsers.

I wonder if it works with Mac/Safari, which is always a little bit "different".

> [@Node-RED SSL using Letsencrypt & Certbot](https://discourse.nodered.org/t/node-red-ssl-using-letsencrypt-certbot/17606):
>
> I've written this up in case it helps other who may wish to secure their node-RED online presence, by using SSL certificates. The installation uses Letsencrypt to issue the certificates and also Certbot to fully automate and handle renewals - so it's a fit & forget solution. Pre-requisites I've started with a RPi3b+ and a fresh 'Buster' operating system, with node-RED installed via the official script. Because node-RED is going to provide my online presence, no other webserver (such as apach…

---

_[View the full topic](https://discourse.nodered.org/t/announce-node-red-contrib-ui-web-push-beta-version/24553)._