I’ve been using Seafile for about 6 months now, but I’m not able to use the Seafile Windows Client to sync any folders. I can upload and download files individually through the client and from the browser.
My Seafile server is setup on a Linux (Centos 7) machine, and I only have clients on my local LAN network attached to it. The seafile server is also not behind a Nginx/Apache server.
The errors on my Windows client are:
[07/07/19 01:57:21] clone-mgr.c(718): Transition clone state for cd348f5f from [init] to [check server].
[07/07/19 01:57:21] http-tx-mgr.c(1285): Bad response code for GET http://mydomain.com:3010/seafhttp/protocol-version: 404.
[07/07/19 01:57:31] http-tx-mgr.c(808): libcurl failed to GET http://mydomain.com:8082/protocol-version: Couldn’t connect to server.
[07/07/19 01:57:31] clone-mgr.c(735): Transition clone state for 730b2086 from [check server] to [error]: check server.
[07/07/19 01:57:34] clone-mgr.c(718): Transition clone state for 730b2086 from [error] to [check server].
[07/07/19 01:57:35] http-tx-mgr.c(1285): Bad response code for GET http://mydomain.com:3010/seafhttp/protocol-version: 404.
The errors from my server include these:
2019-07-07 09:00:33,932 [WARNING] django.request:152 get_response Not Found: /seafhttp/protocol-version
2019-07-07 09:00:38,916 [WARNING] django.request:152 get_response Not Found: /seafhttp/protocol-version
I have tried this on versions 6.3.4 and 7.0.3 for the Linux Seafile server, and 7.0.0 of the Windows client.
I know in previous versions it mentioned that I should leave the File Server Root blank if I am not behind a Nginx/Apache server, but that is apparently not allowed any more
I do notice my client trying to access the server through port 3011 and 8082, which is an issue for sure. I’m just not sure how to resolve this.
Can anyone offer me any suggestions?