# Problems with peers at node operators in Russia

**URL:** <https://forum.autonomys.xyz/t/problems-with-peers-at-node-operators-in-russia/2439>\
**Category:** Support\
**Created:** [January 31, 2024, 9:56pm UTC](https://forum.autonomys.xyz/t/problems-with-peers-at-node-operators-in-russia/2439 "2024-01-31T21:56:10Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![user37](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/user37/32/919_2.png) [@user37](https://forum.autonomys.xyz/u/user37)\
**Post date:** [January 31, 2024, 9:56pm UTC](https://forum.autonomys.xyz/t/problems-with-peers-at-node-operators-in-russia/2439/1 "2024-01-31T21:56:10Z")

</div>

## Issue Report

### Environment

Operating System:_Ubuntu 20.04/22.04_  
Advanced CLI gemini-3h-2024-jan-31-2

### Problem

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.

 ![image](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/f/f8c707864b5f89ad2df23faf6ae9601a98fa611c.png)  
 ![image](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/b/b7a1a8cd874f295784c5c87d3d1ba5e1a833e03b.png)  
 ![image](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/6/68e5291e384cec0cd43cd9fc1ff3bbb236ee43b8.png)

---

<div class="post-metadata">

**Author:** ![user37](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/user37/32/919_2.png) [@user37](https://forum.autonomys.xyz/u/user37)\
**Post date:** [January 31, 2024, 10:04pm UTC](https://forum.autonomys.xyz/t/problems-with-peers-at-node-operators-in-russia/2439/2 "2024-01-31T22:04:18Z")

</div>

![image](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/4/4390c5ac4ff47e17eeae07dc27be423d9cc62e32.png)

---

<div class="post-metadata">

**Author:** ![user37](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/user37/32/919_2.png) [@user37](https://forum.autonomys.xyz/u/user37)\
**Post date:** [January 31, 2024, 10:15pm UTC](https://forum.autonomys.xyz/t/problems-with-peers-at-node-operators-in-russia/2439/3 "2024-01-31T22:15:31Z")

</div>

![image](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/1/198c8ec38617f7170770fa9ac99813e3fa3483fa.png)

---

<div class="post-metadata">

**Author:** ![Jim-Autonomys](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/jim-autonomys/32/2922_2.png) [@Jim-Autonomys](https://forum.autonomys.xyz/u/Jim-Autonomys)\
**Post date:** [January 31, 2024, 10:24pm UTC](https://forum.autonomys.xyz/t/problems-with-peers-at-node-operators-in-russia/2439/4 "2024-01-31T22:24:34Z")

</div>

@shamil any idea how we should go about trying to identify what is common between these nodes that would present the reported symptoms?

---

<div class="post-metadata">

**Author:** ![user37](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/user37/32/919_2.png) [@user37](https://forum.autonomys.xyz/u/user37)\
**Post date:** [January 31, 2024, 10:37pm UTC](https://forum.autonomys.xyz/t/problems-with-peers-at-node-operators-in-russia/2439/5 "2024-01-31T22:37:53Z")

</div>

![image](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/8/8bc3cf84ac3cc5fe11b94b5765b97d69358191a8.png)

---

<div class="post-metadata">

**Author:** ![Pavel\_Kochurov](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/pavel_kochurov/32/1347_2.png) [@Pavel\_Kochurov](https://forum.autonomys.xyz/u/Pavel_Kochurov)\
**Post date:** [January 31, 2024, 10:38pm UTC](https://forum.autonomys.xyz/t/problems-with-peers-at-node-operators-in-russia/2439/6 "2024-01-31T22:38:16Z")

</div>

that’s me. can’t get peers since december. ISP Rostelekom (screenshot from 3g, same problem in 3h)

 ![photo_5314555595807905736_y](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/9/991776e88b5d6e56d1b4c7bc0c9994224c706537.jpeg)

---

<div class="post-metadata">

**Author:** ![shamil](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/shamil/32/875_2.png) [@shamil](https://forum.autonomys.xyz/u/shamil)\
**Post date:** [February 1, 2024, 5:37am UTC](https://forum.autonomys.xyz/t/problems-with-peers-at-node-operators-in-russia/2439/7 "2024-02-01T05:37:19Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![user37](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/user37/32/919_2.png) [@user37](https://forum.autonomys.xyz/u/user37)\
**Post date:** [February 1, 2024, 7:15am UTC](https://forum.autonomys.xyz/t/problems-with-peers-at-node-operators-in-russia/2439/8 "2024-02-01T07:15:43Z")

</div>

![image](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/9/9ead1a4f71c257f61b76803b5314fd3af08a344c.png)  
Now I have peers on both servers but have the following errors. This server is Xeon 2695v4 (2 processors)

---

<div class="post-metadata">

**Author:** ![Jim-Autonomys](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/jim-autonomys/32/2922_2.png) [@Jim-Autonomys](https://forum.autonomys.xyz/u/Jim-Autonomys)\
**Post date:** [February 1, 2024, 10:32am UTC](https://forum.autonomys.xyz/t/problems-with-peers-at-node-operators-in-russia/2439/9 "2024-02-01T10:32:00Z")

</div>

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.

Thanks for the assistance @shamil.

---

<div class="post-metadata">

**Author:** ![Yurally](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/yurally/32/528_2.png) [@Yurally](https://forum.autonomys.xyz/u/Yurally)\
**Post date:** [February 1, 2024, 2:34pm UTC](https://forum.autonomys.xyz/t/problems-with-peers-at-node-operators-in-russia/2439/10 "2024-02-01T14:34:15Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\
**Post date:** [February 1, 2024, 4:17pm UTC](https://forum.autonomys.xyz/t/problems-with-peers-at-node-operators-in-russia/2439/11 "2024-02-01T16:17:58Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![user37](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/user37/32/919_2.png) [@user37](https://forum.autonomys.xyz/u/user37)\
**Post date:** [February 1, 2024, 4:20pm UTC](https://forum.autonomys.xyz/t/problems-with-peers-at-node-operators-in-russia/2439/12 "2024-02-01T16:20:10Z")

</div>

I hope it’s resolved soon.

---

<div class="post-metadata">

**Author:** ![Pavel\_Kochurov](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/pavel_kochurov/32/1347_2.png) [@Pavel\_Kochurov](https://forum.autonomys.xyz/u/Pavel_Kochurov)\
**Post date:** [February 1, 2024, 5:15pm UTC](https://forum.autonomys.xyz/t/problems-with-peers-at-node-operators-in-russia/2439/13 "2024-02-01T17:15:52Z")

</div>

unfortunately still have no peers, will try port 30334 now

 ![image](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/b/b42bcac3245f0aa70965e73b374efd5510d46248.png)

---

<div class="post-metadata">

**Author:** ![Pavel\_Kochurov](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/pavel_kochurov/32/1347_2.png) [@Pavel\_Kochurov](https://forum.autonomys.xyz/u/Pavel_Kochurov)\
**Post date:** [February 1, 2024, 5:26pm UTC](https://forum.autonomys.xyz/t/problems-with-peers-at-node-operators-in-russia/2439/14 "2024-02-01T17:26:59Z")

</div>

Yes, looks like it - it doesn’t appear to me. added --listen-on /ip4/0.0.0.0/tcp/30334 ` but it doesn’t work for me
