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

New desktop install will not sync with server. #4845

Closed
Phalen opened this issue Aug 13, 2024 · 5 comments
Closed

New desktop install will not sync with server. #4845

Phalen opened this issue Aug 13, 2024 · 5 comments

Comments

@Phalen
Copy link

Phalen commented Aug 13, 2024

Trilium Version

0.63.7

What operating system are you using?

Windows

What is your setup?

Local + server sync

Operating System Version

Win 10 19045.4651 & mx linux

Description

MX linux works fine and is properly synched. I closed out of that client and then ran the windows client on my win pc. the win install I selected the sync from server. It accepted the right user/pass after i put the wrong one in and now is stuck on synching with 0 items left to sync. logs dont show any thing usefull.

Error logs

09:40:13.019 Returning sync stats: {"initialized":false,"outstandingPullCount":0}
09:40:13.019 304 GET /api/sync/stats with 46 bytes took 0ms

@xmzml
Copy link

xmzml commented Aug 15, 2024

I also encountered this problem. It got stuck when syncing to a fixed number, Outstanding sync items: 819, and it stayed here forever.

@xmzml
Copy link

xmzml commented Aug 15, 2024

Maybe I should change to a different version first. Any suggestions other than 0.63.7?

@meichthys
Copy link
Collaborator

@xmzml
Copy link

xmzml commented Aug 16, 2024

@Phalen The problem can be solved by copying the server's document.db directly to Windows' C:\Users\xxx\AppData\Roaming\trilium-data.

@Phalen
Copy link
Author

Phalen commented Aug 16, 2024

@xmzml Thanks so much for that as that resolved the issue.

@meichthys Now that i realize it is available I just upgraded my desktop to that version. the 2nd system that was having this issue did not care which version you used it got the same error. ironically the server was next even though I didn't realize it. I greatly appreciate the link as that has helped me as well.

@Phalen Phalen closed this as completed Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants