Transport Error on Windows Client

windows

#1

Hello,

i have got a Problem with one of my windows-clients.

after i set up an new seafile server with the latest version, erverything worked fine.
All clients (2 android, 2 windows (7 and 10), 1 ubuntu and 1 ios) downloading and syncing their own and shared folders.

But today, the windows10 client of one account/user refuses to sync all folders with the following error:

when this account creates a new libary, it shows up in the client, but it doesn’t sync to the server.

modifications in shared libs from other clients where shown in the status of the folder, but a sync/download is not possible.

the mobile-client (android) from this account also didn’t syc/open his files.

all other clients/accounts working correct.

This windows10 - client also installed the newest windows-updates today, maybe this is the cause, but i undo the update to the last saving point, but this also didn’t help.

it’s pretty much the same behavior like in this topic, but the solution (enable fastcgi) doens’t help:

*Update:
Here are some log-entries from the applet.log on the wwin10 client:

[12/21/17 18:45:52]Download konnte nicht eingerichtet werden:
Transport Error
[12/21/17 18:45:52][Sea RPC] Bad response: 102 processor is dead.
[12/21/17 18:45:52][Sea RPC] Bad response: 102 processor is dead.
[12/21/17 18:45:52][Sea RPC] Bad response: 102 processor is dead.
[12/21/17 18:45:52][Sea RPC] Bad response: 102 processor is dead.
[12/21/17 18:45:52][Sea RPC] Bad response: 102 processor is dead.
[12/21/17 18:45:52]failed to get repo list: Transport Error

[12/21/17 18:46:54][RPC] failed to start rpc server: 511 Unknown service.
[12/21/17 18:46:54]failed to get repo list: Transport Error

By search over google for the RPC-entrie, i get some results, that points to older github messages, with this problem

I figured out, that i can share libs from the effected user with others… they’re able to download/syc the files from the broken account. -.-"

Any ideas?

Regards,

Sv_en


#2

Same issue, unable to solve as of now


#3

It looks like that I am facing to the same Transport Error on Windows 10 client.


#4

We have the same issue with a Linux client (6.1.8) with current seafile server (6.3.3).