vrtmrz / obsidian-livesync

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

after last updates i have this error: TypeError: Failed to fetch

progressify opened this issue · comments

Expected behaviour

  • Synchronisation ends with the message Replication completed
  • Everything synchronised

Actually happened

  • Synchronisation has been cancelled with the message TypeError Failed to fetch
  • No files synchronised

Reproducing procedure

  1. Configure LiveSync as in the attached material.
  2. Click the replication button on the ribbon.
  3. Synchronising has begun.
  4. About two or three seconds later, we got the error TypeError Failed to fetch.
  5. Replication has been stopped. No files synchronised.

Plug-in log

image

Plug-in log
obsidian-progressify:22/3/2024, 18:48:38->OneShot Sync begin... (sync)
plugin:obsidian-livesync:23102     GET https://<URL db>/ net::ERR_CONNECTION_REFUSED
fetch @ plugin:obsidian-livesync:23102
ourFetch @ plugin:obsidian-livesync:9921
fetchJSON @ plugin:obsidian-livesync:9937
setup2 @ plugin:obsidian-livesync:9955
HttpPouch.o._info @ plugin:obsidian-livesync:10056
eval @ plugin:obsidian-livesync:7145
eval @ plugin:obsidian-livesync:5247
eval @ plugin:obsidian-livesync:5211
eval @ plugin:obsidian-livesync:5204
eval @ plugin:obsidian-livesync:5245
execute @ plugin:obsidian-livesync:7310
ready @ plugin:obsidian-livesync:7319
eval @ plugin:obsidian-livesync:7406
eval @ plugin:obsidian-livesync:9971
Item.run @ plugin:obsidian-livesync:1176
nextTick @ plugin:obsidian-livesync:1154
(anonymous) @ node:internal/process/task_queues:140
runInAsyncScope @ node:async_hooks:204
runMicrotask @ node:internal/process/task_queues:137
IndexedDB (async)
get @ plugin:obsidian-livesync:9106
eval @ plugin:obsidian-livesync:9743
Promise.then (async)
eval @ plugin:obsidian-livesync:9741
eval @ plugin:obsidian-livesync:7021
eval @ plugin:obsidian-livesync:5247
eval @ plugin:obsidian-livesync:5211
eval @ plugin:obsidian-livesync:5204
initializeDatabaseForReplication @ plugin:obsidian-livesync:20242
openReplication @ plugin:obsidian-livesync:20270
replicate @ plugin:obsidian-livesync:24246
await in replicate (async)
eval @ plugin:obsidian-livesync:23383
plugin:obsidian-livesync:23995 TypeError: Failed to fetch
    at fetch (plugin:obsidian-livesync:23102:27)
    at ourFetch (plugin:obsidian-livesync:9921:18)
    at fetchJSON (plugin:obsidian-livesync:9937:21)
    at setup2 (plugin:obsidian-livesync:9955:9)
    at HttpPouch.o._info (plugin:obsidian-livesync:10056:13)
    at klass.eval (plugin:obsidian-livesync:7145:12)
    at klass.eval (plugin:obsidian-livesync:5247:24)
    at eval (plugin:obsidian-livesync:5211:20)
    at new Promise (<anonymous>)
    at klass.eval (plugin:obsidian-livesync:5204:83)
    at eval (plugin:obsidian-livesync:5245:34)
    at TaskQueue.execute (plugin:obsidian-livesync:7310:107)
    at TaskQueue.ready (plugin:obsidian-livesync:7319:10)
    at eval (plugin:obsidian-livesync:7406:22)
    at eval (plugin:obsidian-livesync:9971:5)
    at Item.run (plugin:obsidian-livesync:1176:16)
    at nextTick (plugin:obsidian-livesync:1154:38)
    at node:internal/process/task_queues:140:7
    at AsyncResource.runInAsyncScope (node:async_hooks:204:9)
    at AsyncResource.runMicrotask (node:internal/process/task_queues:137:8)
plugin:obsidian-livesync:23997 obsidian-progressify:22/3/2024, 18:48:38->TypeError:Failed to fetch
plugin:obsidian-livesync:23997 obsidian-progressify:22/3/2024, 18:48:38->Could not connect to https://<URL db>: TypeError:Failed to fetch
**Note** This error caused by many reasons. The only sure thing is you didn't touch the server.
To check details, open inspector.
plugin:obsidian-livesync:23997 obsidian-progressify:22/3/2024, 18:48:38->Could not connect to server.

Screenshots

image

resolved!
probably it was an issue with my Traefik configuration.
After an update of Traefik and a restart of a CouchDB docker-compose it works perfectly

I have the same problem after last update. but I can't fix it by restart couchdb and traefik.

Apologies for the delay!
The Type Error when connecting remotely is a common one and we are not sure much about what the error actually is only from that.
Would you mind if I ask you to check the device logs, please?