I believe this bug is purely with the portable version not the normal filezilla 3.2.3.1. When initially installed the directory name is INSTALL_PATH\FileZillaPortable and everything appears to work fine. If you rename FileZillaPortable to something even as simple as FileZillaPortable2 the program will not connect to ftp sites.
If a dns is used to connect to the ftp site you get this error:
Status: Resolving address of ftp.XXX.com
Status: Connection attempt failed with "EAI_NONAME - Neither nodename nor servname provided, or not known".
Error: Could not connect to server
If you use an IP to connect you get this different error:
Status: Connecting to XXX.XXX.XXX.XXX:21...
Status: Connection attempt failed with "WSAENETDOWN - System's network subsystem has failed".
Error: Could not connect to server
If you exit out and rename FileZillaPortable2 back to FileZillaPortable it works fine.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
... the Appfolder.
Delete Data\settings\filezilla.xml befor starting Filezilla.
Filezilla stores the settings (also the path to the executables) at the end of the session).
BTW: Install Filezilla local an rename the installation folder, the local version will not like it
Paid for Software more or less?
What You need is OSS!
Thanks for the reply. Unfortunately that didn't work. I deleted the file and tried it again with the exact same error. I also noticed that if I rename the FileZillaPortable2 to another name filezilla.xml will automatically update line 17 even without being deleted. Any area that might be causing this hiccup?
I have changed the Name to FileZillaPortable2, start it (second ask from Firewall if FilezillaPortable in the new folder is allowed to connect) no problems to connect.
Please check if Your firewall blocks the "new" App because of the changed folder
Paid for Software more or less?
What You need is OSS!