I am using the Seafile Client to access my private Seafile cloud, which my university provides me with, and to use the team Seafile cloud of the institute I work for. Therefore, I have two different accounts, which have been running simultaneously without any problems so far. However, I noticed that since yesterday, whenever I switch between profiles in my client, the synced folders are automatically unsynced. I tried everything from rebooting, logging out and in again, reinstalling the client — none of that helped. Now I’m driving my colleagues nuts (who do not experience the same issues) by creating SFConflict-files every time I try to resync my folders. Is it possible, that the “Auto unsync libraries that has no permission” function, that came with update 9.0.9 causes the problem? As far as I know, I haven’t lost any permissions, since this problem only occurs on my Windows Desktop PC but not on my Windows Laptop.
EDIT: I just noticed that the client on my Windows laptop is actually still 9.0.7. I was able to download and install the 9.0.7 from your website, and now everything works fine on my Windows desktop PC as well. Maybe the 9.0.9 update for the Windows client should also be withdrawn, as was done with the Mac client update. I imagine I’m not the only one with such problems.
This is still happening for me in 9.0.10 on Windows. All full libraries that I enabled sync for on this machine are working, only selectively synced libraries (i.e. only a sub-folder of a library is being synced to this machine) fail and get removed as soon as I restart the client.
I did. Installed 9.0.10 for Windows, selective syncs were gone again. Added them again. Restarted the client, some are still visible, but not synced (empty cloud beside it). Refreshing with the button up top inside the client removes even those from the ‘synced’ section. I can reproduce it all the time.
Can confirm from two different Windows systems syncing different sub-folders (to the same Seafile installation though), just tried it out on 9.0.10. Still happening as described above.
I have a homenetwork, with two devices running different seafile servers. I acquired a new Raspberry PI and kept the old server running, for migration.
The old device runs Server Version 10.0.1, the new device runs 12.0.14. Both use HTTPS, routing is done via Ports. Thus, the old device has the domain https://seafile.mydomain.com:8050, while the new device has the domain https://seafile.mydomain.com:8060. Port forwarding in the router is configured accordingly.
Also, for both I use accounts with the same EMail address. Passwords are different, and so are HTTPS certificates, as both were requested on device via let-s encrypt. Both servers are online and fully functional, though I suspect the seafile clinet perhaps could be confused by identical user names and domains (except for the port suffix!).
On multiple devices, i was logged into the old server. Using Seafile Client 9.0.14 on Windows, I can connect to both, but if I switch between accounts, all libraries are always unsynced. This is true for fully synced libraries as well as for libraries where I just started the synchronisation process.
The problems occurs, as far as I can tell, always. I can resync libraries, but as soon as I switch between accounts they are unsynced again.
On one device, I still have Client version 9.0.2. installed. Again, I can log into both servers, and everything looks good, and switching accounts works as intended - nothing is unsynced.
The current sync client does not support handling servers that have the same host but different ports. By default, the client assumes that different services use different hosts.
When the host is the same but the ports differ, the client cannot distinguish which server a library belongs to, which leads to this issue.
Currently, you can resolve this by modifying the configuration so that the two servers use different hosts.
I see, I suppose the client then looks for a library from server A on server B, cannot find it, assumes it was removed and auto unsyncs.
For the next release, I propose to at least implement an error message, when the user tries to add accounts like this. Software should never silently fail. Unsyncing is relatively harmless, for now, but such kind of error could also lead to corrupting libraries on the server, which could be more catastrophic.
Ideally, of course, one would go back to the previous implementation and drop the wrong assumption, that different servers have different “domains” (with which I mean the front part of the URL that does not include the port).
For my situation, it is a bit tricky, since I have a DynDNS configuration and such, so really, devices in my network can only be distinguished by port (which, honestly, should be a perfectly ok situation). I can try to drop HTTPS and connect via local IP address, as long as the client is inside the same network, which is ok, sine running two servers is really only for the migration period.
In conclusion, it would be a good feature to support again, but the larger issue to me is, to allow the user without any complaint to do something that can never work.
Thank you for your support and for developing seafile, I am generally quite happy with it
I am seeing this issue as well after having changed from client 9.0.13 from the Debian package sources to client 9.0.14 as AppImage. I am on Debian 13 and I am accessing one server with different accounts.
