You can check the Browser Console to see if there is more info available about this issue with an autoconfig.cfg file.

• https://developer.mozilla.org/en-US/docs/Tools/Browser_Console

It is possible that an autoconfig.cfg is specified, but that the file is missing or has errors.

• https://support.mozilla.org/en-US/kb/customizing-firefox-using-autoconfig

You can look at the "Help -> More Troubleshooting Information" (about:support) page for the location of the Firefox installation folder.

You can check what .js files are present in the "defaults/pref" folder in the Firefox installation folder. The channel-prefs.js file that sets app.update.channel is a legitimate file in this folder, any other .js file is suspicious. You can open this suspect file in a plain text editor like TextEdit and please post its content to see whether that allows to identify what software created the file. Also please post the content of the autoconfig.cfg file referenced in this autoconfig.js file.

There shouldn't be a autoconfig.cfg file present unless you've created it yourself to initialize some prefs.

If you have this autoconfig.cfg file then best is to do a clean reinstall and delete the Firefox program folder to make sure that all files are removed before reinstalling a freshly downloaded copy of Firefox.

Hi twolf, As I understand it, Filewave is used for controlling deployments over an organization. In that case, I would recommend using the enterprise version of Firefox. You can find more information in the following link: https://www.mozilla.org/firefox/enterprise/

Hi twolf, As I understand it, Filewave is used for controlling deployments over an organization. In that case, I would recommend using the enterprise version of Firefox. You can find more information in the following link: https://www.mozilla.org/firefox/enterprise/

Hi Chris, I am already using the enterprise version of Filewave. Thanks for the prompt reply, I would have responded sooner but I was out of the Country for two-weeks.

You can check the Browser Console to see if there is more info available about this issue with an autoconfig.cfg file.

• https://developer.mozilla.org/en-US/docs/Tools/Browser_Console

It is possible that an autoconfig.cfg is specified, but that the file is missing or has errors.

• https://support.mozilla.org/en-US/kb/customizing-firefox-using-autoconfig

You can look at the "Help -> More Troubleshooting Information" (about:support) page for the location of the Firefox installation folder.

---

You can check what .js files are present in the "defaults/pref" folder in the Firefox installation folder. The channel-prefs.js file that sets app.update.channel is a legitimate file in this folder, any other .js file is suspicious. You can open this suspect file in a plain text editor like TextEdit and please post its content to see whether that allows to identify what software created the file. Also please post the content of the autoconfig.cfg file referenced in this autoconfig.js file.

There shouldn't be a autoconfig.cfg file present unless you've created it yourself to initialize some prefs.

If you have this autoconfig.cfg file then best is to do a clean reinstall and delete the Firefox program folder to make sure that all files are removed before reinstalling a freshly downloaded copy of Firefox.

There are three .js files in the "defaults/prefs" folder. autoconfig.js, channel-prefs.js, and local_settings.js. I have tried to remove both of the other files but they just reappear.

I do not have an autoconfig.cfg file. The only reference I can find to a .cfg file is in the local_settings.js

pref("general.config.filename","mozilla.cfg");

Content of the mozilla.cfg

// var Cc = Components.classes; var Ci = Components.interfaces; var certdb = Cc["@mozilla.org/security/x509certdb;1"].getService(Ci.nsIX509CertDB); cert1 = "" certdb.addCertFromBase64(cert1, "C,C,C", ""); lockPref("network.proxy.type", 5); lockPref("security.enterprise_roots.enabled", true);

If I remove any of the .js files they just come back. If I remove the pref folder or defaults folder it works, but I don't want to have to do this on every device. It is on there on freshly reset Macs after installing Firefox as well.

Here is where I got my PKG:

 https://ftp.mozilla.org/pub/firefox/releases/99.0.1/mac/en-US/

Chris Ilias said

Hi twolf, As I understand it, Filewave is used for controlling deployments over an organization. In that case, I would recommend using the enterprise version of Firefox. You can find more information in the following link: https://www.mozilla.org/firefox/enterprise/

Hi Chris, I am already using the enterprise version of Filewave.

Hi twolf, The enterprise version of Filewave is not the enterprise version of Firefox. The link you gave in your latest response is not the enterprise version of Firefox. Mozilla has a separate product with a separate forum for enterprise deployments. If you need help getting started, just let us know.

twolf2286 said

Chris Ilias said

Hi twolf, As I understand it, Filewave is used for controlling deployments over an organization. In that case, I would recommend using the enterprise version of Firefox. You can find more information in the following link: https://www.mozilla.org/firefox/enterprise/

Hi Chris, I am already using the enterprise version of Filewave.

Hi twolf, The enterprise version of Filewave is not the enterprise version of Firefox. The link you gave in your latest response is not the enterprise version of Firefox. Mozilla has a separate product with a separate forum for enterprise deployments. If you need help getting started, just let us know.

I will need some help then. When I followed your link I selected the PKG Installer link there and followed their directions. That's how I got to the installer the first time.

Edit: Sorry I just saw the typo in my previous post. I meant to say Firefox, not Filewave.

Hi I've moved this support thread over to the Enterprise forum, someone on the Enterprise team might be able to help.

In the meantime, the config file on mac is a PLIST file. Check out the following article for more info: Customizing Firefox on MacOS using configuration profiles

Can you post the full contents of local_settings.js? I want to make sure they are disabling the soundbox.

This is definitely a Filewave bug, though, you should reach out to them.

They really shouldn't be using Autoconfig at all anymore.

Can you post the full contents of local_settings.js? I want to make sure they are disabling the soundbox. This is definitely a Filewave bug, though, you should reach out to them. They really shouldn't be using Autoconfig at all anymore.

It doesn't matter if I do a clean install from Filewave or do it manually. It creates the auto config automatically. Here is the content of the local_settings:

pref("general.config.obscure_value",0); pref("general.config.filename","mozilla.cfg");

You have some sort of software that is doing this to your machine and they are doing it wrong.

The issue is that many many releases ago, we made autoconfig not work without an extra pref that they aren't putting in local_settings.js. So what they are doing is very dated (or only works against the ESR).

What they are doing in this file is installing a root certificate (probably something for your company or antivirus), locking it so you can't change the proxy, and then forcing it to use system certificates.

Is this a company managed machine?