搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Reason for error : <ip address>:8443 uses an invalid security certificate. The certificate is only valid for <ip address> Error code: SSL_ERROR_BAD_CERT_DOMAIN

more options

Getting following domain mismatch error in firefox while domain name is correct (<ip address>) Also Subject Alternative Name has value DN Name=<ip address>

Getting following message in browser

https://<ip address>:8443/ Unable to communicate securely with peer: requested domain name does not match the server’s certificate. HTTP Strict Transport Security: false HTTP Public Key Pinning: false

Getting following domain mismatch error in firefox while domain name is correct (<ip address>) Also Subject Alternative Name has value DN Name=<ip address> Getting following message in browser https://<ip address>:8443/ Unable to communicate securely with peer: requested domain name does not match the server’s certificate. HTTP Strict Transport Security: false HTTP Public Key Pinning: false

所有回覆 (3)

more options

uninstall Firefox. Then Delete the Mozilla Firefox Folders in C:\Program Files and C:\Program Files(x86) Then restart system. Then run Windows Disk Cleanup. (Note: This should be Pinned and run Weekly, If never done below expect 10's of gig's) Then run it again and click the button that says Cleanup System Files. Note: your Firefox Profile is saved. But you should make a back up before you do :

Reinstall with Current Release Firefox 57.0.2 with a Full Version Installer

Please let us know if this solved your issue or if need further assistance.

more options

or : 52.5.2 ESR. It will continue to get security updates until May 2018, and you can download and install it from this page: *https://www.mozilla.org/en-US/firefox/organizations/all/ Note : Legacy Extensions will be deleted or removed in any version update after May 2018.

You should make a backup of your Profile before going back and just because:

Please let us know if this solved your issue or if need further assistance.

more options

This could be an issue specific to IP address certificates. I don't think a non-standard port number (something other than 443) triggers a mismatch with an ordinary domain name. But I don't have an easy way to confirm that...