Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Add exception to self-signed URL system wide

  • 5 Antworten
  • 1 hat dieses Problem
  • 11 Aufrufe
  • Letzte Antwort von Mike Kaply

more options

Hello everyone.

We are using a software in my company that runs a local server with a self-signed certificate. In order to access the software right now we need to instruct the users to manually bypass the warning page for potencial security risks.

Is there a way to use an autoconfig or policy to automatically add the exception to that specific URL? I see that copying the cert_override.txt file in users profiles will add the exception, but I'd like to avoid that. I've also looked at a question with a similar problem here, but I couldn't get this specific solution to work on my end (Firefox ESR 91): https://support.mozilla.org/en-US/questions/1287443

Hello everyone. We are using a software in my company that runs a local server with a self-signed certificate. In order to access the software right now we need to instruct the users to manually bypass the warning page for potencial security risks. Is there a way to use an autoconfig or policy to automatically add the exception to that specific URL? I see that copying the cert_override.txt file in users profiles will add the exception, but I'd like to avoid that. I've also looked at a question with a similar problem here, but I couldn't get this specific solution to work on my end (Firefox ESR 91): https://support.mozilla.org/en-US/questions/1287443

Alle Antworten (5)

more options

That solution should still work if you use autoconfig. What specific problem were you running in to?

more options

Hello Mike,

When using this solution we get an error on startup, saying it failed to read the autoconfig file, see the image attached. I'm using this code on mozilla.cfg, where I store all the pref and lockPref properties, should I use it on local-settings.js instead? Or is there a way to debug this? I can't seem to find an detailed error log for this.

more options

Autoconfig is sandboxed by default. Did you flip the pref so it can run arbitrary code?

If you open up the JS console after this error, it should show exactly what the problem is.

more options

OK, I've got the exact error now: ReferenceError: Services is not defined on mozilla.cfg:16

Is this some import I'm missing? Or maybe it's the pref you told me to flip? What is the name of that pref? I did not find any pref linked to running arbritary code in autoconfig.

more options

In the autoconfig.js where you set the filename and obscure_value, add:

pref("general.config.sandbox_enabled", false);