# Ajuda com Node-RED no HASSIO **URL:** \ **Category:** Node-Red\ **Created:** [6 Fevereiro , 2019 11:38 UTC](https://forum.cpha.pt/t/ajuda-com-node-red-no-hassio/1850 "2019-02-06T11:38:15Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![jruibarroso](https://forum.cpha.pt/user_avatar/forum.cpha.pt/jruibarroso/32/1479_2.png) [@jruibarroso](https://forum.cpha.pt/u/jruibarroso)\ **Post date:** [6 Fevereiro , 2019 11:38 UTC](https://forum.cpha.pt/t/ajuda-com-node-red-no-hassio/1850/1 "2019-02-06T11:38:15Z")
boas pessoal, instalei o Node-red no HASSIO como o tuturial, ja me aparece na lateral esquerda o Node-RED com o icon, quando clico abre nova pagina em [https://hassio.local:1880](https://hassio.local:1880) mas o chrome diz “nao é possivel aceder a este site” esta é minha config do Node-RED ``` { "ssl": true, "certfile": "fullchain.pem", "keyfile": "privkey.pem", "users": [ { "username": "meu user name", "password": "minha pass", "permissions": "*" } ], "http_node_user": [ { "username": "meu user name", "password": "minha pass" } ], "projects": false, "install_packages": [], "install_nodes": [ "node-red-contrib-home-assistant" ], "uninstall_nodes": [] } ``` ---
**Author:** ![jruibarroso](https://forum.cpha.pt/user_avatar/forum.cpha.pt/jruibarroso/32/1479_2.png) [@jruibarroso](https://forum.cpha.pt/u/jruibarroso)\ **Post date:** [6 Fevereiro , 2019 11:43 UTC](https://forum.cpha.pt/t/ajuda-com-node-red-no-hassio/1850/2 "2019-02-06T11:43:09Z")
[img] ![Anota%C3%A7%C3%A3o%202019-02-06%20114231](https://forum.cpha.pt/uploads/default/original/2X/4/4977d10a291a41e5769a9fb8b04f8ec3bf403413.jpeg) ![Capturar](https://forum.cpha.pt/uploads/default/original/2X/2/2c605d547f666eb5d00a0208c84b86706cd62ba8.png) resposta : **hassio.local** recusou estabelecer ligação. Log [INFO] Enabling SSL [INFO] Updating IDE Users [INFO] Adding IDE User jruibarroso [INFO] Updating HTTP Node User [INFO] Adding HTTP Node User jruibarroso [INFO] Disabling Projects [INFO] Attempting to install/update nodes: node-red-contrib-home-assistant npm info it worked if it ends with ok npm info using [npm@5.0.3](mailto:npm@5.0.3) npm info using [node@v8.1.3](mailto:node@v8.1.3) npm http fetch GET 200 [https://registry.npmjs.org/node-red-contrib-home-assistant](https://registry.npmjs.org/node-red-contrib-home-assistant) 417ms npm http fetch GET 200 [https://registry.npmjs.org/node-red-contrib-home-assistant/-/node-red-contrib-home-assistant-0.3.2.tgz](https://registry.npmjs.org/node-red-contrib-home-assistant/-/node-red-contrib-home-assistant-0.3.2.tgz) 314ms npm info lifecycle [node-red-contrib-home-assistant@0.3.2~preuninstall](mailto:node-red-contrib-home-assistant@0.3.2~preuninstall): [node-red-contrib-home-assistant@0.3.2](mailto:node-red-contrib-home-assistant@0.3.2) npm info lifecycle [node-red-contrib-home-assistant@0.3.2~uninstall](mailto:node-red-contrib-home-assistant@0.3.2~uninstall): [node-red-contrib-home-assistant@0.3.2](mailto:node-red-contrib-home-assistant@0.3.2) npm info lifecycle [node-red-contrib-home-assistant@0.3.2~postuninstall](mailto:node-red-contrib-home-assistant@0.3.2~postuninstall): [node-red-contrib-home-assistant@0.3.2](mailto:node-red-contrib-home-assistant@0.3.2) npm info lifecycle [node-red-contrib-home-assistant@0.3.2~preinstall](mailto:node-red-contrib-home-assistant@0.3.2~preinstall): [node-red-contrib-home-assistant@0.3.2](mailto:node-red-contrib-home-assistant@0.3.2) npm info linkStuff [node-red-contrib-home-assistant@0.3.2](mailto:node-red-contrib-home-assistant@0.3.2) npm info lifecycle [node-red-contrib-home-assistant@0.3.2~install](mailto:node-red-contrib-home-assistant@0.3.2~install): [node-red-contrib-home-assistant@0.3.2](mailto:node-red-contrib-home-assistant@0.3.2) npm info lifecycle [node-red-contrib-home-assistant@0.3.2~postinstall](mailto:node-red-contrib-home-assistant@0.3.2~postinstall): [node-red-contrib-home-assistant@0.3.2](mailto:node-red-contrib-home-assistant@0.3.2) npm WARN saveError ENOENT: no such file or directory, open ‘/share/node-red/package.json’ npm info lifecycle undefined~preshrinkwrap: undefined npm info lifecycle undefined~shrinkwrap: undefined npm info lifecycle undefined~postshrinkwrap: undefined npm WARN enoent ENOENT: no such file or directory, open ‘/share/node-red/package.json’ npm WARN node-red No description npm WARN node-red No repository field. npm WARN node-red No README data npm WARN node-red No license field. npm info ok npm info it worked if it ends with ok npm info using [npm@5.0.3](mailto:npm@5.0.3) npm info using [node@v8.1.3](mailto:node@v8.1.3) npm info lifecycle [node-red-docker@1.0.0~prestart](mailto:node-red-docker@1.0.0~prestart): [node-red-docker@1.0.0](mailto:node-red-docker@1.0.0) npm info lifecycle [node-red-docker@1.0.0~start](mailto:node-red-docker@1.0.0~start): [node-red-docker@1.0.0](mailto:node-red-docker@1.0.0) > [node-red-docker@1.0.0](mailto:node-red-docker@1.0.0) start /usr/src/node-red > node $NODE\_OPTIONS node\_modules/node-red/red.js -v $FLOWS “–userDir” “/share/node-red” Error loading settings file: /share/node-red/settings.js { Error: ENOENT: no such file or directory, open ‘/ssl/privkey.pem’ at Object.fs.openSync (fs.js:651:18) at Object.fs.readFileSync (fs.js:553:33) at Object. (/share/node-red/settings.js:137:17) at Module.\_compile (module.js:569:30) at Object.Module.\_extensions..js (module.js:580:10) at Module.load (module.js:503:32) at tryModuleLoad (module.js:466:12) at Function.Module.\_load (module.js:458:3) at Module.require (module.js:513:17) at require (internal/module.js:11:18) errno: -2, code: ‘ENOENT’, syscall: ‘open’, path: ‘/ssl/privkey.pem’ } npm info lifecycle [node-red-docker@1.0.0~poststart](mailto:node-red-docker@1.0.0~poststart): [node-red-docker@1.0.0](mailto:node-red-docker@1.0.0) npm info ok ---
**Author:** ![j\_assuncao](https://forum.cpha.pt/user_avatar/forum.cpha.pt/j_assuncao/32/3_2.png) [@j\_assuncao](https://forum.cpha.pt/u/j_assuncao)\ **Post date:** [6 Fevereiro , 2019 13:40 UTC](https://forum.cpha.pt/t/ajuda-com-node-red-no-hassio/1850/3 "2019-02-06T13:40:53Z")
@jruibarroso quando publicares código deves sublinhar o texto que queres transformar em código e clicar no icone \. Deverá existir um espaço antes e outro depois do bloco de código para que funcione correctamente. O código em Yaml é muito sensível aos espaçamentos e sem o código devidamente formatado não te poderemos ajudar. ---
**Author:** ![jruibarroso](https://forum.cpha.pt/user_avatar/forum.cpha.pt/jruibarroso/32/1479_2.png) [@jruibarroso](https://forum.cpha.pt/u/jruibarroso)\ **Post date:** [6 Fevereiro , 2019 14:57 UTC](https://forum.cpha.pt/t/ajuda-com-node-red-no-hassio/1850/4 "2019-02-06T14:57:07Z")
só tinha 5 linhas de codigo yaml , ja removi o que tenho é só o LOG ---
**Author:** ![j\_assuncao](https://forum.cpha.pt/user_avatar/forum.cpha.pt/j_assuncao/32/3_2.png) [@j\_assuncao](https://forum.cpha.pt/u/j_assuncao)\ **Post date:** [6 Fevereiro , 2019 15:02 UTC](https://forum.cpha.pt/t/ajuda-com-node-red-no-hassio/1850/5 "2019-02-06T15:02:37Z")
Tens a config do Node-Red na primeira publicação. ---
**Author:** ![jruibarroso](https://forum.cpha.pt/user_avatar/forum.cpha.pt/jruibarroso/32/1479_2.png) [@jruibarroso](https://forum.cpha.pt/u/jruibarroso)\ **Post date:** [6 Fevereiro , 2019 16:53 UTC](https://forum.cpha.pt/t/ajuda-com-node-red-no-hassio/1850/6 "2019-02-06T16:53:48Z")
já corrigi , sou novo nestas andanças e nao sabia , peço desculpa ---
**Author:** ![j\_assuncao](https://forum.cpha.pt/user_avatar/forum.cpha.pt/j_assuncao/32/3_2.png) [@j\_assuncao](https://forum.cpha.pt/u/j_assuncao)\ **Post date:** [6 Fevereiro , 2019 18:12 UTC](https://forum.cpha.pt/t/ajuda-com-node-red-no-hassio/1850/7 "2019-02-06T18:12:25Z")
O problema está nos URLs que usas. Não deves usar o `hassio.local` mas sim o endereço IP da máquina onde está o NR está instalado seguido de 1880 (`http://192.168.xxx.xxx:1880`). ---
**Author:** ![system](https://forum.cpha.pt/user_avatar/forum.cpha.pt/system/32/2_2.png) [@system](https://forum.cpha.pt/u/system)\ **Post date:** [7 Maio , 2019 18:21 UTC](https://forum.cpha.pt/t/ajuda-com-node-red-no-hassio/1850/8 "2019-05-07T18:21:55Z")
Este tópico foi automaticamente fechado 90 dias após a última resposta. Novas respostas não são permitidas.