Operators of nodes from Russia reported that there are no peers, I am among them. There are 2 different servers that are not connected to each other and have different providers. After uninstalling 3g which was working fine I installed 3h but no peers, I checked the ports and they were all available. Then I installed the software on the other hardware and the peers were there at first, however I noticed over time that they also disappeared. The 3h telemetry shows that users from the Russian cities of Tyumen and Volokonovka also have no peers.
Yesterday, Russian users experienced major DNS issues but we don’t use those domains and it’s unlikely connected. I would start debugging by inspecting logs(with RUST_LOG=debug environment variable) followed by the change of the local network (e.g.: running from the different cloud vm). Also, it doesn’t seem like a DSN problem - the symptoms indicate that Substrate network can’t be connected.
This is expected as farming is not enabled yet. Sounds like your original network issue was related to a temporary DNS issue that prevented you hitting the bootstrap nodes.
I encountered the same problem, for some reason the node cannot detect the external IP address
When the message “Consensus: sub-libp2p: Discovered new external address for our node:” does not appear, then the node does not see peers; changing port 30333 to 30334 helped some, although they are accessible and not busy with anything else
Our bootstrap nodes are a bit overwhelmed right now, they were crashing a bit, but we’ve got it mostly under control now, so situation going forward should be better.
Discovered new external address for our node:” does not appear, then the node does not see peers; changing port 30333 to 30334 helped some, although they are accessible and not busy with anything else