Syncronization inconsistencies/failures

[zz0rk]

Description

Debian 12 Gnome desktop v0.93.0
Debian 12 server LAN v0.93.0
Debian 12 server WAN v0.93.0 (nginx, cloudflare w/proxy)

I can synchronize from my desktop to either server. I can't synchronize from my LAN server to my WAN server.
Service error on LAN server:

● trilium.service - Trilium Daemon
     Loaded: loaded (/etc/systemd/system/trilium.service; enabled; preset: enabled)
     Active: active (running) since Fri 2025-05-02 21:41:22 PDT; 1 day 23h ago
   Main PID: 1905963 (trilium.sh)
      Tasks: 12 (limit: 19095)
     Memory: 171.7M
        CPU: 42.019s
     CGroup: /system.slice/trilium.service
             ├─1905963 /bin/sh /opt/trilium/trilium.sh
             └─1905965 ./node/bin/node src/main

May 04 20:45:52 server-LAN trilium.sh[1905965]: Sync failed: 'Request to GET https://server-WAN.com/api/setup/status failed, error: AggregateError', stack: Error: Request to GET https://server-WAN.com/api/setup/status failed, error: AggregateError
May 04 20:45:52 server-LAN trilium.sh[1905965]:     at generateError (file:///opt/trilium/src/services/request.js:161:12)
May 04 20:45:52 server-LAN trilium.sh[1905965]:     at ClientRequest.<anonymous> (file:///opt/trilium/src/services/request.js:44:49)
May 04 20:45:52 server-LAN trilium.sh[1905965]:     at ClientRequest.emit (node:events:518:28)
May 04 20:45:52 server-LAN trilium.sh[1905965]:     at emitErrorEvent (node:_http_client:104:11)
May 04 20:45:52 server-LAN trilium.sh[1905965]:     at TLSSocket.socketErrorListener (node:_http_client:518:5)
May 04 20:45:52 server-LAN trilium.sh[1905965]:     at TLSSocket.emit (node:events:518:28)
May 04 20:45:52 server-LAN trilium.sh[1905965]:     at emitErrorNT (node:internal/streams/destroy:170:8)
May 04 20:45:52 server-LAN trilium.sh[1905965]:     at emitErrorCloseNT (node:internal/streams/destroy:129:3)
May 04 20:45:52 server-LAN trilium.sh[1905965]:     at process.processTicksAndRejections (node:internal/process/task_queues:90:21)

Thank you

TriliumNext Version

v0.93.0

What operating system are you using?

Other Linux

What is your setup?

Local + server sync

Operating System Version

Debian 12

Error logs

● trilium.service - Trilium Daemon
Loaded: loaded (/etc/systemd/system/trilium.service; enabled; preset: enabled)
Active: active (running) since Fri 2025-05-02 21:41:22 PDT; 1 day 23h ago
Main PID: 1905963 (trilium.sh)
Tasks: 12 (limit: 19095)
Memory: 171.7M
CPU: 42.019s
CGroup: /system.slice/trilium.service
├─1905963 /bin/sh /opt/trilium/trilium.sh
└─1905965 ./node/bin/node src/main

May 04 20:45:52 server-LAN trilium.sh[1905965]: Sync failed: 'Request to GET https://server-WAN.com/api/setup/status failed, error: AggregateError', stack: Error: Request to GET https://server-WAN.com/api/setup/status failed, error: AggregateError
May 04 20:45:52 server-LAN trilium.sh[1905965]: at generateError (file:///opt/trilium/src/services/request.js:161:12)
May 04 20:45:52 server-LAN trilium.sh[1905965]: at ClientRequest. (file:///opt/trilium/src/services/request.js:44:49)
May 04 20:45:52 server-LAN trilium.sh[1905965]: at ClientRequest.emit (node:events:518:28)
May 04 20:45:52 server-LAN trilium.sh[1905965]: at emitErrorEvent (node:_http_client:104:11)
May 04 20:45:52 server-LAN trilium.sh[1905965]: at TLSSocket.socketErrorListener (node:_http_client:518:5)
May 04 20:45:52 server-LAN trilium.sh[1905965]: at TLSSocket.emit (node:events:518:28)
May 04 20:45:52 server-LAN trilium.sh[1905965]: at emitErrorNT (node:internal/streams/destroy:170:8)
May 04 20:45:52 server-LAN trilium.sh[1905965]: at emitErrorCloseNT (node:internal/streams/destroy:129:3)
May 04 20:45:52 server-LAN trilium.sh[1905965]: at process.processTicksAndRejections (node:internal/process/task_queues:90:21)

[eliandoran]

@zz0rk , looks like a network/DNS issue.
Can you provide the full logs to better understand the issue?

[zz0rk]

The log showed the exact same error for each time I did a test sync, no additional information. I did realize though what caused the issue. I had recently enabled VPN tunneling for a certain network range. The server LAN was part of that range, my desktop was not. Thank you!