node ver is 2.0.1
Reachability check failed: cannot be reached
WARNING!
WARNING!
WARNING!
You failed reachability with QUIC enabled. Consider switching to TCP
WARNING!
WARNING!
WARNING!
It doesn’t look like a normal screen.
I wonder if it’s something I should wait for.
I wonder if I should do something else.
- eading from server: Application error 0x0 (remote)",“stacktrace”:“source.quilibrium.com/quilibrium/monorepo/node/consensus/data.(*DataClockConsensusEngine).runPreMidnightProofWorker\n\t/opt/ceremonyclient/node/consensus/data/pre_midnight_proof_worker.go:185”}
It seems like an error that the server is not recognized.
The problem is with the RPC connectivity check URL. The Node is sending a request to rpc.quilibrium.com/connectivity-check in JSON format, and under the hood, that server sends the request to the client from 186.233.186.60 which seems to be a Brazilian subnet which is not routed in many parts of the world.
This has also been signaled on Discord by a friend of mine, but no actions have been taken so far.
So, if you check a tcpdump when the node requests DHT connectivity check you will see that a request comes from the above address, but if you do a traceroute to that IP, most probably it will end up unreachable after few hops.
I had to tunnel my 11 nodes via a wireguard vpn to an Oracle OCI VM, where that IP has connectivity, and do the DNAT there… Some complex traffic engineering…
This is how it’s looking from my end, i have 2 different local ISP and neither are routing that subnet:
1 Like