Shared folders missing after reboot of server - restart service and they are back

[david.sain]

I have a server that has a management agent on it from our platform (Kaseya). After system updates are pushed, servers are rebooted early Sunday morning. This server has Filezilla Server 0.9.59 Beta.

After the server is rebooted automatically, the Filezilla server is inaccessible by a vendor. Once the server has been rebooted again, it seems to work fine.

I looked at Filezilla's configuration after I had restarted the server. Looked at the ports and made certain nothing was contending for port 21. Started looking at the vendor application only to discover it's not related - the file comes from their location over the internet.

Then I looked at the configuration prior to a manual restart of the server or service. I created a test user and was warned that there was no shared folder - Something as if the folder needed to exist before I could create the user. Looking at that tab, there is nothing in the path.

Restarted the Filezilla Server SERVICE only. Opened the application and the folder is now available.

I looked in the server log and see NO errors. In fact, everything looks perfect. I searched and only found something that turned out to be network related (involving targeting a NAS). The folder path here is local (C:\FTP).

I'm just taking over management of this server and the previous admin just manually rebooted each week instead of looking into the root of the issue. I'm hoping this is the root - I see 0.9.60.2 is available. It's not a beta so perhaps it will address this? Can I install it over the top of the beta?

Thanks for any input.
David

[botg]

Which Windows version are you using?

[boco]

I see 0.9.60.2 is available. It's not a beta so perhaps it will address this?

All FileZilla Server versions are betas. 0.9.60.2 is no exception.