搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Provide mirror of Firefox sync for Russian users in non-blocked IP subnet

more options

Mozilla Firefox Sync is blocked in whole Russia, when Russian authorities (Roskomnadzor) try to block Telegram, so it blocks those subnets: http://isitblockedinrussia.com/?host=accounts.firefox.com 35.160.0.0/13 54.144.0.0/12

Additional info here: https://github.com/sxiii/russian-blackout

So all Russian users at now can't use Firefox Sync (accounts.firefox.com) and other Mozilla cloud services.

Can Mozilla provide mirror or proxy for accounts.firefox.com website and other services in new IP subnet, that not blocked in Russia?

For Russian users: Роскомнадзор (РКН) заблокировал в России доступ к синхронизации Mozilla Firefox поэтому сайты accounts.firefox.com, firefoxusercontent.com, sync.services.mozilla.com не открываются у многих русских провайдеров (Ростелеком, Мегамакс, Virgin Connect и т.п.)

Mozilla Firefox Sync is blocked in whole Russia, when Russian authorities (Roskomnadzor) try to block Telegram, so it blocks those subnets: http://isitblockedinrussia.com/?host=accounts.firefox.com 35.160.0.0/13 54.144.0.0/12 Additional info here: https://github.com/sxiii/russian-blackout So all Russian users at now can't use Firefox Sync (accounts.firefox.com) and other Mozilla cloud services. Can Mozilla provide mirror or proxy for accounts.firefox.com website and other services in new IP subnet, that not blocked in Russia? For Russian users: Роскомнадзор (РКН) заблокировал в России доступ к синхронизации Mozilla Firefox поэтому сайты accounts.firefox.com, firefoxusercontent.com, sync.services.mozilla.com не открываются у многих русских провайдеров (Ростелеком, Мегамакс, Virgin Connect и т.п.)

被采纳的解决方案

35.160.0.0/13 and 54.144.0.0/12 are removed from list of blocked IP ranges in Russia at 08.06.2018, so seems the problem is solved now.

定位到答案原位置 👍 0

所有回复 (5)

more options

Please, fix this problem. I can't stop using Firefox Sync services. Firefox Sync is very handy.

more options

Also, topics and messages from forum.mozilla-russia.org devoted to block and censorship of russian internet by the governmental institution (РКН) are being deleted with no reasons (as Murz had written, some blocked IP affected Firefox Sync services)! Why moderators of russian forum.mozilla-russia.org are making the censorship deleting messages describing problems with Firefox Sync? Currently no way of using Firefox Sync in Russia. Trying to find another browser now. Very disappointed.

more options

Found out that my messages from forum.mozilla-russia.org (asking why do you delete messages of users having problems with Firefox Sync in Russia due to РКН blocking and censorship) were deleted AGAIN and my account in forum.mozilla-russia.org was banned. Very disappointed that so-so non-commercial and apolitical project as Firefox in Russian reality became totally political and censored. Moderators and administrators of Russian forum.mozilla-russia.org give bans to users asking help for evading IP-blocking. Deleting my Firefox Sync now, deleting Firefox. Go far, censors! Hope, international Firefox team will give some attention to local censorship of russian moderators and administrators from forum.mozilla-russia.org. Shame on them!

more options

I have no idea why Sync is being blocked in Russia, but I have contacted one of the Mozilla Sync developers about this thread. Maybe he will have an answer for you as to what is going on and if Mozilla can do anything about the situation.

That said, it is possible to set up your own Sync server: https://github.com/mozilla-services/syncserver https://mozilla-services.readthedocs.io/en/latest/howtos/run-sync-1.5.html

And it may be possible to setup a wide-scale Sync server that is hosted in Russia and serves Russia-based user's exclusively. Maybe that would get around the blocks to accessing the Mozilla Sync servers.

more options

选择的解决方案

35.160.0.0/13 and 54.144.0.0/12 are removed from list of blocked IP ranges in Russia at 08.06.2018, so seems the problem is solved now.