Jetpack connections

By default, when a WordPress single site or a network site on a WordPress multisite is created, the Jetpack plugin is automatically enabled for that site.

A system process runs every hour after the site’s Jetpack connection is created to check that it is still active. If the system detects that the connection is not active, it will automatically attempt to reconnect. A site’s Jetpack connection can be disrupted if the site’s address URL is updated, for example during a site launch.

When enabled, Jetpack plugin automatically creates a connection to WordPress.com. This connection is required for features such as Jetpack Stats and Jetpack Activity Log.

If a site’s connection to Jetpack is disrupted and does not reconnect over a reasonable amount of time, create a VIP Support request for assistance.

WPVIP machine user

Jetpack and Akismet connections are registered via a WPVIP machine user. Depending on when an application was first initialized, this machine user will be one of:

• wpvip-jetpack-connection-owner: The current per-organization machine user, used for newer applications.
• wpcomvip: The legacy machine user, used for older applications.

Both users serve the same purpose: They provision the Jetpack Complete plan for a site and are required for the VIP Platform to manage Jetpack and Akismet connections.

The WPVIP machine user is listed as a registered user on WordPress sites. This user should not be removed. Logins for the machine user are disabled, and as a result, two-factor authentication for that user is also disabled.

Prevent Jetpack from automatically connecting

If a site on an environment needs to be opted out of the automated reconnection behavior of Jetpack, define VIP_JETPACK_AUTO_MANAGE_CONNECTION as false in vip-config.php:

define( 'VIP_JETPACK_AUTO_MANAGE_CONNECTION', false );

Prevent Jetpack from loading

To prevent Jetpack from loading in an environment define VIP_JETPACK_SKIP_LOAD as true in vip-config.php:

define( 'VIP_JETPACK_SKIP_LOAD', true );