In Firefox 4.0 with a Server with a self signed certificate using IPv6 I can not add a "Security Exception" for this certificate.
In Firefox 4.0 I have a server ... it contains a self signed certificate. Using IPv6 I can not add a "Security Exception" for this certificate.
1. I log onto the server (using IPv6). I get the "Untrusted connection page" saying "This connection is Untrusted"
2. I click on "Add Exception.." under the "I understand the Risks" section.
3. The "Add Security Exception" dialog comes up. soon after the dialog comes up I get an additional "Alert" dialog saying
An exception occured during connection to xxxxxxxxx. Peer's certificate issuer has been marked as not trusted by the User. (Error code sec_error_untrusted_issuer).
Please note that this works in Firefox 3.6.16 (in IPv4 and IPv6). It also works in Firefox 4.0 in IPv4 only IPv6 has an issue. What's wrong?
تمام جوابات (3)
Exactly the same problem, except I'm using FF v6 for Windows, not FF v4 as for the lead post. This is for a self-cert which IS trusted, although the error message says it isn't.
I have the same problem with Firefox 6 on Windows connecting to any IPv6 address with a self-signed certificate. IPv4 address do not yield problems.
Isarian کی جانب سے میں ترمیمکی گئ
Still broken in Firefox 7, Firefox 8 Workaround: use Firefox 3 else Chrome
And on Linux x86_64, Fedora 13 speaking to print servers, routers, nas boxen.
This is a frequent occurrence when using broken self-signed certificates on locally-maintained print servers and/or hardware devices.
The error message (containing a valid IPv6 address) is as follows: An error occurred during a connection to 2001:ffff:ffff:0:ffff:ffff:feff:ffff:631. Peer's certificate issuer has been marked as not trusted by the user. (Error code: sec_error_untrusted_issuer
It would be super-duper helpful if the error message explained more about the certificate issuer and where it was marked as non-trusted, and how to unmark it. It remains the case that these indicate mis-configuration which cannot be changed on the server side because that mis-configured server is the *only* service portal access. Gotta be a way to drop the shields.