Import missing host.ignoreCertErrors
EntropyWorks opened this issue · comments
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?
I'm using the nightly build for MacOS. I had exported the config from a working nightly build on another MacOS machine. When importing the config into the new laptop it appears to connect but just sits there connecting.
- Working Sieve.app export configuation
- New laptop download new version of Sieve.app from nightly build.
- Import old config
- Fails to work
- Delete config
- Manually enter settings from the exported json file.
- Make sure to have Fingerprint set
- Fails to connect
- Open up Developer Tools
- Application -> Storage -> Local Storage -> file://
- @krmi707c-8yx53fzo6j.host.ignoreCertErrors = UNABLE_TO_VERIFY_LEAF_SIGNATURE
- That seems to have fixed it!!!
What did you expect to happen?
I expected the import to work and prompt me for a password. Adding KEY=@krmi707c-8yx53fzo6j.host.ignoreCertErrors VALUE=UNABLE_TO_VERIFY_LEAF_SIGNATURE by hand fixed things.
Screenshots
Which Version
- Standalone app
- MacOS nightly build
- Postfix Dovecot
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Confirmed reproduced on Windows. Can only get past the error message by adding UNABLE_TO_VERIFY_LEAF_SIGNATURE in the debugger > Application > Storage > file:// > ???.host.ignoreCertErrors. Application doesn't set this when the warning dialog is OK'd. Value stays at "undefined".
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This bot is way too anxious.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Or the issue isn't getting the attention it would need...?
Same here. Spent hours on trying to modify LevelDB externally. Then found this issue and the "solution".
The error still exists. I do not get it on my old server, but my new one is all of a sudden producing this error.
Any insights where this does come from server-wise and how I could make it operational again?
I am planning to migrate to the new server - but not while Sieve is not working. ;)
The error still exists. I do not get it on my old server, but my new one is all of a sudden producing this error. Any insights where this does come from server-wise and how I could make it operational again?
I am planning to migrate to the new server - but not while Sieve is not working. ;)
Sorry for bumping this issue, but I am still stuck and I am not able to apply the suggested workaround.
Is there any chance that this error will get fixed in the near future? I am really stuck with my migration;
and I dont want to search for new tools to manage my sieve files.