I know that message. It’s indeed not from Filestash, it’s from our FTP server. Our server has quite aggressive inactivity timeouts and will kill the connection after only 20 seconds of inactivity. If Filestash just sets up an FTP connection once and keeps it open across requests, you would run into that.
And I’ve also seen in the past that trying to write files over an FTP connection that has already timed out may result in empty files being stored.
So I think both issues are caused by improper handling of closed connections. But I can’t say I know enough about the intricacies of FTP to know this for sure or how to solve it.
I’m surprised all of you got that far though. I tried it myself yesterday from the Docker image but couldn’t connect due to a TLS error. I know that issue is also on us, but not having an ability to disable TLS was a bummer.
I didn’t know about Filestahs before and after taking a close look, I do like the concept! Most web based file managers use PHP backends, which is an extremely poor choice because the PHP FTP module is terrible and PHP in general isn’t efficient with IO, so having a backend written in Golang could be really good!