-
Notifications
You must be signed in to change notification settings - Fork 193
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
[Bug]: Error when trying to sync vault with E2E encryption #737
Comments
go to onedrive website, is there any unencrypted files inside |
I have same issue with Ubuntu 22.04 and Windows, iPhone. I'm using R1 for storage to sync.In my situation, the encrypted files are stored in R1 bucket including .obsidian folder because I'm using option for synchronizing config. There are no failure with no password but it occurs extracting encrypted files directly. In addition, I'm also facing anothor issue which the original local vault (this is stored in Ubuntu 22.04) cannot sync to remote after once closing obsidian. From these phenomenons, I guess there are some issues on encrypt/decrypt modules. I'm using:
ps: |
go to r2 website, is there any unencrypted files inside uour encrypted vault? |
No. All files are encrypted. |
so is the issue still consistently reproducible now? |
I could resolve the issue in my case. |
if a consistent reproducible step is found, please post it here and you are welcome to re open the issue |
What happened?
I have saved a drive on windows, setting a password. I can confirm I can see the folder with encrypted files at in Apps/remotely-save/
After going on to my mac
I get the error shown in the screenshot. If I set no password on the mac side, I pull the encrypted files, so the connection is definitely OK.
What OS are you using?
Windows, macOS
What remote cloud services are you using? (Please choose the specified one if it's in the list)
OneDrive for personal
Version of the plugin
0.5.12
Version of Obsidian
1.6.5
Using password or not
Ensure no sensitive information
The text was updated successfully, but these errors were encountered: