Do the nodes continue to function if the panel goes down?

[Onotot]

Hello. In one of the earlier versions of the panel, when the server with the panel went offline, the nodes stopped working.
Is this still a problem, or was it fixed? Or maybe I'm missing some settings?

[hann-wang]

Still a problem

[M03ED]

Yes there is a keep alive variable for each node and you can set value as you need, default is 60 second

[Applone]

I'm facing the same problem. my time to live is set to 21600 seconds (6 hours), if I disconnect the server with the panel, the node on the other server immediately stops working. The logs show that xray core stops when it does not receive information from the panel.

log.txt

P.S.: The panel sends a stop signal to the nodes during a graceful shutdown. As a test, I shut down the server hosting the panel, which triggered a graceful shutdown, causing the node to simply stop via the panel's command. The question is: why does the panel send a stop signal to the nodes when it shuts down in the first place? What is the point? The nodes should be autonomous. Furthermore, we need to consider that a panel crash doesn't always just look like an absence of polling, yet that is the only scenario the current TTL system protects against.

[Onotot]

Yes there is a keep alive variable for each node and you can set value as you need, default is 60 second

Unfortunately, the nodes are disconnecting despite the specified time.

[RbPyer]

Yes, the same problem. If the panel crashes, all nodes go down.

[subzero911]

I can confirm the bug.
I set 24h timeout for node.
turned off a pasarguard panel
node stopped immediately.
panel v5.0.3

[subzero911]

Solution: add the following variable to the panel .env:

STOP_NODES_ON_SHUTDOWN = false

[Applone]

@M03ED Why is there any timeout anyway? What's the point? Why not just make an option to disable it fully or make it disabled by default?