Access from Russia
Asked by Bogdan Khomutovskii:

git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks fetch --no-tags origin  
fatal: unable to access '\*\*\*\*\*': Recv failure: Connection was reset

tracert bitbucket.org \[18.234.32.155\]

1 \<1 ?? \<1 ?? \<1 ?? router \[192.168.88.1\]  
2 2 ms \<1 ?? \<1 ?? ppp-gw.tis-dialog.ru \[83.219.128.0\]  
3 1 ms \<1 ?? \<1 ?? 10.192.168.12  
4 1 ms 1 ms \<1 ?? 10.192.168.135  
5 13 ms 13 ms 12 ms ae4-214.rt.lim.waw.pl.retn.net \[87.245.249.66\]  
6 118 ms 117 ms 117 ms ae1-7.rt.tlx.nyc.us.retn.net \[87.245.234.6\]  
7 \* \* \* The waiting interval for the request has been exceeded.  
8 \* \* \* The waiting interval for the request has been exceeded.  
9 \* \* \* The waiting interval for the request has been exceeded.  
10 \* \* \* The waiting interval for the request has been exceeded.  
11 \* \* \* The waiting interval for the request has been exceeded.  
12 \* \* \* The waiting interval for the request has been exceeded.  
13 \* \* \* The waiting interval for the request has been exceeded.  
14 \* \* \* The waiting interval for the request has been exceeded.  
15 \* \* \* The waiting interval for the request has been exceeded.  
16 \* \* \* The waiting interval for the request has been exceeded.  
17 \* \* \* The waiting interval for the request has been exceeded.  
18 \* \* \* The waiting interval for the request has been exceeded.  
19 \* \* \* The waiting interval for the request has been exceeded.  
20 \* \* \* The waiting interval for the request has been exceeded.  
21 \* \* \* The waiting interval for the request has been exceeded.  
22 \* \* \* The waiting interval for the request has been exceeded.  
23 \* \* \* The waiting interval for the request has been exceeded.  
24 \* \* \* The waiting interval for the request has been exceeded.  
25 \* \* \* The waiting interval for the request has been exceeded.  
26 \* \* \* The waiting interval for the request has been exceeded.  
27 \* \* \* The waiting interval for the request has been exceeded.  
28 \* \* \* The waiting interval for the request has been exceeded.  
29 \* \* \* The waiting interval for the request has been exceeded.  
30 \* \* \* The waiting interval for the request has been exceeded.


Answers:
author: Nic Brough -Adaptavist-
body: Welcome to the Atlassian Community!

My guess would be that you are being blocked by the sanction rules that most of the world has imposed on Russia because of its illegal invasion of Ukraine. See <https://www.atlassian.com/blog/announcements/atlassian-stands-with-ukraine> for Atlassian's explanation of why they're doing it.


author: David at David Simpson Apps
body: Hosting on AWS, like Atlassian do, it's straightforward to block access by country.   

Here's how we blocked access for our Marketplace apps:

![IMG_4841.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/261232iBE1C7650A0E74527/image-size/large?v=v2&px=999 "IMG_4841.jpeg")  

I recommend you restore your repositories from backups and host them in a local service from your country.

comments: author: dmyudin
body: Hi. Thanks for your answer, but now it seems like everything works well. I hope it was temporary problem. But even if it wasn't, i'd rather use vnp than quit from bitbucket.


author: dmyudin
body: I am experiencing the same problem last few days too. I get this error:  
2023-06-01 19:15:19.673 \[info\] fatal: unable to access '<https://bitbucket.org/my-workspace-name/my-repo-name.git/>': Recv failure: Connection was reset  
If atlassian blocks access from russian ip's it would be nice if they say to us users directly: "please move you repos to other provider". But they do not.

comments: author: Nic Brough -Adaptavist-
body: Please see <https://www.atlassian.com/blog/announcements/atlassian-stands-with-ukraine> and check your network connection for blocks.


author: dmyudin
body: The post you point at is quite old. Connection problems began a few days ago. It seems like you are not the technical guy from atlassian team who knows a definite answer. So please stop spreading your quesses. Thanks.


author: Nic Brough -Adaptavist-
body: The intent in the blog post still represents Atlassian's stance, it doesn't matter that it is old.

Have you checked your basic connectivity to the site? We can't tell you anything about the problem if you won't tell us where it is.

Have you tried a simple "trace route"?


author: dmyudin
body: Of course i did. Trace route is much the same as the topic starter's.


author: Nic Brough -Adaptavist-
body: The original post contains a trace route that is consistent with the sanctions explained in the blog post. So yes, you're being deliberately blocked because of the sanctions against Russia.


author: Bogdan Khomutovskii
body: Your assumption is wrong. Other products of the company such as trello and others work fine. Is your assumption based on dislike of Russians ? If you don't have official information, I advise you not to spread false rumors.

comments: author: Nic Brough -Adaptavist-
body: It was just a guess. Access to other systems is irrelevant, Atlassian block access to different systems differently.

I'm not spreading "false rumours". It is a fact that Russia has invaded Ukraine illegally, and it is a fact that many organisations are blocking access to their systems from Russia.


Tags: russia