Sentinel Nodes stop working about dvpn-node HOT 10 CLOSED

One thing will be to have alternate RPC servers. However, at the moment we can provide single RPC endpoint in node configuration. As this seems to be quite critical point in whole setup, maybe reasonable is to consider ability to add up to 3 RPC endpoints and add some round-robin "when first one responds with error, try another one".
That would make whole process more resilient.
Another solution could be ignoring error for some time and retry RPC communication after let's say 3 or 5 minutes (this interval might also be defined in config "In case of failure retry in X minutes" parameter.
Basically just implement something which prevents immediate node crash once RPC can't be contacted.

from dvpn-node.

Yes, this will be added in next version.

from dvpn-node.

Hi @Femkecl, It seems like the issue is with RPC endpoint. Can you please try checking with another public RPC endpoint.

from dvpn-node.

Have done that and the issue remains.

from dvpn-node.

Please, question regarding your comment "try checking with another public RPC endpoint"

According to the documentation we are advised to use "https://rpc.sentinel.co:443".

Please, are you able to provide an authorized list of alternate RPC endpoints?

B.Rgds,
HA

from dvpn-node.

FYI. I switched my nodes to a different RPC and so far it's working great.

rpc_address = "https://rpc.sentinel.smartnodes.one:443"

from dvpn-node.

Hi there, what URL is this? The listing of the nodes.

Screenshots

from dvpn-node.

FYI. I switched my nodes to a different RPC and so far it's working great.

rpc_address = "https://rpc.sentinel.smartnodes.one:443"

This rpc address seems to be down. I get a timeout at startup.

from dvpn-node.

Yes, that one died last month. Switch back to the original or try the ITA Staker.

from dvpn-node.

Yes, that one died last month. Switch back to the original or try the ITA Staker.

I just found another one but dit not try it rpc.mathnodes.com:4444
I'm using the first one.

from dvpn-node.