Ben Hardill

No, it stalled. I'll try and have another look this week

@Simonefardella I have a fix that needs testing with as many different HTTP servers as possible. If you can download the file attached to this comments and (backup first) replace...

What version of docker are you running? also can you confirm you are running a 32bit version of the Raspberry Pi OS?

Probable duplicate of https://github.com/node-red/node-red-docker/issues/296

Does adding `--security-opt=seccomp=unconfined` to the `docker run` command work?

@DanielWeigl & @snkku Can you run the following please: `scmp_sys_resolver -a arm clock_gettime64` And update with the output and also see if you can work out what version of libseccomp...

`sudo scmp_sys_resolver -a arm clock_gettime64` is not meant to be a fix, it is a test to see if seccomp supports 64bit time. The correct solution is upgrade to Bullseye,...

Leave it here, we can move it later if needed. What we do need is an approach to profiling the app in a way that we can easily link up...

I will debug this at the weekend, I 90+% think I know what the problem is (re-encrypting creds when not needed/wanted)

The work around to this is when you copy the `settings.js`, `flows.json` & `flows_cred.json` to the new machine in `/home/pi/.node-red` you should also make sure the `/home/pi/.node-red/.config.runtime.json` file is deleted....