Dette websted vil have begrænset funktionalitet, mens vi gennemgår vedligeholdelse for at forbedre din oplevelse. Hvis en artikel ikke løser dit problem, og du vil stille et spørgsmål, har vi vores supportfællesskab, der venter på at hjælpe dig på @FirefoxSupport på Twitter og/r/firefox på Reddit.

Avatar for Username

Søg i 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.

Læs mere

Denne tråd blev arkiveret. Stil et nyt spørgsmål, hvis du har brug for hjælp.

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

  • 2 svar
  • 5 har dette problem
  • 3 visninger
  • Seneste svar af 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?

Alle svar (2)

Jon23342
Jon23342 Spørgsmålsstiller
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 Spørgsmålsstiller
more options

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