Replies: 2 comments
-
There are various reports of this issue, e.g. #1533 or #1368. In some cases, this error occurs after denying permission to connect to localhost via plain http (without TLS). In this case, restarting Cryptomator is sufficient. |
Beta Was this translation helpful? Give feedback.
0 replies
-
To provide an alternative answer, in case nothing else helps: You can always switch to using FUSE instead.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Please agree to the following
Summary
No drive enable possible - restart - then it works again
What software is involved?
Volume Type
No response
Steps to Reproduce
Expected Behavior
Actual Behavior
No release from LW
Reproducibility
Always
Relevant Log Output
No response
Anything else?
No response
Beta Was this translation helpful? Give feedback.
All reactions