In days gone by, people used to use file transfer protocol (FTP) to connect to their Web sites to copy files to and from their local computer.
With the rise of SSL for secure connections between browsers and Web sites, good old FTP is no longer considered secure and most (responsible) hosting companies no longer offer it.
The good news is there is a secure replacement for FTP, simply called SFTP, which uses a secure shell (SSH) connection to ensure all data is encrypted when transferring files.
SFTP is not as straightforward to setup as FTP, but once you’re there you can use a GUI client to easily shuffle files to your WordPress site. In this blog we will take a look at how to setup SFTP, from generating the keys to transferring files.
To use SFTP you need to have a set of keys. Digital keys combine to form a “match” to authenticate two machines and distinguish from imposters. We say “keys” because there is a private-public pair. Think of the difference this way:
By generating a pair of keys you will have a secure way of encrypting file transfers between you and your host.
When generating a key pair you will be doing the following, with slight variations depending on the client software:
On Windows you can use a free software package like Putty to generate a set of keys.
First, download the package from here: https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
Then install it using by double clicking the Windows installer file.
To generate a set of keys you will need to download puttygen.exe, which can be found here: https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
Open puttygen.exe. Select SSH as the type of key to generate and click Generate. You can then save your private and public keys. [Note: Putty “save public key” does not have a file type, it’s just a text file with no extension. Thoughts? Do they need to save it to a .pem file type?]
Most Linux distributions ship with a package like OpenSSH which can generate a key pair from the command line.
Run the command:
ssh-keygen –t rsa
You will be prompted to enter a location to save the private key. Choose a location (e.g. /home/user/ssh) and the public key will be saved in that location as well.
Next, type in a password at the prompt. If you leave this empty (just hit enter) there will be no password.
Mac OS X works much the same as Linux and you can generate a key pair from the terminal. Follow the Linux command line as above.
If you are unable to generate a key pair from a local machine, such as Chrome OS, all is not lost as you can try a Web application to generate them.
Services like JS Encrypt (https://travistidwell.com/jsencrypt/demo/) will generate a key pair you can download and use on any machine.
On Android there are a number of SSH clients such as JuiceSSH and Termux that will allow you to generate SSH keys.
As with Android, there are apps for iOS, such as ish.app, which allow you to generate a ssh key pair.
With your freshly minted keys ready to use, it’s time to send the public key to your WordPress hosting provider.
You can do this via email or with a web application. You public key will be saved in the provider’s authorised keys file allowing you to connect to your WordPress files folder securely.
Remember, keep your private key private and don’t sent it to anyone or misplace it.
With all the groundwork done, it’s time to fire up your favourite FTP client. So long as the client supports SFTP then the user experience will be essentially the same.
FileZilla is a great, free FTP and SFTP client for Windows, Linux and MacOS. To perform key-based authentication, navigate to Edit -> Settings and you will see the SFTP settings. Add your private key and you will be able to connect to the server which has your public key.
Add your private SSH key to FileZilla
Most Unix-like operating systems generally support the sftp command from the terminal, but how to use that is the topic of another blog.
If you’re confident using sftp on a command line, you probably don’t need too much guidance anyway.
With so many different WordPress hosting companies out there, the level of service and support also differs greatly. Read on to see how WPQuasar can migrate your site to our cloud for free as part of the on boarding process.
Regular site backups are important at the best of times, but before any change of host is attempted a backup of your site is a must. If your current host has a backup feature we can use that, but we will also capture the site data with our backup tools.
With the site data backed up, we will upload it to a new WordPress instance on the WPQuasar cloud. This process is semi-automated and might involve changes to files that reference the domain name.
With the content and database data running on WPQuasar, we will perform a test of the migrated site in a staging environment. You will be given a custom staging URL under the wpquasar.dev domain.
Once everyone is happy the migrated site has been tested and is performing well, we can switch over the domains DNS records. We will show you what to do here.
At WPQuasar our engineers can perform a site migration at either the system or plugin level, depending on which migration path is the best option for your site.