Seafile client unable to sync with changed port

Hello!

I have set up a Seafile environment as per this guide. https://manual.seafile.com/deploy/using_sqlite.html For some reason my router refuses to port forward port 8082. In the script setup-seafile.sh i changed this to port 8085, rest of the settings are left as default. When logging in to Seahub I’m able to upload files, and create a new library. I have also checked that both port 8000 and 8085 is available with the command; telnet my-domain port (as i found in the wiki) Both those requests are successful.

Problem is that the Linux client doesn’t seem to use this port. (seafile-gui with APT under ubuntu) After installing i followed the setup and successfully logged in to the service, but i could not send or receive files. In the logs it says the following over and over.

Client log from /home/user/.ccnet/logs/seafile.log
[01/14/18 19:42:02] seaf-daemon.c(558): starting seafile client 6.1.0
[01/14/18 19:42:02] ../common/mq-mgr.c(60): [mq client] mq cilent is started
[01/14/18 19:42:02] ../common/mq-mgr.c(106): [mq mgr] publish to heartbeat mq: seafile.heartbeat
[01/14/18 19:43:18] clone-mgr.c(840): Transition clone state for aa4e076f from [init] to [check server].
[01/14/18 19:43:18] http-tx-mgr.c(1236): Bad response code for GET http://my-domain.example:8000/seafhttp/protocol-version: 404.
[01/14/18 19:43:18] http-tx-mgr.c(771): libcurl failed to GET http://my-domain.example:8082/protocol-version: Couldn't connect to server.
[01/14/18 19:43:18] clone-mgr.c(857): Transition clone state for aa4e076f from [check server] to [error]: check server.
[01/14/18 19:43:22] clone-mgr.c(840): Transition clone state for aa4e076f from [error] to [check server].
[01/14/18 19:43:22] http-tx-mgr.c(1236): Bad response code for GET http://my-domain.example:8000/seafhttp/protocol-version: 404.
[01/14/18 19:43:22] http-tx-mgr.c(771): libcurl failed to GET http://my-domain.example:8082/protocol-version: Couldn't connect to server.
[01/14/18 19:43:22] clone-mgr.c(857): Transition clone state for aa4e076f from [check server] to [error]: check server.
[01/14/18 19:43:27] clone-mgr.c(840): Transition clone state for aa4e076f from [error] to [check server].
[01/14/18 19:43:27] http-tx-mgr.c(1236): Bad response code for GET http://my-domain.example:8000/seafhttp/protocol-version: 404.
[01/14/18 19:43:27] http-tx-mgr.c(771): libcurl failed to GET http://my-domain.example:8082/protocol-version: Couldn't connect to server.
[01/14/18 19:43:27] clone-mgr.c(857): Transition clone state for aa4e076f from [check server] to [error]: check server.
[01/14/18 19:43:32] clone-mgr.c(840): Transition clone state for aa4e076f from [error] to [check server].

After some googling i cannot find any solid answers to this issue. Neither am i able to locate a config file where i can manually change the port. Is there something I’m missing, or is this a bug? Please ask if you need more information.

Thank you for your time.
Kad

Please setup a local reverse proxy on the server. Way less complicated and more secure.

Thank you for your quick reply.

Is there any documentation in how to do that?

https://manual.seafile.com/deploy/deploy_with_nginx.html

This server manual is not nice if one is new to Unix/Linux. But this should get you sorted. If you don’t need a valid certificate, at least setup a self-signed certificate. I don’t know why they removed the part for self-signed certs. (not nice!)

https://manual.seafile.com/deploy/https_with_nginx.html

Thank you for the link.

I’m not new to Linux, i have experience with Linux environments from my work.
Also is there any significant advantage or disadvantage over choosing Nginx over Apache for Seafile?

Not really. Nginx is more lightweight than apache.