Local Connect doesn't work for some Legacy WP Engine sites

[scottbuscemi]

I still can’t pull down sites. It will show that the pull is successful, but the files and db from WP Engine won’t get pulled down. I’m on 5.7.2.

{"thread":"main","class":"","level":"info","message":"Downloading latest excerpt from install ...\n","timestamp":"2020-08-25T19:45:02.524Z"}
{"thread":"main","class":"","message":"Plan for install *** doesn't support SSH\r\nConnection to ***.ssh.wpengine.net closed by remote host.\r\n","level":"warn","timestamp":"2020-08-25T19:45:04.407Z"}
{"thread":"main","class":"","level":"info","message":"\u001b[1;31m\rError: \u001b[0munknown error encountered downloading database: Unable to pull database: exit status 1\n","timestamp":"2020-08-25T19:45:04.418Z"}
{"thread":"main","class":"r","message":"Error: ENOENT: no such file or directory, open '/Users/***/Local Sites/***/app/public/.wpengine-conf/wp-config-site.php'","level":"error","timestamp":"2020-08-25T19:45:04.423Z"}

@ben.turner any chance for a fix on this?

EDIT: turns out my plan does not include SSH. Perhaps Local could properly show an error message when this is the case rather than stating the pull was successful.

[ben.turner]

Hey @scottbuscemi – It looks like this is a slightly different issue than the original thread so I moved it to its own topic.

I followed up with some people at WP Engine, and it looks like this is due to a very edge case scenario where SSH isn’t available on older infrastructure.

Because Local makes use of SSH when using Connect, this is why it fails.

Right now there isn’t a good way to fix this, and so the only work around would be to migrate the remote site to some a new, different infrastructure. If you reach out to WP Engine’s support team, they should be able to help with that.

Sorry for the confusion and hassle with this, but I hope that all makes sense!

[scottbuscemi]

Thanks! Support was able to get me into an account with SSH.