2nd desktop client install fails.

[Phalen]

Description

initial install of server and client always works normally. .94+ version. current server is 98.1 and client is 99.4 multiple client and server versions with the same result. the 2nd install always fails during initial sync
`### Trilium Notes setup

Sync in progress
Sync has been correctly set up. It will take some time for the initial sync to finish. Once it's done, you'll be redirected to the login page.

Outstanding sync items: 0`

if i copy the data dir from another desktop install it will not sync. it can push data to the server but not recieve it.

TriliumNext Version

0.99.4

What operating system are you using?

Other (specify below)

What is your setup?

Local + server sync

Operating System Version

Win 10 mx23.5 mx25.0rc1 ubuntu 24.10

Error logs

05:59:36.020 📦 Versions: app=0.99.4 db=233 sync=36 clipper=1.0
05:59:36.020 🔧 Build: 2025-11-09 20:13:06 (06eb30c)
05:59:36.020 📂 Data dir: C:\Users\Kendrick\AppData\Roaming\trilium-data
05:59:36.020 ⏰ UTC time: 2025-11-11 10:59:35
05:59:36.021 💻 CPU: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (8-core @ 3408 Mhz)
05:59:36.021 💾 DB size: 4 KiB
05:59:36.021
05:59:36.024 DB not initialized, please follow on-screen instructions.
05:59:36.061 Trusted reverse proxy: false
05:59:36.061 App HTTP server starting up at port 37840
05:59:36.224 Listening on port 37840
05:59:59.114 Getting document options FROM sync server.
05:59:59.232 Creating database for sync
05:59:59.254 Schema and not synced options generated.
05:59:59.254 Triggering sync.
05:59:59.256 Slow 200 POST /api/setup/sync-from-server with 20 bytes took 142ms
05:59:59.286 Sending message to all clients: {"type":"sync-push-in-progress","lastSyncedPush":0}
05:59:59.286 Sync djjodki6gc: Pushing 1 sync changes in 10ms
05:59:59.286 Nothing to push
06:00:00.266 Returning sync stats: {"initialized":false,"outstandingPullCount":0}
06:00:00.266 200 GET /api/sync/stats with 46 bytes took 0ms
06:00:01.274 Returning sync stats: {"initialized":false,"outstandingPullCount":0}
06:00:01.274 304 GET /api/sync/stats with 46 bytes took 0ms
06:00:02.264 Returning sync stats: {"initialized":false,"outstandingPullCount":0}
06:00:02.264 304 GET /api/sync/stats with 46 bytes took 1ms
06:00:03.277 Returning sync stats: {"initialized":false,"outstandingPullCount":0}
06:00:03.278 304 GET /api/sync/stats with 46 bytes took 1ms
.....................................................
06:01:17.495 304 GET /api/sync/stats with 46 bytes took 1ms
06:01:59.288 Sync failed: 'Process exceeded time limit 120000', stack: Error: Process exceeded time limit 120000
at S9 (C:\Users\Kendrick\AppData\Local\trilium\app-0.99.4\resources\app.asar\main.cjs:8:198891)
at eB (C:\Users\Kendrick\AppData\Local\trilium\app-0.99.4\resources\app.asar\main.cjs:1752:6823)
at V7i (C:\Users\Kendrick\AppData\Local\trilium\app-0.99.4\resources\app.asar\main.cjs:1752:4574)
at C:\Users\Kendrick\AppData\Local\trilium\app-0.99.4\resources\app.asar\main.cjs:1752:3212
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async Object.RYr [as doExclusively] (C:\Users\Kendrick\AppData\Local\trilium\app-0.99.4\resources\app.asar\main.cjs:16:3678)
at async Object.WWe [as sync] (C:\Users\Kendrick\AppData\Local\trilium\app-0.99.4\resources\app.asar\main.cjs:1752:3033)
06:02:05.508 Returning sync stats: {"initialized":false,"outstandingPullCount":0}
06:02:05.509 304 GET /api/sync/stats with 46 bytes took 1ms
06:03:05.537 Returning sync stats: {"initialized":false,"outstandingPullCount":0}
06:03:05.538 304 GET /api/sync/stats with 46 bytes took 1ms
......................................

[dosubot]

Hi @Phalen! I'm Dosu and I’m helping the Trilium team.

Your second desktop client fails initial sync because the process exceeds the 120-second timeout, leaving the database uninitialized and sync stuck at initialized:false with no outstanding items. This is a known issue that can happen even with modestly sized databases, especially after copying a data directory or when large attachments or problematic notes are present. Copying the data directory directly can also cause sync state mismatches or deadlocks, allowing pushes but blocking pulls from the server.

A recommended workaround is to export all root notes from the server's web frontend, import them into the new desktop client, and then reconfigure sync in the client settings. This avoids the problematic direct sync or document.db copy methods that often reproduce the timeout error. If you see authentication errors or session issues, deleting or renaming the local trilium-data directory and starting sync from scratch can help. Also, check for large attachments or unusual notes that might be slowing down sync, and try removing them if possible. More details and step-by-step suggestions are available in this discussion and here.

If the problem persists, ensure your server isn't behind a reverse proxy with strict body size limits, and that the server's document.db isn't excessively large.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[Phalen]

the db size is just under 100mb there are screen shots for troubleshooting purposes in the notes. i have not found any attachments.

[dosubot]

Screenshots and images embedded in notes are stored as blobs in the database, not as classic attachments. Even if you don't see attachments, these blobs can add up and impact sync performance—especially during initial sync—because Trilium has to transfer all image data along with your notes. A 100MB database with many screenshots can hit sync timeouts or get stuck if the process takes too long or if there are resource constraints on the client or server.

If sync keeps failing, the most reliable workaround is to export your notes from the server web interface and import them into the new client, then set up sync again. This avoids the problematic bulk sync of blobs that often causes timeouts. For more details on how images are handled and why this impacts sync, see this discussion and the documentation.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}