You are ignoring the very obvious error that is shown repeatedly in that log file.
In fact, you don't need to be messing with startup files as Node-RED is clearly trying to start but is crashing repeatedly.
29 May 21:44:37 - [error] [http request:Load JPG image from axis] Error: connect EHOSTUNREACH 192.168.1.46:80
29 May 21:44:37 - [red] Uncaught Exception:
29 May 21:44:37 - Error: EACCES: permission denied, mkdir '//pki'
at Object.mkdirSync (fs.js:752:3)
at _verify_serverCertificate (/opt/plcnext/appshome/data/60002172000051/lib/node_modules/node-red-contrib-iiot-opcua/node_modules/node-opcua-client/src/client_base.js:339:12)
at /opt/plcnext/appshome/data/60002172000051/lib/node_modules/node-red-contrib-iiot-opcua/node_modules/node-opcua-client/src/client_base.js:624:13
at /opt/plcnext/appshome/data/60002172000051/lib/node_modules/node-red-contrib-iiot-opcua/node_modules/node-opcua-client/src/client_base.js:248:9
at /opt/plcnext/appshome/data/60002172000051/lib/node_modules/node-red-contrib-iiot-opcua/node_modules/async/dist/async.js:3888:9
at /opt/plcnext/appshome/data/60002172000051/lib/node_modules/node-red-contrib-iiot-opcua/node_modules/async/dist/async.js:473:16
at replenish (/opt/plcnext/appshome/data/60002172000051/lib/node_modules/node-red-contrib-iiot-opcua/node_modules/async/dist/async.js:1006:25)
at iterateeCallback (/opt/plcnext/appshome/data/60002172000051/lib/node_modules/node-red-contrib-iiot-opcua/node_modules/async/dist/async.js:995:17)
at /opt/plcnext/appshome/data/60002172000051/lib/node_modules/node-red-contrib-iiot-opcua/node_modules/async/dist/async.js:969:16
at Immediate.<anonymous> (/opt/plcnext/appshome/data/60002172000051/lib/node_modules/node-red-contrib-iiot-opcua/node_modules/async/dist/async.js:3885:13)
Shows you quite clearly that a node is crashing Node-RED because it doesn't have access to a file that it wants.
In reality no node should do that as all file access should be wrapped such that errors are returned.
The problem lies with the node node-red-contrib-iiot-opcua. You should raise an issue on GitHub for that node.
I believe we have seen multiple issues with that node and it does seem to be causing issues. (apologies if I've confused it with something else).
