I’m really careful about upgrades.
My enterprise IT experience shouts at me each time I want to upgrade anything. Thankfully, consumer software is more resilient and provides an overall better upgrade experience. Nonetheless, it is better to be careful than sorry 🙂
So this fine day, It was with some premonition I clicked the upgrade button when FileZilla asked me while starting up. As most of the web junkies understand, FTP is an integral part of a website. And what better tool for FTP other than FileZilla, the free and open source tool that has been there for us since forever.
Alas, this particular upgrade was not that seamless an experience.
Immediately after upgrade to FileZilla version 3.10.1, I could not connect to any of my websites on BlueHost.
The error –
The error says –
Response: 200 TYPE is now 8-bit binary Command: PASV Response: 227 Entering Passive Mode (69,195,124,162,124,79) Command: MLSD Error: Connection timed out Error: Failed to retrieve directory listing
I did not get an answer directly to this problem elsewhere. But eventually found an answer when I compared settings with the older version. Although none of my settings changed, FileZilla itself changed keeping all of our best interests in mind.
In FileZilla: go to File > Site Manager.
In “General” tab, the “Encryption” field was set to a different value as compared to the older version. I changed the value back to “Only use plain FTP” to get it working again.
I can very well understand the reason for the change by the FileZilla team. FTP is basically insecure, and any kind of encryption helps. Using SSH FTP or using TLS is the way forward.
At the same time, this way of changing a default configuration value is worrisome. I had tens of websites and I could easily change the configuration as required. But I can very well imagine the plight of people having hundreds of websites saved in FileZilla.
The future is of course secure FTP. I’m trying to migrate my BlueHost FTP accounts towards using TLS.