In my own profile on my old Win10 Joplin 3.0.15 (prod, win32), I make Joplin Cloud Shares available to others.
In my own profile on my old Win10 Joplin 3.0.15 (prod, win32), I have 0 problems with encryption.
Recently, I created a new Joplin Cloud account for someone else and a new profile in Joplin.
In this new profile, I get a Joplin Cloud Share from my own profile.
In this new profile on my old Win10 Joplin 3.0.15 (prod, win32), I have 45 encryption issues.
In this new profile on my new Win11 Joplin 3.0.15 (prod, win32) I have 453 encryption problems.
Question: What can I do to fix all encryption problems on all Windows Joplins?
Screenshots
In my own profile on my old Win10 Joplin 3.0.15 (prod, win32), I have 0 problems with encryption.
Joplin 3.0.15 (prod, win32)
Client-ID: "the old one on Win10"
Sync-Version: 3
Profil-Version: 47
Unterstützter Schlüsselbund: Ja
Note: What I've done so far to try to reproduce this locally.
I'm recording what I've done so far. As commented below, there are at least 1-2 major differences between my test setup and the setup in the reported issue.
Possible difference 0: Device and Joplin locale is English (USA), tests were done on a Linux computer (Fedora 40).
Started test Joplin Server instance.
Possible difference 1: I'm testing with Joplin Server. My main account is a Joplin Server account and will differ somewhat from a Joplin Cloud Teams user.
Created a secondary account (can share with other users).
Email: self2@localhost.
Possible difference 2: Number of users shared with at a time?
Possible difference 3: Secondary account type?
Attempted to share a notebook with self2@localhost containing 2054 notes and one subnotebook, though not many resources (and all smaller than a few megabytes).
Possible difference 4: Maximum resource size?
Switched back to the secondary account and enabled encryption.
I was previously shown an error similar to "self2@localhost must enable encryption".
Switched back to the primary account and completed the share.
While waiting for sync, added 1-2 resources to a note.
Verified that sync completed successfully.
Created 5 more test accounts. (share-user-1@localhost, ...)
Enabled encryption for each account.
Switched back to the main account.
Shared with share-user-1@localhost.
Stopped Joplin Server.
Tried to share with share-user-2@localhost (this failed)
Started Joplin Server.
Shared with share-user-2@localhost, share-user-3@localhost, share-user-4@localhost, and share-user-5@localhost.
Changed a note in the subfolder of the shared folder.
Synced.
Switched to share-user-2@localhost's profile.
Synced.
Verified that there are no decryption errors.
Attached a 244 MB attachment to a new note.
Synced.
Got an "Uploading items larger than 250 MB is currently disabled" error.
Synced again.
Deleted the attachment.
Clicked cancel.
Waited for "Cancelling..." to go away.
Next, I plan to try reducing the differences documented above. If I'm still unable to reproduce the issue, logs (which may contain a more detailed error message) may help.
One (1) Joplin Cloud Teams account sharing folder with three (3) Joplin Cloud Basic accounts.
Sharing started when no read-only option was available. Changed to read-only option when I found it was available as a new feature.
The problem also occurs with Joplin 3.1.24 (prod, win32).
This is a disappointment as seamless note sharing is one of the key features I pay for with Joplin's cloud accounts and which was promised priority support for.
Since I don't have access to the Win11 computer documented above at the moment, I installed Joplin on a new Win11 computer, set the user interface to English and reproduced the problem as far as possible.
That depends on what you consider normal.
I, for example, don't understand how the number Total 1377/1377
from the sync status is supposed to fit logically with the number Decrypted items 1554/1554
In this log, I notice the following lines in particular,
which seems to contradict the screenshot above:
2024-12-04 20:16:15: DecryptionWorker: cannot start because no master key is currently loaded.
and 2024-12-04 20:16:15: Sync cancelled - no sync target is selected.
