Launcher looks good, but when I try to set up a PIN, I’ve been getting errors like this:
WARN 15:01:06.019853959 [crust::bootstrap bootstrap.rs:121] Error connecting to bootstrap peer: Connection refused (os error 111)
WARN 15:03:13.201667650 [crust::connection connection.rs:163] TCP direct connect failed: Connection timed out (os error 110)
Tried two systems at different times of day from different networks. Best guess is that the 100 node test network has been overwhelmed with excited supporters, but if that’s not what you’re seeing I could use a hand getting the Launcher of the ground…
Don’t you think that the Support side of the forum (the pinned topic maybe) should include this information as well as other critical details of the implementation?
Better to just have at the top of the dev update that the test mentioned in the update has ended. Usually its people who have just read the update and want to try it. Maybe that is something @Ross could be on top of. Just edit his post saying the test is now finished.
This is something that should be covered by the network dashboard - one place to check rather than looking through the forum. David updated on this last night: