KOReader plugin Connection failed (code -5): Connect timed out after 10 secs

[pdc1]

I am thrilled to see a KOReader plugin for Crosspoint-Sync! I can finally get my clippings :)

However, it's not currently working (version 0.2.7). I do have a private CA, and I did add it to the latest cacert.pem, and copied it back to the plugin directory. I restarted KOReader.

I double-checked the URL and credentials are correct. I tried using cacert.pem with a local curl command and it appeared to work. Also, the regular progress sync works, just not the Crosspoint sync.

Is there something else I can do to troubleshoot?

Here are the logs from KOReader:

[...]
ffi.load: rt
�[33m[W 2026/11/14 10:42:27] _G.__TURBO_USE_LUASOCKET__ set, using LuaSocket (degraded performance).�[0m
ffi.findlib: tffi_wrap
ffi.load: libs/libtffi_wrap.so
ffi.findlib: ssl [60]
ffi.load: libs/libssl.so.60
�[33m[W 2026/11/14 10:42:37] [async.lua] Connect timed out after 10 secs. POST koreader-sync.home/api/v1/stats/koreader�[0m
�[31m[E 2026/11/14 10:42:37] [async.lua] Error code -5. Connect timed out after 10 secs�[0m
[...]

I don't see any logs for this on the server, is there some way to increase default logging levels in the crosspoint-sync container?

[pdc1]

BTW, I have roughly 200 books in KOReader, in case that might be causing the timeout?

[itsthisjustin]

BTW, I have roughly 200 books in KOReader, in case that might be causing the timeout?

Try the latest one I just published

[pdc1]

Now I get <book title>: Server returned 404. Check your account and server version.

The logs show:
�[33m[W 2026/11/14 11:49:19] [async.lua] POST koreader-sync.home:443/api/v1/stats/koreader => 404 Not Found 93ms�[0m

I am also seeing 404 errors from CrossInk when updating stats, but I thought that was something with rc2. I have a caddy reverse proxy in place, but I don't see errors in the caddy logs, and other APIs are working from my desktop:

> curl -sS https://koreader-sync.home:443/api/v1/progress \
             -H "x-auth-user: pdc1" -H "x-auth-key: [redacted]" | jq | head
{
  "next": null,
  "items": [
    {
      "document": "38e882a70a2d60454207dc2dbeed6c39",
      "history_only": false,
      [...]

[itsthisjustin]

You're self hosting right? You're on the latest version of the server?