WordPress WP Engine WPEngine

WP Engine How To SFTP

SFTP may sound intimidating but don’t fret! It’s not. If you’ve used “regular” FTP, SFTP is no sweat. Here’s a quick quide on how to set up SFTP credentials with WP Engine.

  1. Login to the WP Engine User Portal
  2. Click “SFTP Users” in the left hand menu.
WP Engine How To SFTP

3. Click the purple “Create SFTP User” button.

4. Enter username, password, optional path (if you don’t know what path is, you don’t need it) and click “Add SFTP user”.

5. That’s it! Your new SFTP user will now be shown in the list of SFTP Users.

Note: Once the user is created, WP Engine will append the username you chose, to the end of your account username.

6. Connection information is listed at the top of the SFTP Users screen. Your SFTP server name is always in the following format: The port is always 2222 (unlike regular FTP which is typically 22)

7. Now you can use your favorite FTP program* to connect to your WP Engine install allowing you to manage files.

*For Windows, we like FileZilla.

Sign up for premium WordPress hosting with WP Engine today!

WordPress WP Engine WPEngine

WP Engine How To Create Staging

Thankfully almost every action within the WP Engine User Portal is intuitive, and creating a staging environment is no exception.

Steps to Create Staging at WP Engine

  1. Login to the User Portal
  2. Click Create Staging in left hand menu.
WP Engine How To Create Staging - Start

3. Choose environment options. Here you have the option to clone the live or Production site, start new (blank or guided) or copy from another install. In most cases you’ll select “Copy an existing environment to this site” as this will allow you to clone your Production environment.

WP Engine How To Create Staging - Choose environment type

4. Select the production environment. Note that you’ll need to choose the most recent Backup. If you want the most current version of your Production environment, you’ll want to create a Backup first, before you create the staging environment.

WP Engine How To Create Staging - Select environment to copy

5. Give your staging environment a unique name, and click Add Environment.

6. That’s it! You’re done. Just give it a few minutes, and the new install will be built. If you did copy the Production environment, your WordPress user information remains exactly the same, just use the new staging URL.

Note: You’ll need to create new credentials in order to access the staging install via SFTP.

Sign up for WP Engine today!


This Post Was Composed with LocalWP

On my “to try” list for a while now is LocalWP, an application to streamline the process of working with WordPress locally. Put another way, you can build a WordPress website on your local computer and then use WPLocal to push that site online. Why would you do this you ask? There are several reasons, chief amongst them being speed. Here’s why I like LocalWP and will consider working it into my normal workflow.:

  1. It’s fast. While WPEngine is fast, the speed of interacting with any website that isn’t hosted locally is a result of many factors including your Internet connection speed and daily traffic levels. WPLocal is operating on your local computer which for the most part bypasses any reliance on your Internet connection.
  2. Good for travel. For those that travel and rely on cellular Internet access, closely managing your bandwidth usage is key to survival. Because WPLocal works mostly offline, this reduces the amount of bandwidth used and is of course much faster than working online if your connection is poor.
  3. Another staging environment. While WPEngine features a robust and easy-to-use staging environment system, working locally gives you another staging environment, to queue your updates and protect you (from yourself) from screwing up a live website.
  4. Tight integration with WPEngine. LocalWP will connect directly to WPEngine using their API, which is easily enabled. You can then view all of your sites, and “pull” any of them locally, to be edited and then pushed back live.
  5. It’s free. The Community version is free, and LocalWP claims it will stay that way. Pro adds a few features, and priority support which makes sense if you’re going to make LocalWP an integral part of your team’s process.

While I’ve only scratched the surface of what LocalWP can offer, I’m pleased to find the toolset to be simple and powerful.


Upon pushing my local changes live, I had an issue. The local domain: josiahcole.local did not update to the live domain: – A quick chat with WPEngine support solved the issue, however the root cause is still unkown. I will udpate this post the next time I attempt to publish vis LocalWP.

WordPress WP Engine WPEngine

How to Clear the WP Engine Cache

WP Engine built-in caching is a breath of fresh air if you’re used to managing caching plugins, and their finicky settings and tendency to break.  Built into the WordPress dashboard, the WP Engine cache control is just two clicks away, which makes theme changes easy to see immediately.

This action can also be accomplished via the WP User Customer Portal which is a nice feature addition, allowing an administrator or network technician to clear the website cache, without having direct WordPress access.

WPEngine Cache Control User Portal
WordPress WP Engine WPEngine

How to Access phpMyAdmin at WP Engine

WPEngine phpMyAdminIf you’ve run WordPress for any length of time, you’re no doubt familiar with phpMyAdmin.  Access to phpMyAdmin can often be critical to your WordPress debugging needs, and thankfully WP Engine makes this very easy.

Unlike some web hosts which hide phpMyAdmin, or put it behind an additional (and unknown) password – phpMyAdmin at WPEngine is accessible via one-click inside their User Portal.

Steps to Access phpMyAdmin at WP Engine

  1. Login to the WPEngine User Portal.
  2. Click PHPMyAdmin in the sidebar menu.
  3. That’s it!

phpMyAdmin will launch in a new tab, and you’ll have direct access to both the staging, and live databases.

Make sure to run a full backup before making any direct changes to your database.