Both @torchard and I have never come across this one.
Did some reading and seems that its linked to the EPIC (or, more accurately - since it has nothing to do specifically with EPIC - the device running nodeJS) certificate store or if you are using VPN or web proxy.
I think this explains why we have not seen it in house (yet). We don’t run either VPN much and for sure don’t have a web proxy.
Do you have an IT department that might be able to help work out why their certificate is over riding the EPIC certificate store?
There are some possible shell work arounds, but I am not sure you have shell installed on this EPIC?
Fixed: The issue was in our company’s network firewall.
Here is IT’s explanation.
The controller is missing a certificate from the firewall that allows it to perform virus scanning on the encrypted traffic. When a device goes out to the internet the traffic is usually encrypted from the device (controller in this instance) to the internet server and all the firewall can see is encrypted traffic. The firewall we use has decryption capabilities so the connection from the device to the firewall is encrypted using our certificate, then is scanned for viruses/malware, and then the connection from the firewall to the internet server is encrypted. This only works if the encryption key from the firewall is installed on the device. We use Active Directory to push the cert to computers but it needs to be manually installed on any device not in active directory.
In other words: Don’t do any banking at work (or anything else you don’t want your employer to see.) This is basically a corporate man-in-the-middle attack.
