Firefox update blocked by firewall
Yesterday I've got a report from one company about Firefox update being blocked by their firewall. Once it's on, the update fails. Turning it off fixes the update problem, but also open their network, which is not desired. I advised to whitelist domains mentioned in article https://developer.mozilla.org/en-US/docs/Mozilla/Setting_up_an_update_server (aus2.mozilla.org and download.mozilla.org), but seems it did not help. Firefox update still failed with "Update failed" message. So what servers Firefox needs access to during the update process so they can whitelist them?
EDIT: Just to add, before whitelisting the mentioned domain, Firefox won't be able to even find the update. Now the update if found, but fails when downloading.
Geändert am von Michal Stanke
Ausgewählte Lösung
The response I have got at #releng on IRC: Firefox first checks the updates available on one of the aus.mozilla.org, aus2 - aus5.mozilla.org servers, than it gets the update. In downloading the update ftp.mozilla.org, archive.mozilla.org or download.cdn.mozilla.net are usually involved.
But other functionality can be also influenced (add-on updates, plugin checks, etc.). It's good to check about:config preferences containing %LOCALE%. Some more can be found for mozilla.org, mozilla.net and mozilla.com.
I will check back with the administrator, who originally asked me this question and mark as resolved, once the updates work for them.
Diese Antwort im Kontext lesen 👍 0Alle Antworten (5)
If the update can't work, get the full version; Download Firefox For All languages And Systems {web link}
Downloading the full installer manually for each even minor update is not a solution here. Whitelisting the update servers is, I am just looking for a list of servers actually need during the update, to let them know. Do you know if and where is such list written, or who would know it?
I've called the big guys to help you. Good luck.
Ausgewählte Lösung
The response I have got at #releng on IRC: Firefox first checks the updates available on one of the aus.mozilla.org, aus2 - aus5.mozilla.org servers, than it gets the update. In downloading the update ftp.mozilla.org, archive.mozilla.org or download.cdn.mozilla.net are usually involved.
But other functionality can be also influenced (add-on updates, plugin checks, etc.). It's good to check about:config preferences containing %LOCALE%. Some more can be found for mozilla.org, mozilla.net and mozilla.com.
I will check back with the administrator, who originally asked me this question and mark as resolved, once the updates work for them.
You can use the Live Http Headers extension to check the HTTP request headers and check what URLs are involved.