gaschz/trilium
1
0
Fork 0
mirror of https://github.com/zadam/trilium.git synced 2025-06-06 18:08:33 +02:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Updated Synchronization (markdown)

zadam 2023-10-19 00:16:30 +02:00
parent ebfcdafb44
commit 92dbd50371
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Synchronization.md

@ -49,6 +49,12 @@ Two different setups are supported:
* you can explicitly set proxy server to be used in Options / Sync. Only unauthenticated proxy servers are currently supported. * you can explicitly set proxy server to be used in Options / Sync. Only unauthenticated proxy servers are currently supported.
* if no proxy server is explicitly configured, then Trilium will use system proxy settings * if no proxy server is explicitly configured, then Trilium will use system proxy settings
## Troubleshooting
### Different date/time on client and server
For a successful sync, both client and server need to have save date time, with a tolerance of maximum 5 minutes difference.
## Certificate issues ## Certificate issues
When TLS is in use, Trilium client will attempt to verify the server certificate. In some cases (self-signed certs, some corporate proxy servers), the verification will be unsuccessful and sync will fail. In those cases, you can run the Trilium client with environment variable `NODE_TLS_REJECT_UNAUTHORIZED` set to `0`: When TLS is in use, Trilium client will attempt to verify the server certificate. In some cases (self-signed certs, some corporate proxy servers), the verification will be unsuccessful and sync will fail. In those cases, you can run the Trilium client with environment variable `NODE_TLS_REJECT_UNAUTHORIZED` set to `0`: