# Scratch 3 and NodeRED working together

**URL:** <https://discourse.nodered.org/t/scratch-3-and-nodered-working-together/8473>\
**Category:** Share Your Projects\
**Created:** [28 February 2019 14:14 UTC](https://discourse.nodered.org/t/scratch-3-and-nodered-working-together/8473 "2019-02-28T14:14:53Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [2 March 2019 11:40 UTC](https://discourse.nodered.org/t/scratch-3-and-nodered-working-together/8473/14 "2019-03-02T11:40:38Z")

</div>

OK -managed to setup NodeRED as https server

> [@Is it possible to use NodeRED as functioning LAN https server?](https://discourse.nodered.org/t/is-it-possible-to-use-nodered-as-functioning-lan-https-server/8078/9):
>
> Spoke too soon frowning Everything worked without https when Scratch 3 running in browser on same machine as NodeRED but when trying to use across a LAN - it wanted webserver to be https again So I edited my settings .js like this ... // The `https` setting requires the `fs` module. Uncomment the following // to make it available: var fs = require("fs") ... https: { key: fs.readFileSync('ca.key'), cert: fs.readFileSync('ca.pem') }, ... httpNodeCors: { ori…

So if you do those changes (don't forget to stick ca.key and ca.pem in /home/pi/.node-red) then it works again

You do have to accept my certs in a webbrowser session 1st so you need to kick the session into life by doing some like  
[https://192.168.0.189:1880/translate?test](https://192.168.0.189:1880/translate?test)  
(replace my address with your Pi one)

No where near as smooth and easy as doing it on one machine 🙂

---

_[View the full topic](https://discourse.nodered.org/t/scratch-3-and-nodered-working-together/8473)._