-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
gRPC don't work with SSL/TLS #6951
Comments
Can you try specifying your key as well? Something like
I see only |
I think that for traffic encryption we don't need use certificate authorization. And |
Oh I see How did you generate certs? Thanks. |
Good morning.
Then these files was synced on all hosts. Then on host02 I launch etcd with
|
@Felixoid Can you try our master branch or Could be Go related... And I notice
This doesn't seem like our official release. We build v3.0.x with Go 1.6.3. Can you also try our official etcd releases? |
@Felixoid Any updates? |
Hello @gyuho
I built different versions of releases etcd + golang for experiments:
All works fine
Also works as expected. I think it's solution - don't to build v3.0 with go v1.7 |
Yeah v3.0.x should be used with Go 1.6.x. Closing. Thanks! |
Version
First part: noising logs from v3rpc/grpc
Config:
http2Client.notify.txt
After another server connect with enabled ssl begin to repeat string:
2016-12-06 16:31:43.093112 I | v3rpc/grpc: transport: http2Client.notifyError got notified that the client transport was broken unexpected EOF.
I think it's the root of the next problem
Second part: etcdctl didn't work with enabled encryption
ok, drop database, try again with
| grep -v
Config:
auto-tls.txt
auto-tls-etcdctl.txt
Reproduced also with valid cert+key+cacert
Config:
tls.txt
tls-etcdctl.txt
Trace of the server with the last config
trace.txt
The text was updated successfully, but these errors were encountered: