[BUG] Could not perform operation. Error: Error: 14 UNAVAILABLE: Empty update

[bla-ckbox]

Describe the bug can not save profile / test connection

To Reproduce Save profile with Auth and Secure connection

Desktop

• Windows 10
• ETCD manager version 1.2.0

Additional context

• etcd Version 3.4.13

{
  "profiles": [
    {
      "etcd": {
        "hosts": "172.18.16.190",
        "dialTimeout": 30000,
        "retry": false,
        "port": 2379,
        "ssl": {
          "enabled": true,
          "certificate": "C:\\Temp\\client.pem",
          "certKey": "C:\\Temp\\client-key.pem",
          "certChain": "C:\\Temp\\ca.pem"
        }
      },
      "config": {
        "language": "en",
        "animateBg": false,
        "background": true,
        "name": "default"
      },
      "watchers": {
        "autoload": false,
        "reconnects": true,
        "disconnects": true,
        "error": true
      },
      "etcdAuth": {
        "username": "foobar",
        "password": "********"
      },
      "credentials": {
        "rootCertificate": {
          "type": "Buffer",
          "data": [...truncated...]
        },
        "privateKey": {
          "type": "Buffer",
          "data": [...truncated...]
        }
      }
    }
  ]
}

[Bonehead5338]

+1

[raf924]

+1

[i4004]

Same error on me, couldn't find workaround yet. With etcdctl it works.

[mrysbekov]

+1

[yangtingtools]

Same error on me,can you help me.

[smile-luobin]

Same error on me,can you help me.

[gtamas]

Thanks for reporting this, I will look into this.

Currently I have little for this project but I will get back to it as soon as I can.

In the meantime, PRs are welcome :) If anyone wants to help, please contact me!. Comment below and mention me.

Thanks in advance!

[daviesluke]

+1

[AlexBar]

The same issue here

[ChrLau]

Hi, same error here under Ubuntu 20.04. What I notice is that there is an error message in the console window when I try to save the profile:

E0922 13:22:44.589153685 14203 ssl_transport_security.cc:1245] Handshake failed with fatal error SSL_ERROR_SSL: error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED.

Our etcd hosts do use SSL-Certs provided by an company internal CA. Those Rootcerts are in my system keystore, but of course will never be publically available. As far as I know snap is not able to use the system certificate store?

What is a bit misleading is: The connection test is successful. And I entered an HTTPS-URL. So I assume this really just checks network connectivity and NOT additionally the SSL Handshake? Would be nice if the test would do both. Oh, and of course an option to add custom CA certs :-)

I guess what happens is (without looking at any code): Test connection only verifies network connectivity. Upon clicking "save profile" etcd-manager tries to actually connect to the etcd host(s) and gather the required information to add it to the profile. This fails at the SSL Handshake and we end up with this lovely error message. :smile:

Problems with CA certs which are not in the official Browser CAB Truststore seem like a common issue with snaps: https://forum.snapcraft.io/t/using-the-system-certificate-authorities/10732/10

[ChrLau]

I tried to add the CA cert to snap via: snap set system store-certs.cert1="$(cat /path/to/mycert)"

After reading: https://forum.snapcraft.io/t/system-options/87

Still the same error. An mount --bind /etc/ssl /snap/core18/current/etc/ssl/ also didn't work.

[onedr0p]

@ChrLau even if you added the SSL certs it still won't work. It's an issue with the software. If we couldn't make it work without snap, you won't get it working with snap.

[ChrLau]

@onedr0p Well it was just speculation from my side and I was willing to spent the time trying. Additionally I saw noone trying similiar steps/workarounds here, therefor I posted it here so other people can skip trying these steps.

But given the fact that this software is unmaintained for 2 years we decided against it, even if there will be a workaround some time in the future..

[glebyan]

Same issue on macos ventura 13.2 (22D49) M1

[ZhangSIming-blyq]

Same issue on Macos (2023-07-26) connecting with client.crt, client.key and ca.crt.