Sure we can bear some downtime. But I am afraid it will be same story again if new IP too gets blocked. If the block is intentional on authorities part, for undisclosed reasons, then we can’t do much.
I wrote to them, not once, I receive a notification that the letter was not delivered
who blocked and for what article
I have one of the three of my providers does not block traffic, I connect via VPN to the network with this provider and I’m here 
I’m from Russia. The site is working fine without VPN. The problem is in your ISP.
not all providers are law-abiding,
as I said above, I have three providers and only one is blocking.
Unfortunely, my ISP is very law-abiding.
Hello @Kai
The government has not responded to my letter for several months. Maybe I found a way to bypass the lock. I tried with other sites that post torrents on them turned out to enter. I did ipv6 support at home with a Hurricane Electric broker. ipv4toipv6 and sites with ipv6 support, I can open any. Is it possible to make ipv6 support on your website and community?
Not work (not support ipv6):
Work (support ipv6):
1 Like
That’s a very good idea as a workaround! Indeed, we so far didn’t have IPv6 enabled (while it in any case makes sense). Just did it now:
kai$ nslookup -query=AAAA community.openhab.org
Server: 172.20.10.1
Address: 172.20.10.1#53
Non-authoritative answer:
community.openhab.org has AAAA address 2a03:b0c0:3:d0::a:1
Let me know if that works for you!
1 Like
Wow, great!
Works!
Thank you very much!
2 Likes
Excellent, very happy to hear that!
This trick doesn’t slove the problem.
Really the problem is provider’s routing mistake or CDN’s error. I checked different russian providers and some of them allow to open community but some of them not. Roscomnadzor doesn’t block this site or IP.
lower some tracert results:
Enforta aka ROM-RU work fine:
1 66 ms 65 ms 71 ms 172.16.103.1 2 92 ms 87 ms 80 ms 5x16x9x153.static-business.iz.ertelecom.ru [5.16.9.153] 3 321 ms 75 ms 90 ms 188-234-157-101.ertelecom.ru [188.234.157.101] 4 85 ms 79 ms 78 ms as9049.ix.dataix.ru [178.18.224.152] 5 193 ms 204 ms 203 ms as14061.ix.dataix.ru [178.18.224.159] 6 208 ms 204 ms 408 ms 138.197.250.145 7 196 ms 205 ms 204 ms 46.101.248.207
and Megafon mobile strange routing:
1 2 ms 4 ms 2 ms 192.168.43.1 2 * * * Request timed out 3 38 ms 39 ms 39 ms 10.153.60.1 4 112 ms 304 ms 117 ms 10.78.248.73 5 75 ms 303 ms 97 ms 10.78.248.74 6 56 ms 61 ms 56 ms 10.78.246.33 7 52 ms 77 ms 73 ms 10.110.206.2 8 44 ms 35 ms 39 ms 10.78.248.85 9 42 ms 38 ms 39 ms 10.78.250.174 10 43 ms 37 ms 38 ms ip-83-149-1-137.nwgsm.ru [83.149.1.137] 11 41 ms 76 ms 39 ms ip-83-149-6-242.nwgsm.ru [83.149.6.242] 12 * * * Request timed out 13 * * * Request timed out 14 * * * Request timed out 15 * * * Request timed out 16 * * * Request timed out 17 * * * Request timed out
Access restriction by ip address. The court blocked this ip. If it works on some operators, this means that the operator itself simply did not block this ip. For some, even rutracker.org works. Configure DNS over HTTPS in the browser (now this function is supported by most browsers) it is necessary to hide requests to the DNS server from the provider.
Thanks.
Blocking by IP 