Solution: FTP not fully working after updating password on Godaddy server

FileZilla, Find and Edit the Trusted TLS Certs file

Today I ran into another small FTP issue, weird and annoying for anyone who’s not that ‘techy’ (I am using FileZilla 3 on Windows 7).

What happened is I changed the password for an FTP account on a client’s Godaddy Linux Classic hosting account, when the password was updated I was able to log in and the directory listing was easily retrieved but I was not able to transfer any files between the server and my computer.

I searched for answers on Google and it returned FileZilla forums oldest threads suggesting a Registry Edit (run > regedit.ext), of course that did not work.

Background:

The FTP accounts I had previously saved in my FileZilla had the TLS Certificates trusted and saved already, by changing the password on the server, the Certificate changed and it was not ‘OK’ anymore, but the FTP Client (in my case FileZilla 3) did not ask for the new cert again as it already had the certificate for that site/server saved locally.

Removing the account and adding it again will not work, also simple uninstall would also not work as the ‘config/settings/preferences’ files are kept on the computer even after uninstall.

Solution:

There is a file named ‘trustedcerts.xml’ which contains all the trusted TLS Certificates you have saved for your ease from previous sessions, you have to edit this file (see screenshot below).

On my Windows 7 setup, this file is located in:
C:\Users\<user-name>\AppData\Roaming\FileZilla

Note: Replace C: with your default Windows drive and <user-name> with the Windows user you’re accessing the computer with.

Ediding FileZilla 3, Trusted Certs XML file
Ediding FileZilla 3, Trusted Certs XML file – Click/Tap screenshot to load high-res version in new tab.

Caution: You need to select the proper tags for the proper ‘domain/IP’ for deletion as we can see in the above screen grab of the ‘trustedcerts.xml’ file.

Select the tag:

<Certificate> ......2b687474703a2f2f6
6f6d2f736669673273312d38312e63726c30630603551d20045c305
303d06082b060105050702011631687474703a2f2f6365727469666
46563682e636f6d2f7265706f7369746f72792... </Certificate>

And anything in between and press ‘Del’ on the keyboard, press CTRL+S to save the file, go back to the FTP Client/FileZilla and re-connect to the website/server, you should get the prompt to again accept the TLS Certificate, accept it and you’re good to go.

You can post your questions/comments below.

 

Get Docker Toolbox installed on Windows 7 – Run your first command

Docker Toolbox installed on Windows 7

After setting up my Win 7 Ultimate PC for virtualization with the combination of hardware-software jujitsu I was ready to install ‘Docker Toolbox’ as ‘Docker for Windows’ needs at least Windows 10 Pro.

The limitation is placed since Windows 7 is not equipped with a native Hyper-V (Hypervisor) technology.

You can download Docker Toolbox here and install on your computer using the detailed instructions found on the page.

Done with the installation? Now you have a tool you can use for your web development needs like an Apache / Nginx localhost server and several other apps you can see in the Kitematic GUI installed with the toolbox package.

When you have the whole app installed you will need to run the ‘Docker Quickstart Terminal’ (icon found on Desktop/Quickstart Menu) and you’ll have a command-line tool (bash) at your service.

The first command you’ll want to type would be the famous hello-world thingy but you need to follow the following syntax for that;

docker container run hello-world

The program will download the hello-world image (pre-packaged working stuff) since it’s the first time and it’s not present locally — hello-world now tells you if everything installed is functioning correctly. Your terminal window should look like below;

Docker Terminal in response to hello-world command
Docker Terminal in response to hello-world command (click image to open full-size in new tab)

Ok we are close to setting up our Local Apache Server for testing our web dev stuff closer to the production environment. I will post that command in my next post.

If you’re in a hurry you can join this free course at Code School for learning the basics of Docker/Docker Toolbox.

What’s this all about?

Coding Life

Hi,

I am Iqtidar Ali a front-end developer since the HTML 4.0 and Macromedia Flash 4 (later Adobe Flash) days of the web.

Every now and then we run into several issues while working on projects small to large — even while learning new stuff — so I thought of creating this blog as a public diary where I could post how I got the problems solved and sometimes my thoughts on the dev and tech in general.

This should be helpful for me and other devs in-case we run into a similar problem in future, we’ll just copy paste the solution 🙂

Thanks for reading, hope it makes sense.

Enabling Virtualization on Windows 7 machine when only enabling from BIOS isn’t working

Enable Virtualization - Windows 7

Today I sat on the mission to install ‘Docker’ on my Win 7 laptop and for that I had to enable Virtualization on my machine.

The simplest quick solution is that ‘if’ you already don’t have Virtualization enabled in BIOS, you need to just Restart your computer and press F2* (Dell) at the start screen > go to Advanced tab > select Virtualization > Enable > Press F10 to save and Enter to select ‘Yes’ > Exit this is what’s required for solving the ‘Hardware’ part of the problem.

But after doing this I again checked if the ‘Virtualization’ is enabled by using Microsoft’s ‘Hardware Accelerated Virtualization Detection Tool (click to download from MS site)

If the detection tool tells you it’s installed ‘hurrayyyy’ otherwise still don’t worry, you need to download ‘Windows Virtual PC’ from the MS website, Install it, restart the system, run the detection tool again and it should solve the problem.

I was able to find the correct solution from Tom’s Hardware website’s this thread. You can post a question to the above thread just in-case the problem is still not solved.

* Depending on your manufacturer the button to enter BIOS setup can be F2, Del or different, please refer to manufacturer guide or search online for the exact key for your specific brand or product.