Firefox Won't sync through work firewall any more
I used to be able to sync through my work firewall. I do not know what changed, but I can no longer do so. Google Chrome (which uses built-in windows certificates) works I imported the certificates manually for firefox and while I can reach all websites I go to, I cannot perform a sync operation.
I am using Firefox Portable v47, but it hasn't worked in several updates.
Please see attached text bug report from about:sync-log. Well, that didn't work. Please see below data from the sync log
1466560867988 Sync.Service INFO Loading Weave 1.49.0 1466560867990 Sync.Engine.Clients DEBUG Engine initialized 1466560867991 Sync.Engine.Clients DEBUG Resetting clients last sync time 1466560867996 Sync.Engine.Bookmarks DEBUG Engine initialized 1466560867998 Sync.Engine.Forms DEBUG Engine initialized 1466560868001 Sync.Engine.History DEBUG Engine initialized 1466560868005 Sync.Engine.Passwords DEBUG Engine initialized 1466560868008 Sync.Engine.Prefs DEBUG Engine initialized 1466560868010 Sync.Engine.Tabs DEBUG Engine initialized 1466560868010 Sync.Engine.Tabs DEBUG Resetting tabs last sync time 1466560868014 Sync.Engine.Addons DEBUG Engine initialized 1466560868016 Sync.Service INFO Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0 1466560868018 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1466560868019 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1466560868019 Sync.Service DEBUG Caching URLs under storage user base: https://sync-176-us-west-2.sync.services.mozilla.com/1.5/15404241/ 1466560868019 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1466560868019 Sync.AddonsReconciler INFO Registering as Add-on Manager listener. 1466560868020 Sync.AddonsReconciler DEBUG Adding change listener. 1466560868046 browserwindow.syncui DEBUG observed: weave:service:ready 1466560868047 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1466560868049 browserwindow.syncui DEBUG _loginFailed has sync state=success.login 1466560868051 browserwindow.syncui DEBUG _loginFailed has sync state=success.login 1466560868054 FirefoxAccounts TRACE not checking freshness of profile as it remains recent 1466560870357 Sync.ErrorHandler DEBUG Beginning user-triggered sync. 1466560870381 Sync.Service DEBUG User-Agent: Firefox/47.0 FxSync/1.49.0.20160604131506. 1466560870381 Sync.Service INFO Starting sync at 2016-06-21 19:01:10 1466560870381 Sync.Service DEBUG In sync: should login. 1466560870381 browserwindow.syncui DEBUG observed: weave:service:login:start 1466560870382 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1466560870382 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1466560870382 Sync.Service INFO Logging in the user. 1466560870383 Sync.BrowserIDManager INFO Waiting for user to be verified. 1466560870383 FirefoxAccounts DEBUG already verified 1466560870383 browserwindow.syncui DEBUG _loginFailed has sync state=success.login 1466560870384 Sync.BrowserIDManager INFO Starting fetch for key bundle. 1466560870384 FirefoxAccounts DEBUG already verified 1466560870384 Sync.BrowserIDManager INFO Getting an assertion from: https://token.services.mozilla.com/1.0/sync/1.5 1466560870384 FirefoxAccounts DEBUG enter getAssertion() 1466560870393 browserwindow.syncui DEBUG _loginFailed has sync state=success.login 1466560870403 FirefoxAccounts DEBUG got keyPair 1466560870403 FirefoxAccounts DEBUG getCertificateSigned: true true 1466560871163 Hawk DEBUG (Response) /certificate/sign: code: 200 - Status text: OK 1466560871163 Sync.RESTResponse TRACE Processing response headers. 1466560871164 Hawk DEBUG Clock offset vs https://api.accounts.firefox.com/v1: -1164 1466560871164 FirefoxAccounts DEBUG getCertificate got a new one: true 1466560871164 FirefoxAccounts DEBUG _updateAccountData with items: ["keyPair","cert"] 1466560871165 FirefoxAccounts DEBUG getAssertionFromCert 1466560871165 FirefoxAccounts DEBUG writing plain storage: ["email","sessionToken","uid","verified","oauthTokens"] 1466560871165 FirefoxAccounts TRACE starting write of json user data: ["email","sessionToken","uid","verified","oauthTokens"] 1466560871169 FirefoxAccounts DEBUG getAssertionFromCert returning signed: true 1466560871169 Sync.BrowserIDManager DEBUG Getting a token 1466560871170 Common.TokenServerClient DEBUG Beginning BID assertion exchange: https://token.services.mozilla.com/1.0/sync/1.5 1466560871178 FirefoxAccounts TRACE finished write of json user data - took: 12 1466560871178 FirefoxAccounts DEBUG writing secure storage: ["kA","kB"] 1466560871178 FirefoxAccounts TRACE starting write of user data to the login manager 1466560871192 FirefoxAccounts TRACE finished write of user data to the login manager 1466560871491 Common.TokenServerClient DEBUG Got token response: 200 1466560871492 Sync.RESTResponse TRACE Processing response headers. 1466560871492 Common.TokenServerClient DEBUG Successful token response 1466560871492 Sync.BrowserIDManager DEBUG Successfully got a sync token 1466560871493 Sync.BulkKeyBundle INFO BulkKeyBundle being created for undefined 1466560871493 Sync.BrowserIDManager INFO Background fetch for key bundle done 1466560871493 Sync.Status DEBUG Status.login: success.login => success.login 1466560871493 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1466560871494 Sync.Service DEBUG Caching URLs under storage user base: https://sync-176-us-west-2.sync.services.mozilla.com/1.5/15404241/ 1466560871494 Sync.Service INFO User logged in successfully - verifying login. 1466560871494 Sync.BrowserIDManager DEBUG unlockAndVerifyAuthState already has (or can fetch) sync keys 1466560871494 Sync.Service DEBUG Fetching unlocked auth state returned success.status_ok 1466560871495 Sync.BrowserIDManager DEBUG _ensureValidToken already has one 1466560873054 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1466560873054 Sync.Service DEBUG User-Agent: Firefox/47.0 FxSync/1.49.0.20160604131506. 1466560873055 Sync.Service INFO Starting sync at 2016-06-21 19:01:13 1466560873055 Sync.Service DEBUG In sync: should login. 1466560873055 Sync.Service DEBUG Exception: Could not acquire lock. Label: "service.js: login". 1466560873055 Sync.Service INFO Cannot start sync: already syncing? 1466560873055 Sync.Service DEBUG Not syncing: login returned false. 1466561171526 Sync.Service DEBUG verifyLogin failed: Error: Aborting due to channel inactivity. (resource://services-sync/resource.js:405:19) JS Stack trace: notify@utils.js:178:9 < waitForSyncCallback@async.js:98:7 < Res__request@resource.js:398:14 < Res_get@resource.js:425:12 < verifyLogin@service.js:694:18 < onNotify@service.js:977:12 < WrappedNotify@util.js:146:21 < WrappedLock@util.js:101:16 < WrappedCatch@util.js:75:16 < login@service.js:988:12 < sync/<@service.js:1236:14 < WrappedCatch@util.js:75:16 < sync@service.js:1232:5 < Res_get@resource.js:425:12 < verifyLogin@service.js:694:18 < onNotify@service.js:977:12 < WrappedNotify@util.js:146:21 < WrappedLock@util.js:101:16 < WrappedCatch@util.js:75:16 < login@service.js:988:12 < sync/<@service.js:1236:14 < WrappedCatch@util.js:75:16 < sync@service.js:1232:5 1466561171527 Sync.Status DEBUG Status.login: success.login => error.login.reason.network 1466561171527 Sync.Status DEBUG Status.service: success.status_ok => error.login.failed 1466561171527 Sync.Status DEBUG Status.login: error.login.reason.network => error.login.reason.network 1466561171527 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1466561171528 browserwindow.syncui DEBUG observed: weave:service:login:error 1466561171528 browserwindow.syncui DEBUG onLoginError: login=error.login.reason.network, sync=success.sync 1466561171529 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1466561171530 Sync.SyncScheduler DEBUG Next sync in 3600000 ms. 1466561171530 Sync.ErrorHandler ERROR Sync encountered a login error
Solução escolhida
I should have been more clear: Working for a very large company means we sometimes have to do clandestine workarounds just to get our jobs done. Firefox is one of those workarounds. IE is the only browser we're officially allowed to have -- all the way up. The boss hates it too, and so does his boss.
Having said that, I did fix the problem and because I hate people who fix things and don't say how, here you go:
I noted I could get to civilian web pages, but tabs Firefox Sync said "not connected to the internet."
- I returned to where our company stores internet certificates that are automatically downloaded for IE. (And thus Chrome, which uses the same system ones)
- I manually re-uploaded the certificates. There were two new ones
- I cancelled sync
- I took a deep breath and deleted the passwords.
- I closed Firefox
- I opened Firefox and started Sync
- I had to sign in/enter my credentials
- Back to normal.
Good luck to everyone else.
Ler esta resposta no contexto 👍 0Todas as respostas (5)
Hi
You may want to have a chat to your companies IT security team about the changes they have made to their firewall.
My work only allows IE 10, no other browsers installed. I'm running Firefox PortableApp as a workaround.
Many modern supplier and other websites we interact with (looking up parts and information) no longer work with IE, which puts us in a bind.
But officially we can't acknowledge we're using other browsers. Thank you for the suggestion.
Tell the boss that the blocking is interfering with your work.
Solução escolhida
I should have been more clear: Working for a very large company means we sometimes have to do clandestine workarounds just to get our jobs done. Firefox is one of those workarounds. IE is the only browser we're officially allowed to have -- all the way up. The boss hates it too, and so does his boss.
Having said that, I did fix the problem and because I hate people who fix things and don't say how, here you go:
I noted I could get to civilian web pages, but tabs Firefox Sync said "not connected to the internet."
- I returned to where our company stores internet certificates that are automatically downloaded for IE. (And thus Chrome, which uses the same system ones)
- I manually re-uploaded the certificates. There were two new ones
- I cancelled sync
- I took a deep breath and deleted the passwords.
- I closed Firefox
- I opened Firefox and started Sync
- I had to sign in/enter my credentials
- Back to normal.
Good luck to everyone else.
That was very good work. Well done.