搜索 | 用户支持

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

Learn More

Sync server not reacheable

more options

I'm having problems to sync my account with one computer, and apparently the reason is that it cannot reach the sync server

https://sync-1-us-west1-g.sync.services.mozilla.com

I can open the above url from my phone and from one laptop, but I cannot open that address from the laptop that I'm trying to synchronize. I got the address from the sync-log

Sync.Resource WARN GET request to https://sync-1-us-west1-g.sync.services.mozilla.com/1.5/161701144/info/collections failed: [Exception... "The connection has timed out" nsresult: "0x804b000e (NS_ERROR_NET_TIMEOUT)" location: "<unknown>" data: no] No traceback available

Sync.Service DEBUG verifyLogin failed: [Exception... "The connection has timed out" nsresult: "0x804b000e (NS_ERROR_NET_TIMEOUT)" location: "<unknown>" data: no] No traceback available

Both computers and phone are connected to the same local network.

I'm having problems to sync my account with one computer, and apparently the reason is that it cannot reach the sync server https://sync-1-us-west1-g.sync.services.mozilla.com I can open the above url from my phone and from one laptop, but I cannot open that address from the laptop that I'm trying to synchronize. I got the address from the sync-log Sync.Resource WARN GET request to https://sync-1-us-west1-g.sync.services.mozilla.com/1.5/161701144/info/collections failed: [Exception... "The connection has timed out" nsresult: "0x804b000e (NS_ERROR_NET_TIMEOUT)" location: "<unknown>" data: no] No traceback available Sync.Service DEBUG verifyLogin failed: [Exception... "The connection has timed out" nsresult: "0x804b000e (NS_ERROR_NET_TIMEOUT)" location: "<unknown>" data: no] No traceback available Both computers and phone are connected to the same local network.

被采纳的解决方案

The issue was a pf blocking list that include the ip of the sync server. IP removed, end of the issue.

定位到答案原位置 👍 0

所有回复 (1)

more options

选择的解决方案

The issue was a pf blocking list that include the ip of the sync server. IP removed, end of the issue.