Notifications
Clear all
Topic starter
Hi
I spent some time solving this...
Symptom : Seafile crash with a popup "seafile closed unexpectedly"
Cause : the seaf-daemon is unable to start because it can't get and IP and thus open a socket
Fix : If you use advanced network configuration, Seafile won't start unless you apply an exception to Seafile folder.
For seadrive :
Symptom : drive is mounted but can't be opened
Cause : almost the same, seaf_pipe failed to connect socket: 10049
Fix : apply and exception to Seadrive folder
My 0.02€
Posted : 28/12/2018 6:37 pm
I have found that the IP assignment generally causes more problems. Thus, I've changed it to be a whitelist rather than a blacklist. (Apply only to these programs) I find that this is much more compatible with most applications. (including browsing)
Posted : 30/12/2018 7:26 am
