Not sure why it is not syncing :( How to force push to server?

[gerroon]

I was able to set this up with the help from @vrtmrz using Docker and Apache. I can get the test connection work. I am unable to sync, not sure what the issue might be.

The data folder of the CD is just 64k after the sync. Do I need to have multiple sync points set up and running at the same time? Maybe CD server does not store any sync files?

Docker on Debian, Obsidian 1.4.13 on Windows 11

11/14/2023, 11:00:18 AM->Hidden files scanned: 0 files had been modified
11/14/2023, 11:01:05 AM->Connected to https://DOMAIN.com/obsidiansync
11/14/2023, 11:01:29 AM->Before LiveSync, start OneShot once...
11/14/2023, 11:01:29 AM->OneShot Sync begin... (pullOnly)
11/14/2023, 11:01:40 AM->Before LiveSync, start OneShot once...
11/14/2023, 11:01:40 AM->OneShot Sync begin... (pullOnly)
11/14/2023, 11:01:51 AM->Before LiveSync, start OneShot once...
11/14/2023, 11:01:51 AM->OneShot Sync begin... (pullOnly)
11/14/2023, 11:02:06 AM->Counting remote database
11/14/2023, 11:02:06 AM->Database active-size: -, external-size:-, file-size: -
11/14/2023, 11:02:06 AM->Collecting unreferenced chunks on https://DOMAIN.com/obsidiansync
11/14/2023, 11:02:07 AM->Failed to make design document for operating chunks
11/14/2023, 11:02:07 AM->Could not prepare design document for operating chunks
11/14/2023, 11:02:42 AM->LiveSync Disabled.
11/14/2023, 11:03:04 AM->LiveSync Enabled.
11/14/2023, 11:03:04 AM->Before LiveSync, start OneShot once...
11/14/2023, 11:03:04 AM->OneShot Sync begin... (pullOnly)
11/14/2023, 11:03:06 AM->Before LiveSync, start OneShot once...
11/14/2023, 11:03:06 AM->OneShot Sync begin... (pullOnly)

Server log

obsidian-livesync | [notice] 2023-11-14T16:58:06.793466Z nonode@nohost <0.8941.0> ea349190ec DOMAIN.com 192.168.100.2 admin GET / 200 ok 1
obsidian-livesync | [notice] 2023-11-14T16:58:06.797914Z nonode@nohost <0.8941.0> 4301f3c015 DOMAIN.com 192.168.100.2 admin GET / 200 ok 1
obsidian-livesync | [notice] 2023-11-14T16:58:06.802306Z nonode@nohost <0.8941.0> f0c7de2b04 DOMAIN.com 192.168.100.2 admin GET /_design/replicate? 404 ok 1
obsidian-livesync | [notice] 2023-11-14T16:58:06.806731Z nonode@nohost <0.8941.0> 24ffb87679 DOMAIN.com 192.168.100.2 admin PUT /_design/replicate 404 ok 1
obsidian-livesync | [notice] 2023-11-14T16:58:08.799949Z nonode@nohost <0.8966.0> b7ea20b6cc DOMAIN.com 192.168.100.2 admin GET / 200 ok 1
obsidian-livesync | [notice] 2023-11-14T16:58:08.806504Z nonode@nohost <0.8966.0> a3205b7684 DOMAIN.com 192.168.100.2 admin GET / 200 ok 1
obsidian-livesync | [notice] 2023-11-14T16:58:08.811191Z nonode@nohost <0.8966.0> f679eaf27c DOMAIN.com 192.168.100.2 admin GET /_design/replicate? 404 ok 1
obsidian-livesync | [notice] 2023-11-14T16:58:08.816207Z nonode@nohost <0.8966.0> e0812f30ab DOMAIN.com 192.168.100.2 admin PUT /_design/replicate 404 ok 1
obsidian-livesync | [notice] 2023-11-14T17:01:11.262345Z nonode@nohost <0.10454.0> be07124295 DOMAIN.com 192.168.100.2 admin GET / 200 ok 1
obsidian-livesync | [notice] 2023-11-14T17:01:11.266790Z nonode@nohost <0.10454.0> 17256e881d DOMAIN.com 192.168.100.2 admin GET / 200 ok 1
obsidian-livesync | [notice] 2023-11-14T17:01:11.272491Z nonode@nohost <0.10454.0> e90269e006 DOMAIN.com 192.168.100.2 admin GET /_design/replicate? 404 ok 2
obsidian-livesync | [notice] 2023-11-14T17:01:11.276586Z nonode@nohost <0.10454.0> 0f5ee81fe4 DOMAIN.com 192.168.100.2 admin PUT /_design/replicate 404 ok 1
obsidian-livesync | [notice] 2023-11-14T17:01:42.475784Z nonode@nohost <0.10726.0> 8ee2fc9bb6 DOMAIN.com 192.168.100.2 admin GET / 200 ok 1
obsidian-livesync | [notice] 2023-11-14T17:01:42.482393Z nonode@nohost <0.10726.0> ac91d2ab91 DOMAIN.com 192.168.100.2 admin GET / 200 ok 1
obsidian-livesync | [notice] 2023-11-14T17:01:42.488802Z nonode@nohost <0.10726.0> d3731f6826 DOMAIN.com 192.168.100.2 admin GET /_design/replicate? 404 ok 1
obsidian-livesync | [notice] 2023-11-14T17:01:42.493352Z nonode@nohost <0.10726.0> 3e06ea7b4c DOMAIN.com 192.168.100.2 admin PUT /_design/replicate 404 ok 1
obsidian-livesync | [notice] 2023-11-14T17:01:55.416298Z nonode@nohost <0.10834.0> 771e526f60 DOMAIN.com 192.168.100.2 admin GET / 200 ok 1
obsidian-livesync | [notice] 2023-11-14T17:01:55.421928Z nonode@nohost <0.10834.0> 0231e3d582 DOMAIN.com 192.168.100.2 admin GET / 200 ok 1
obsidian-livesync | [notice] 2023-11-14T17:01:55.426495Z nonode@nohost <0.10834.0> 12f6b0ba48 DOMAIN.com 192.168.100.2 admin GET /_design/replicate? 404 ok 1
obsidian-livesync | [notice] 2023-11-14T17:01:55.431090Z nonode@nohost <0.10834.0> e042218410 DOMAIN.com 192.168.100.2 admin PUT /_design/replicate 404 ok 1

[gerroon]

@vrtmrz Any ideas why this fails or not syncs?
docker-compose

version: "2.1"
services:
  couchdb:
    image: couchdb
    container_name: obsidian-livesync
    user: 1000:1000
    environment:
      - COUCHDB_USER=admin
      - COUCHDB_PASSWORD=xxxxxxxxx
    volumes:
      - /media/obsidian_livesync/data:/opt/couchdb/data
      - ./local.ini:/opt/couchdb/etc/local.ini
    ports:
      - 5984:5984
    restart: unless-stopped

local.ini

[couchdb]
single_node=true
max_document_size = 50000000

[chttpd]
require_valid_user = true
max_http_request_size = 4294967296
enable_cors = true

[chttpd_auth]
require_valid_user = true
authentication_redirect = /_utils/session.html

[httpd]
WWW-Authenticate = Basic realm="couchdb"
bind_address = 0.0.0.0

[cors]
origins = app://obsidian.md, capacitor://localhost, http://localhost, https://MYDOMAIN.com
credentials = true
headers = accept, authorization, content-type, origin, referer
methods = GET,PUT,POST,HEAD,DELETE
max_age = 3600

[techn0pia]

Similar configuration I did today.

I had to create a database via https://couchdb.home.arpa/_utils/#/_all_dbs first and enter it in the config.
Afterwards syncing worked 👍

[gerroon]

Thanks for the reply, but your link is not opening :(

[gerroon]

I see, now I got it. You are right, I am able to sync it after creating and linking the database. Thanks for the help