WPCloud Deploy Documentation

Reasons Servers Fail To Deploy

In general, a server should finish deploying within 30 minutes. Most, except those from VULTR, should deploy in 20 mins or less.

Here are some reasons that a server might fail to deploy properly or look like it’s “stuck”:

Keys, Keys, Keys

By far, the number one reason for servers not deploying is an incorrect combination of PUBLIC-PRIVATE SSH keys provided in the SETTINGS screen.  Check, double-check and triple-check that your public-private key combinations are correct and that your password for your private key, if any, is valid (and does not contain special characters).

How to generate SSH key-pairs

If the information for your SSH key-pair is not entered properly we cannot log into the newly provisioned server to install our stack.

Bad Location & Size Combination

Many providers do not have all server sizes at all locations.  VULTR’s High Frequency servers are a particular egregious violator.  So, it is possible that you might be requesting a server size that just isn’t available.

Firewalls & Proxies

When a new server is being provisioned, it needs to call back into the server on which the WPCD plugin is installed.  If that server has a firewall in front of it, then the call-backs might be blocked.  The easiest way to handle this is to white-list your new servers’ IP as soon as it’s finished being created – you’ll need to monitor your server providers’ dashboard to see when the server is up and running and then copying its IP address to white-list on your firewall.

See also: Common server deployment issues and error messages

WP Crons Not Running

In order for servers and sites to be deployed properly, the WP CRON service needs to be working.  In particular, the following THREE crons (cron-hooks) need to be running on the server where the WPCD plugin is installed:

  • wpcd_wordpress_deferred_actions_for_server
  • wpcd_wordpress_deferred_actions_for_apps
  • wpcd_wordpress_file_watcher

When the plugin is first installed, these are probably running. But, over time, if other things are installed on your WordPress site, these processes might not start up or might have been killed.  The easiest way to check that they are installed and running is to install the WP CRONTROL plugin from wordpress.org.  Once that has been installed, go to the TOOLS->CRON EVENTS screen and in the search box on the upper right of that screen, enter “wpcd”.  You should then see the following screen:

If all THREE items are NOT shown, you should deactivate and reactivate the WPCD plugin.

Note: We have more than three crons running but those are the most important.  Additional ones are:

  • wpcd_scan_notifications_actions
  • wpcd_clean_up_pending_logs
  • wpcd_scan_scheduled_servers (If the Power Tools add-on is installed)

It is strongly recommended that CRONS are set to run at least once per minute.