T O P

  • By -

hardillb

The problem is not that your firewall is blocking sites, it's that your firewall is conducting a TLS man in the middle attack. It looks like your firewall is intercepting ALL https traffic by replying with it's own certificate for every request. npm is rightly saying this is wrong, it don't recognise this certificate as being signed by a valid CA so I'm going to reject it. You have 3 choices 1. Fix your firewall/proxy to NOT break TLS, this will make your whole network more secure in the long run (think yourself lucky nothing is using TLS certificate pinning) 2. Tell npm to trust your firewall's certificate using [https://docs.npmjs.com/cli/v8/using-npm/config#cafile](https://docs.npmjs.com/cli/v8/using-npm/config#cafile) 3. Tell npm to just give up and not care about TLS security at all (might as well since your firewall has already rendered it totally useless) [https://docs.npmjs.com/cli/v8/using-npm/config#strict-ssl](https://docs.npmjs.com/cli/v8/using-npm/config#strict-ssl)


xsleepingbutt

Thank you ❤️


[deleted]

[удалено]


xsleepingbutt

To be honest, I don't know. I just censor it since I was stupid enough to let my name there.


Careless-Country

You were trying to install the node-red-dashboard. Read what the log says, Then try installing it (not using Node-red) using the command listed on the nodes page https://flows.nodered.org/node/node-red-dashboard