# \[ANNOUNCE\] node-red-contrib-ui-web-push: beta version **URL:** \ **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:** 8\ **Page:** 5

**Author:** ![VinistoisR](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/vinistoisr/32/5778_2.png) [@VinistoisR](https://discourse.nodered.org/u/VinistoisR)\ **Post date:** [18 April 2020 20:34 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-web-push-beta-version/24553/82 "2020-04-18T20:34:16Z")

this node is fantastic, thank you so much for developing it, so we can all say goodbye to Telegram. This is obviously conceptually superior. Have you tested sending short gifs? IMHO all the lets encrypt stuff doesn't belong in node red at all. Users should be using a web proxy that terminates SSL, manages certs, and forwards traffic to node-red. After all, probably a good chunk are using docker, so a simple Traefik container solves all these issues auto-magically. Many hundreds of thousands of services rely on traefik, so they keep it all up to date with lets-encrypt, managing dns or http challenges, and renewals, like complete magic. A bit silly to try to re-invent that wheel inside node-red, when all you'll end up with is a less secure solution anyways. I'll set this up soon and post up my results! ---

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\ **Post date:** [18 April 2020 20:48 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-web-push-beta-version/24553/83 "2020-04-18T20:48:51Z")

Hi, thanks for the feedback! > [@VinistoisR](#): > > Have you tested sending short gifs? Do you mean sending a single image? If so, you can find an example flow on my readme page. > [@VinistoisR](#): > > we can all say goodbye to Telegram I'm not very convinced of that anymore, since Telegram has build native apps for all platforms. So every user can easily use those, without all the ssl setup issues... > [@VinistoisR](#): > > A bit silly to try to re-invent that wheel inside node-red You are absolutely right that a web proxy does the job, but we have to be aware that Node-RED is not only made for users with a massive amount of technical skills. Would have liked to have a single-node solution for less-experienced users, but I'm afraid one or two [issues](https://discourse.nodered.org/t/announce-node-red-contrib-acme-client-early-alpha-version/24983) will prevent me from accomplishing that. Unless somebody can give me the golden tip ... ---

**Author:** ![VinistoisR](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/vinistoisr/32/5778_2.png) [@VinistoisR](https://discourse.nodered.org/u/VinistoisR)\ **Post date:** [18 April 2020 21:09 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-web-push-beta-version/24553/84 "2020-04-18T21:09:44Z")

> [@BartButenaers](#): > > You are absolutely right that a web proxy does the job, but we have to be aware that Node-RED is not only made for users with a massive amount of technical skills. Would have liked to have a single-node solution for less-experienced users, but I'm afraid one or two [issues](https://discourse.nodered.org/t/announce-node-red-contrib-acme-client-early-alpha-version/24983) will prevent me from accomplishing that. Unless somebody can give me the golden tip ... That's exactly why SSL setup should be left to something easy, automatic, and reproducible. It's trivial to provide a docker-compose example that launches node-red and traefik together. Not only that, but it makes it easy to protect node-red with oauth instead of basic auth. There are some _very_ significant risks exposing the node-red port to the web with basic auth. I would call that ill-advised, at best. Encouraging users to do so is asking for trouble. Just so you know, with a traefik proxy setup you don't have to expose the node-red port to the docker host even, and nor do you have to open ports on your firewall. You can have a node-red instance completely unavailable to the internet, and still get an SSL cert using a DNS challenge. And yes, your notifications can _still_ go out to mobile users. ---

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\ **Post date:** [18 April 2020 21:27 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-web-push-beta-version/24553/85 "2020-04-18T21:27:16Z")

> [@VinistoisR](#): > > It's trivial to provide a docker-compose example that launches node-red and traefik together. All that you say makes sense! However from experience I know that lots of the users of my nodes are hobbyists, who won't get Docker or anything like that up and running. But if you know a way for this kind of users to easily setup LetsEncrypt (both with https-01 and dns-01 challenges), don't hesitate to explain the steps in the "_share your project_" category on this forum! The more options we have, the better ... ---

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\ **Post date:** [18 April 2020 21:58 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-web-push-beta-version/24553/86 "2020-04-18T21:58:22Z")

Yes please. That would be a very useful option to have available.. ---

**Author:** ![VinistoisR](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/vinistoisr/32/5778_2.png) [@VinistoisR](https://discourse.nodered.org/u/VinistoisR)\ **Post date:** [18 April 2020 23:16 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-web-push-beta-version/24553/87 "2020-04-18T23:16:52Z")

> [@Node-RED SSL reverse proxy w/ Google Oauth](https://discourse.nodered.org/t/node-red-ssl-reverse-proxy/25103): > > edit: please see [this post](https://discourse.nodered.org/t/node-red-ssl-reverse-proxy/25103/49) for most recent deployment instructions Here's a docker-compose.yml file to deploy Node-RED and Traefik, a reverse proxy that automates fetching, issuing, and renewing free SSL certificates from Let's Encrypt. There are two ways Lets Encrypt verifies that you are the owner of a domain so they can give you a free cert. HTTP validation. Let's Encrypt gives you a token, and you put a file on your web server at http://\/.well-known/acme-challenge/token...… ---

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\ **Post date:** [19 April 2020 06:53 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-web-push-beta-version/24553/88 "2020-04-19T06:53:37Z")

Morning Vinistois, wow that was fast feedback! Will try to digest it today (when I get some time from the wife and kids), but seems to be very well explained at first sight... Thanks a lot for sharing your knowledge on this forum! ---

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\ **Post date:** [8 June 2020 21:46 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-web-push-beta-version/24553/89 "2020-06-08T21:46:22Z")

Closed on 8 June 2020 21:46 UTC This topic was automatically closed after 60 days. New replies are no longer allowed. [Previous page](https://discourse.nodered.org/t/announce-node-red-contrib-ui-web-push-beta-version/24553.md?page=4)