Hello, im running into issues where the nodered http in node freezes.
I have variables saved in nodered, which are then requested through a http in set to get.
This will then return the requested data.
Easy, smooth, clean, simple.
Until it just stops.
There's no errors, the portainer log only shows that im redploying trying to fix the issue, and there is nothing coming out from the node when attatching it to a debug node.
The script that performed the request shows a 404 in the console.
Now sometimes you can get away with moving the node and redeploying, or sometimes you have to move and change the name.
But more recently, you have to recreate it.
Create a new http in, set it to get, copy-paste the web adress, move the link from the old to the new node.
And then it just works, even though its exactly the same thing.
So im asking if anyone has a clue what this could be, and any guidence on how to debug this.
Seeing how the issue is with the first node in the chain, im having trouble even knowing where to start debugging.
Any help is apreciated.
I currently have no idea how many calls, but its seemingly random.
The script that last failed the get request is running once a minute, which is what they're usually set to.
Its any of the http in nodes.
Many different ways, but a Lua script and a browser is what specifically was used last.
The lua script would return sucess, but with nil data returned.
The browser would put a 404 in the logs.
Web adresses, some nodes/adresses returns a web page, and then you can input data or settings, and then other nodes/adresses are used for scripts to use a get to fetch that data.
AWS EC2 server, running Ubuntu 20.04.4 LTS
We are also using the AWS loadbalancer
Node JS 16.16.0
Yes, in Portainer 2.9.2
No, there is a "normal" ammount of debug messages, but once the error happens, there's nothing coming out of the http node.
No message to debug, no message to return to sender, no nothing.
And then you do the delete and recreate dance and it works again.
I'll try it, but will the catch node catch the error if the node is not outputting anything and is seemingly unresponsive?
Unfortunately in the process of debugging, the node is now responding again, so ill have to wait for another to freeze.
Is there a limit where you'd go "that's too many" ?