-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSL handshake failed #29
Comments
What is your |
There are multiple reports of this issue. I will look into it and reply shortly. Thank you for your patience. |
After careful investigation, I found that you cannot use |
BTW, under Windows, replace all the |
@CURAS This issue is finally resolved. In v1.2.0, you'll be able to verify using the original certificate. |
When I connect my own server with client, it will show these error infos.
server:
client:
I set
cert.pem
for cert,privkey.pem
for key and keep empty for key password in my server's configuration file, which are provided by Let's Encrypt. And I also setcert.pem
for cert in my client's configuration file.I don't know if I choose a wrong certificate, and when I choose
fullchain.pem
, these error infos disappeared again.The text was updated successfully, but these errors were encountered: