Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

ค้นหาฝ่ายสนับสนุน

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.

เรียนรู้เพิ่มเติม

I got an error "SSL peer was unable to negotiate an acceptable set of security parameters. SSL_ERROR_HANDSHAKE_FAILURE_ALERT"

  • 3 การตอบกลับ
  • 2 คนมีปัญหานี้
  • 1 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย christ1

more options

I can't find the detail in the link on the error page https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean

Do you have the explanation of this error?

I can't find the detail in the link on the error page https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean Do you have the explanation of this error?

การตอบกลับทั้งหมด (3)

more options

Please post a screenshot of the error message. https://support.mozilla.org/en-US/kb/how-do-i-create-screenshot-my-problem

What site are you trying to access? Please provide a link.

more options

Thanks for your reply. Unfortunately, My browser use Japanese Language. So it's difficult to understand what they said.

I can point you the link.Please check this. https://www.re-guide.jp/mypage/auto_login.php

more options

According to the SSL Labs test the site looks very reasonable. https://www.ssllabs.com/ssltest/analyze.html?d=www.re-guide.jp

Why it doesn't work with Firefox, I don't know. I can only guess about a server configuration error. Try to contact the web site owner.

The site doesn't work in Chrome either, so it's unlikely that this is a Firefox issue.