Upgrading to 1.6.0 fails

Need help with FileZilla Server? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Post Reply
Message
Author
general_chaos
504 Command not implemented
Posts: 6
Joined: 2013-06-20 14:54

Upgrading to 1.6.0 fails

#1 Post by general_chaos » 2022-12-06 18:33

I've tried several times, but the upgrade to 1.6.0 fails on my server. A copy of the error dialog, and the install log, are attached.
After this happens, I can manually start the server and the GUI, but all of my settings are gone. I tried copying in the old xml configs from v1.5.1 into the directory 1.6.0 installs in, but it doesn't use them.

I noticed in the changelog for 1.6.0-rc1: the installer now offers to keep the existing service configuration of a previously installed FileZilla Server whose release must be above or equal to 1.6.0.
Are upgrades from 1.5.1 to 1.6.0 not supported?
Attachments
fz_upgrade_error.txt
(2.22 KiB) Downloaded 36 times
Screenshot 2022-12-06 132937.png
Screenshot 2022-12-06 132937.png (5.51 KiB) Viewed 818 times

User avatar
botg
Site Admin
Posts: 35508
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: Upgrading to 1.6.0 fails

#2 Post by botg » 2022-12-06 19:49

What happens if you restart the installation following a reboot?

general_chaos
504 Command not implemented
Posts: 6
Joined: 2013-06-20 14:54

Re: Upgrading to 1.6.0 fails

#3 Post by general_chaos » 2022-12-06 20:14

I just tested, and it works as expected if I try the install again after rebooting after the failure. THANK YOU!

I do notice that it warns me about passive mode and port forwarding, despite those already being configured from the previous install, but it's working, and my old settings are present:
Screenshot 2022-12-06 151230.png
Screenshot 2022-12-06 151230.png (19.84 KiB) Viewed 806 times

general_chaos
504 Command not implemented
Posts: 6
Joined: 2013-06-20 14:54

Re: Upgrading to 1.6.0 fails

#4 Post by general_chaos » 2022-12-06 21:47

I ran through the network configuration wizard, and this warning still appears after a reboot. Not a huge deal, but thought I should report.

Post Reply