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

Can't add exception for self signed certificate

  • 1 Antwort
  • 11 haben dieses Problem
  • 3 Aufrufe
  • Letzte Antwort von Mark Sapiro

more options

I have a Motorola Droid Turbo phone with Android 5.1 and Firefox 41.0.2.

My personal site has a self signed certificate. When I initially got this phone in July, I was using a then current but older version of Firefox and was able to add a security exception for my site. My certificate subsequently expired and I updated it and I am now unable to add the exception. If I go to an https URL on my site, I get the 'This Connection is Untrusted' page. Tapping 'Technical Details' tells me the certificate is self signed as expected.

Tapping 'I Understand the Risks' gets me the 'Visit site' and 'Add permanent exception' buttons, but tapping either of these just refreshes the 'This Connection is Untrusted' page without going to the URL or adding the exception.

I have a Motorola Droid Turbo phone with Android 5.1 and Firefox 41.0.2. My personal site has a self signed certificate. When I initially got this phone in July, I was using a then current but older version of Firefox and was able to add a security exception for my site. My certificate subsequently expired and I updated it and I am now unable to add the exception. If I go to an https URL on my site, I get the 'This Connection is Untrusted' page. Tapping 'Technical Details' tells me the certificate is self signed as expected. Tapping 'I Understand the Risks' gets me the 'Visit site' and 'Add permanent exception' buttons, but tapping either of these just refreshes the 'This Connection is Untrusted' page without going to the URL or adding the exception.

Alle Antworten (1)

more options

I just upgraded Firefox on my phone to version 42.0 and still have the same issue.