Ben Hardill

Yep, I've tested again and the NodeJS 20 and 22 builds just never finish on ARMv7 (same as s390x and ARMv6). The NodeJS 18 build works, but that's not helpful...

The next build should have a 32bit ARMv7 build

We have never build ARMv8 32bit containers (and there are no nodejs base containers with that tag https://hub.docker.com/_/node/tags).

You need to: - build the containers yourself - Stick at 3.1.x version - Use the debian based build - Wait for the next spin (most likely 4.0.3)

I have respun the 4.0.2 builds today. There should now be ARMv7 containers in the manifest

@PallaviRayapu Please do not tag people in issues like that, we will review things when we have time. The `settings.js` file doesn't appear to match log output as it has...

There is something else going on here, that sample flow is running correctly for me with a fresh pull of `nodered/node-red:latest` (4.0.5) Are you testing all this on the same...

@Koneisto this is about making HTTP requests to other services, not making requests to routes hosted on Node-RED, please open another issue if you are having problems with the HTTP-in/HTTP-reponse...

It's working for both 4.0.x and 3.1.x here, both in and outside docker. Both use the `got` library as the http agent at the same level (v12.6.x) There might be...

Can we get some extra details from people with failures please - Is this when testing from home or a business environment (just trying to gauge if there are likely...