I’m surprised to get the “FailedExternalReachability” in my logs even while ports on both sides of my private test-network are open.
I’ve opened port 5483 on my instance on AWS. The port get’s open whenever I start a new network using safe_vault -f.
So the seednode is running on AWS and the port is open. Next step I start a node from home with the same settings and I can actually see the port go open (DMZ host in action, it’s normally closed). The nodes trie to connect to AWS, it actually does but in 4 seconds the nodes stops and I get this in my PC vault log:
Listener started on port 5483. ERROR 18:41:32.384463600 [crust::main::bootstrap mod.rs:184] Failed to Bootstrap: (FailedExternalReachability) Bootstrapee node could not establish connection to us. INFO 18:41:32.384463600 [routing::states::bootstrapping bootstrapping.rs:201] Bootstrapping(b0f337..) Failed to bootstrap. Terminating. DEBUG 18:41:32.384463600 [routing::state_machine state_machine.rs:267] State::Bootstrapping(b0f337..) Terminating state machine
This is weird, as I also checked that my local port did open.
I write this in the “support” category but I actually think it is a bug. I’ve seen this one with several others as well in community networks over the last few days. Anyone a clue? Is there a timer wrongly set in the code somewhere?