Bug #3301
Firefox Sync in Iceweasel not working
Status:
fixed
Priority:
bug
Assignee:
% Done:
0%
Description
- steps to reproduce:
Trying to sync into Firefox Sync.
- expected result:
Logging in, having to enter some confirmation number, and start syncing.
- actual result:
Hangs indefinitely at the "working" stage, which occurs both after entering your email and/or entering your password.
Related issues
History
Updated by bill-auger almost 2 years ago
- Status changed from unconfirmed to confirmed
not sure how long its been broken - i never noticed because i am always signed in - so the bug is probably only on the initial login page
Response not received for: fxaccounts:can_link_account instrument.js:109:42
v instrument.js:109
error logger.js:72
timeout duplex.js:35
s helpers.js:74
Updated by avalos over 1 year ago
This is the solution: https://libredd.it/r/firefox/comments/5d7cid/comment/da5grvf/?utm_source=share&utm_medium=web2x&context=3
Add https://accounts.firefox.com to the beginning of webchannel.allowObject.urlWhitelist in about:config and Sync will work.
Updated by bill-auger over 1 year ago
amazing - good find - that did fix the problem
what is peculiar though, is that this was allegedly necessary
since firefox v50; but it has (apparently) been working in
iceweasel, without that URL whitelisted, until only a few
versions ago
diff --git a/libre/iceweasel/vendor.js.in b/libre/iceweasel/vendor.js.in
index cccb37aae..1569e9858 100644
--- a/libre/iceweasel/vendor.js.in
+++ b/libre/iceweasel/vendor.js.in
@@ -310,3 +310,6 @@ pref("extensions.getAddons.showPane", false);
// Setting these preferences just in case and to not frustrate users.
pref("app.normandy.api_url", "http://127.0.0.1/");
pref("app.normandy.enabled", false);
+
+// enable "sync" feature
+pref("webchannel.allowObject.urlWhitelist", "https://content.cdn.mozilla.net https://support.mozilla.org https://install.mozilla.org https://accounts.firefox.com");
Updated by bill-auger over 1 year ago
- Related to Bug #2554: [icecat]: can not sign in to sync added
Updated by bill-auger over 1 year ago
- Status changed from confirmed to fixed
iceweasel 104.0.1 has this patch applied