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

TLS error #937

Open
3 tasks done
robertvanya opened this issue Oct 20, 2024 · 1 comment
Open
3 tasks done

TLS error #937

robertvanya opened this issue Oct 20, 2024 · 1 comment

Comments

@robertvanya
Copy link

Prerequisites

  • Tried the most recent nightly build
  • Checked if your issue is already reported.
  • Answered all the questions in this template (Or provide a working crystal ball).

What happened?

When trying to connect to the server, an "Error upgrading (DEPTH_ZERO_SELF_SIGNED_CERT)" is shown. After clicking Continue button, the same repeats in a loop, it does not connect.

  1. run the app
  2. Click the Connect button on the first connection

What did you expect to happen?

Expected to connect

Logs and Traces

If applicable, include a debug log/trace with your issue. Just go to the extensions settings and enable debugging options in the debug tab. Dumping "byte arrays" is usually not necessary. Keep in mind the line starting with "AUTHENTICATE" contains your password. So scramble this line.

Which Version

0.6.1

  • Standalone app (the addon does not show the error, but never connects either)
  • Operating system Windows 11, on Ubuntu 24 the same
  • dovecot+managesieve
@thsmi
Copy link
Owner

thsmi commented Dec 21, 2024

DEPTH_ZERO_SELF_SIGNED_CERT is a very generic error without any logs and detail on the certificate hashes it is impossible to tell what went wrong.

The real fix for this kind of errors is making sure your Root CA is deployed correctly on your clients into the corresponding cert stores, so that the application can pick it up from there and automatically trust the connection.

But as workaround if node regards your certificate as somehow trustworthy you should get a UI, which asks you if you trust the unsafe cert's fingerprints and want to set an exception for this certificate.

But as previously written there is not much more to tell without having a log and knowing the details about the certificate.

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

No branches or pull requests

2 participants