Skip to content
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

Closed
CURAS opened this issue Apr 2, 2018 · 7 comments
Closed

SSL handshake failed #29

CURAS opened this issue Apr 2, 2018 · 7 comments
Assignees

Comments

@CURAS
Copy link

CURAS commented Apr 2, 2018

When I connect my own server with client, it will show these error infos.
server:
image
client:
image

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 set cert.pem for cert in my client's configuration file.
image

I don't know if I choose a wrong certificate, and when I choose fullchain.pem, these error infos disappeared again.

@GreaterFire
Copy link
Member

What is your ssl.cert in the client config?

@CURAS
Copy link
Author

CURAS commented Apr 5, 2018

My client's config
image

My client's folder
image

My server's config
image

@CURAS CURAS closed this as completed Apr 5, 2018
@CURAS CURAS reopened this Apr 5, 2018
@GreaterFire
Copy link
Member

There are multiple reports of this issue. I will look into it and reply shortly. Thank you for your patience.

@GreaterFire
Copy link
Member

GreaterFire commented Apr 6, 2018

After careful investigation, I found that you cannot use fullchain.pem to verify the remote certificate -- only a CA certificate can do the verifying work. That's why a self-signed certificate can verify itself: it is its own CA. So I recommend you to use CA certificate, like the one I provided (examples/ca_certs.pem-example), which is a CA list extracted from Mozilla Firefox. Or if you are using Let's Encrypt, you can use DST Root CA X3.

@GreaterFire GreaterFire self-assigned this Apr 6, 2018
@CURAS
Copy link
Author

CURAS commented Apr 6, 2018

I have tried both the certificates you provided, but I'm sorry to said the problem still exists.
By the way, it works well in my browser.
image

@GreaterFire
Copy link
Member

BTW, under Windows, replace all the \ in the path with /. It must work.

GreaterFire added a commit that referenced this issue May 6, 2018
@GreaterFire
Copy link
Member

GreaterFire commented May 6, 2018

@CURAS This issue is finally resolved. In v1.2.0, you'll be able to verify using the original certificate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants