Join us and the lead editor of IRL, Mozilla's multi-award-winning podcast, for a behind-the-scenes look at the pod and to contribute your ideas for the next season, themed: "AI and ME." Mark your calendar and join our Community Call on Wednesday, Aug 7, 17:00–17:45 UTC. See you there!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Rohkem teavet

Teema arhiveeriti. Please ask a new question if you need help.

Permanently store exception for untrusted connections only available when FIrefox is launched as an admin

  • 2 vastust
  • 5 on selline probleem
  • 3 views
  • Viimati vastas Jon23342

Jon23342
Jon23342
more options

Specs: Firefox 16.0.1 

           Windows 7 64 bit
           Joined to Windows Domain

I use sites that use self signed certs. When launching firefox normally, I add the exception (the permanently store exception is greyed out). This only lasts for that session. Once you close Firefox, need to add the exception again. Only when launched as an admin, am I able to check Permanently store.

Machine is joined to a windows domain. Anyone know about this. Is there a policy in AD that can fix?

Specs: Firefox 16.0.1 Windows 7 64 bit Joined to Windows Domain I use sites that use self signed certs. When launching firefox normally, I add the exception (the permanently store exception is greyed out). This only lasts for that session. Once you close Firefox, need to add the exception again. Only when launched as an admin, am I able to check Permanently store. Machine is joined to a windows domain. Anyone know about this. Is there a policy in AD that can fix?

All Replies (2)

Jon23342
Jon23342 Küsimuse esitaja
more options

Troubleshooting done - Uninstalled and reinstalled latest version of Firefox, deleted cert_override.txt and cert8.db files, started Firefox without add-ins.

no solution

Jon23342
Jon23342 Küsimuse esitaja
more options

Created non-domain local user account on the machine and it works....obviously policy issue