Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

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.

Izabrano rješenje

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

Pročitaj ovaj odgovor u kontekstu 👍 0

Svi odgovori (1)

more options

Odabrano rješenje

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