“cannot access install” Error when Deploying from BitBucket to WP Engine

I recently came across a “cannot access install” error when deploying from a BitBucket repo Pipeline to WP Engine.

The error occurred on the rsync command, but during debugging I got the same problem with a simple SSH connect.  Nothing had changed on either setup recently.

I contacted WP Support and we worked through debugging the problem.  We couldn’t find the cause, and so I deleted the SSH key pair from BitBucket, and created a new pair.

I then added the new public key to WP Engine, and everything worked again.

I’m putting this out here in case this helps someone else.

I reduced CD pipeline from 43 minutes to 11 minutes, using parallel steps

I work on a large collection of sites for a university.

It’s a single codebase, shared onto 9 sites.  This is done via Bitbucket Pipelines.

For years each site has it’s own step in the pipeline CD script to copy the files to the server.  These steps were run sequentially, one after the other.

I’ve just changes these 9 steps to run in parallel.

Typical times were 43 minutes to deploy, but now it’s 11 minutes.

This will make a big difference, as when checking results on a site at the end of the list, I had to wait a long time.

Latest from the blog

View All
Social media & sharing icons powered by UltimatelySocial