Anki self-sync server: A network error has occured

101 views
Skip to first unread message

Lyubomir

unread,
Jul 25, 2023, 8:34:52 AM7/25/23
to AnkiDroid
Hello, i have deployed a self-sync server. The requests are getting to the server and i see the following:
INFO request{uri="/sync/meta" ip="10.14
INFO request{uri="/sync/meta" ip="10.14
INFO request{uri="/msync/begin" ip="10.
INFO request{uri="/sync/meta" ip="10.14
INFO request{uri="/sync/sync/hostKey"}:
INFO request{uri="/sync/sync/hostKey"}:
INFO request{uri="/sync/sync/hostKey"}:
INFO request{uri="/sync/sync/hostKey"}:
INFO request{uri="/sync/sync/hostKey"}:
INFO request{uri="/sync/sync/hostKey"}:

My settings are:

Why /sync/sync twice?

Lyubomir

unread,
Jul 27, 2023, 1:18:33 PM7/27/23
to AnkiDroid
I want to ask if this is considered an AnkiDroid bug or a bug in the parent Anki project's documentation?
Current text is as follows:

Older desktop clients required you to define SYNC_ENDPOINT and SYNC_ENDPOINT_MEDIA. If using an older client, you'd put it as e.g. http://192.168.1.200:8080/sync/ and http://192.168.1.200:8080/msync/ respectively. AnkiDroid also currently requires separate configuration for the two endpoints.

Minami Hasaki

unread,
Jul 31, 2023, 4:49:03 PM7/31/23
to AnkiDroid
The documentation seems correct. I think maybe you might have misinterpreted. The first paragraph under Client Setup and the instructions under Reverse Proxies seem to provide the necessary information that
the URL should have been either https:IPADDRESS:PORT, or in your case with a domain/subdomain https://DOMAIN.NAME. SYNC_ENDPOINT (/sync/) and SYNC_ENDPOINT_MEDIA (/msync/) should only be used for older clients, though that does sound very vague. I would suggest either opening a issue or PR here asking for or adding a version number requirement to specify what is considered an older client.
Reply all
Reply to author
Forward
0 new messages