Desktop Sync client does not sync with different transport port

Hi all,

I’ve deployed the Seafile 8 in Ubuntu 20, all seems fine. I’ve changed the transfer port from 8082 to 8083 as the 8082 is being used by another server. For the moment, web interface is able to upload/download files properly.

I’ve not configured any reverse proxy.

i’ve configured the Seafile sync client in the same network, so no NAT nor firewall between them, and it is able to see the libraries and documents, but when I try to sync it, I got these messages in the log:

[04/16/22 22:26:36] Bad response code for GET http:// localIP:8000/seafhttp/protocol-version: 404.
[04/16/22 22:26:38] libcurl failed to GET http:// localIP:8082/protocol-version: Couldn’t connect to server.
[04/16/22 22:26:38] Transition clone state for 832f14cb from [check server] to [error]: Cannot connect to server.
[04/16/22 22:26:41] Transition clone state for 832f14cb from [error] to [check server].
[04/16/22 22:26:41] Bad response code for GET http:// localIP:8000/seafhttp/protocol-version: 404.
[04/16/22 22:26:43] libcurl failed to GET http:// localIP:8082/protocol-version: Couldn’t connect to server.
[04/16/22 22:26:43] Transition clone state for 832f14cb from [check server] to [error]: Cannot connect to server.

It is still trying to use the 8082 instead of 8083 configured in the server. May I need to do something extra in the scync client?

Thanks

In the folder /opt/seafile/logs/seahub.log I can see thousands of lines like

2022-04-18 17:00:50,416 [WARNING] django.request:222 log_response Not Found: /seafhttp/protocol-version

Maybe it can be helpfull.

Thanks

The port 8082 is fixed, you can’t change it.If you want to use other port, you’d better setup nginx before seafile.