So Seafile has started to become a massive pain in my backside for me, nothing against the developers, but out of nowhere, the whole infrastructure just implodes and it stops working for some reason.
As of last night, my server stopped connecting clients, and no libraries or files can be accessed through already logged in ones. When logging in through a browser, the only place a logout and login works now, since logging in through the Windows client itself responds with “Failed to login, internal server error,” will simply kick out “Error.” No libraries, no files, no anything. Despite it working the night before. No config files have been changed with Seafile, I have it running as a Windows Service in the background, the only thing that has happened since last night was a Windows Virus scan that detected and deleted nothing, and a Malwarebytes Virus scan that did the same.
My only working theory is that port 13001, the port setup for “Client” in the ccnet config file, is being blocked. Which wouldn’t make sense, given that I’m forcing it open through my router. Yet it remains closed on my system when checked through websites that do so. The all-critical 8000 and 8082 ports are open however. Even changing 13001 to a known open port, in this case, 32400, did nothing to solve the problem.
The thing that’s angering me the most, is that it does this out of nowhere, seemingly breaking at random times where the server hasn’t been touched in several days. Everything else I push through my server is still up, Minecraft Server, Back-end website, PleX server, making Seafile the only one that spontaneously breaks.
The usual suspect of this issue, Windows Firewall, isn’t doing it either. So I’m at a loss. A pretty big one.