logseq / logseq/db-test

Every existing graph don't sync in browser

Open
#937 4 comments 0 reactions 1 assignee View on GitHub

@tiensonqin is already working on this.

Since Jun 19, 2026.

bug
Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### Search first

- [x] I searched and no similar issues were found

### What Happened?

I opened https://test.logseq.com/#/ in a browser again after some time and was greeted with this:

Image

I reloaded the page. The app started, but is not syncing. There i see an error.

Online
10 pending local changes
0 pending server changes

```
DB schema migrated from {:major 65, :minor 24}
core.cljs:205 DB schema migrated to {:major 65, :minor 25}
core.cljs:205 DB schema migrated to {:major 65, :minor 26}
core.cljs:205 DB schema migrated to {:major 65, :minor 27}
core.cljs:205 DB schema migrated to {:major 65, :minor 28}
core.cljs:205 DB schema migrated to {:major 65, :minor 29}
core.cljs:205 DB schema migrated to {:major 65, :minor 30}
core.cljs:205 DB schema migrated to {:major 65, :minor 31}
core.cljs:205 DB schema migrated to {:major 65, :minor 32}
core.cljs:205 DB schema migrated to {:major 65, :minor 33}
...
15:57:19.507 [frontend.handler.db-based.rtc-background-tasks] {:line 51, :try-to-start-rtc [:trigger-rtc "logseq_db_buga"]}
console.js:40 15:57:19.507 [frontend.handler.db-based.sync] {:db-sync/start {:repo "logseq_db_buga"}, :line 211}
core.cljs:4085 15:57:19.512 [frontend.worker.sync] {:db-sync/connect! {:repo "logseq_db_buga", :token-exists? true}, :line 301}
core.cljs:4085 15:57:21.579 [frontend.worker.sync] {:db-sync/ws-handle-message-failed {:repo "logseq_db_buga", :error #error {:message "Invalid local tx", :data {:repo "logseq_db_buga", :message-type "hello", :local-tx nil}}}, :line 160}
cljs.core/apply-to-simple @ core.cljs:4085Understand this error
sync.cljs:264 16:08:19.514 [frontend.worker.sync] {:db-sync/ws-stale-timeout {:repo "logseq_db_buga", :stale-ms 657935}, :line 264}
cljs.core/apply-to-simple @ core.cljs:4085
cljs.core/apply-to-simple @ core.cljs:4080
cljs.core/apply @ core.cljs:4074
(anonymous) @ console.cljs:45
log_record_handler @ glogi.cljs:199
(anonymous) @ log.js:702
getEffectiveLevel @ log.js:701
goog.log.publishLogRecord @ log.js:994
lambdaisland.glogi/log @ glogi.cljs:26
frontend.worker.sync/close-stale-ws-loop @ sync.cljs:264Understand this warning
sync.cljs:232 16:08:29.943 [frontend.worker.sync] {:db-sync/ws-closed {:repo "logseq_db_buga"}, :line 232}
sync.cljs:218 16:08:29.959 [frontend.worker.sync] {:db-sync/ws-reconnect-scheduled {:repo "logseq_db_buga", :delay 1219, :attempt 0, :reason :close}, :line 218}
sync.cljs:204 16:08:31.178 [frontend.worker.sync] {:db-sync/ws-reconnect {:repo "logseq_db_buga", :db-sync-client-exists? true}, :line 204}
sync.cljs:301 16:08:31.180 [frontend.worker.sync] {:db-sync/connect! {:repo "logseq_db_buga", :token-exists? true}, :line 301}
sync.cljs:160 16:08:32.885 [frontend.worker.sync] {:db-sync/ws-handle-message-failed {:repo "logseq_db_buga", :error #error {:message "Invalid local tx", :data {:repo "logseq_db_buga", :message-type "hello", :local-tx nil}}}, :line 160}
```

I opened 2 graph that all had this error. When opening the third, the app seem to randomly forget the password and asked again: "Enter password for remote graphs". This should not happen! (https://github.com/logseq/db-test/issues/929)

After i input the passwort, the graph opened, but is again not syncing.

```
16:30:57.891 [frontend.worker.sync.download] {:db-sync/download-graph-by-id-failed {:repo "logseq_db_dddd", :graph-id "9ae786ef-b1ce-41be-aff8-391c79853e52", :graph-e2ee? true, :stage :prepare-e2ee, :error #error {:message "ui-request-timeout", :data {:code :ui-request-timeout, :request-id "11f05d45-d4ac-4398-9dfd-ae53bab26713", :action :request-e2ee-password, :timeout-ms 60000}}, :error-stack "Error: ui-request-timeout\n at new em (https://test.logseq.com/js/db-worker.js?electron=false&capacitor=&publishing=false:662:26)\n at gm (https://test.logseq.com/js/db-worker.js?electron=false&capacitor=&publishing=false:663:315)\n at fm (https://test.logseq.com/js/db-worker.js?electron=false&capacitor=&publishing=false:663:276)\n at https://test.logseq.com/js/db-worker.js?electron=false&capacitor=&publishing=false:3669:239", :error-cause nil}, :line 538}
RTC download graph failed, error:
16:30:57.897 [frontend.handler.events] {:rtc-download-graph-failed #error {:message "db-sync download failed", :data {:repo "logseq_db_dddd", :graph-id "9ae786ef-b1ce-41be-aff8-391c79853e52", :graph-e2ee? true, :stage :prepare-e2ee, :error-message "ui-request-timeout", :error-cause nil}}, :line 397}
```

After reloading the page again, i only get this error:

```
16:35:00.809 [frontend.worker.sync] {:db-sync/ws-handle-message-failed {:repo "logseq_db_cccc", :error #error {:message "Invalid local tx", :data {:repo "logseq_db_cccc", :message-type "hello", :local-tx nil}}}, :line 160}
```

Every existing graph had this issue!

### Reproduce the Bug

1. Open https://test.logseq.com/#/ in Chrome
2. Open an existing graph (not downloading a new one)
3. Check if it syncs

### Expected Behavior

All graphs sync.

### Screenshots

_No response_

### Files

_No response_

### Browser, Desktop or Mobile Platform Information

NixOS
Google Chrome 147.0.7727.101
Logseq 2.0.1 (this seem not to be the nightly?)

### Additional Context

When opening a new graph that i have just created in the desktop app, it downloads and syncs successfully. There might be an issue with existing graphs in the browser.

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.