-
Notifications
You must be signed in to change notification settings - Fork 60
Open
Description
Describe the bug
Use the same certifiates (ca.pem, client.crt, client.key),the etcdctl
can connect to cluster successfully.
❯ etcdctl --cacert="ca.pem" --cert="client.crt" --key="client.key" --endpoints="https://etcd.fccl.local:2379" member list
c23fad347fee0a7, started, etcd-3, https://192.168.122.93:2380, https://192.168.122.93:2379,https://192.168.122.93:4001, false
757e7683f515eea2, started, etcd-2, https://192.168.122.92:2380, https://192.168.122.92:2379,https://192.168.122.92:4001, false
9f1c42ff2f0fc235, started, etcd-1, https://192.168.122.91:2380, https://192.168.122.91:2379,https://192.168.122.91:4001, false
But when configure it in etcd-manager
It reported errors
E0114 11:51:51.752654155 5226 ssl_transport_security.cc:690] Invalid private key.
E0114 11:51:51.752748647 5226 ssl_security_connector.cc:112] Handshaker factory creation failed with TSI_INVALID_ARGUMENT.
E0114 11:51:51.752767642 5226 secure_channel_create.cc:132] Failed to create secure subchannel for secure name '192.168.122.91:2379'
E0114 11:51:51.752777857 5226 secure_channel_create.cc:50] Failed to create channel args during subchannel creation.
To Reproduce
Steps to reproduce the behavior:
- Go to Etcd Settings
- Toggle on 'Secure connection', and browser the related certificates files.
Expected behavior
Connect to cluster successfully.
Screenshots
Se above.
Desktop (please complete the following information):
- OS: Linux (openSUSE Leap)
- OS version: 15.4
- ETCD manager version: 1.2 (AppImage)
Metadata
Metadata
Assignees
Labels
No labels