That certainly is an odd issue to see. When you connected to WP Engine did you use the API credentials from WP Engine? It’s possible you may need to recreate those credentials. Here is a help doc with information on getting started with WP Engine connect.
Thanks for double checking the connection with the API Key. Upon another look at the screenshot you provided of your WP Engine site list, I am seeing that each site appears to be set as a single environment site.
The Local team is aware of an issue where single environment sites aren’t being listed after connecting to WP Engine and a fix is being worked on. A current work around for this would be to convert to multi environment sites. To learn more about converting to multi environment sites here is a link to How to Convert Single-Environment Sites.
At the time Julio responded, I changed my setup and created a “multi-site environment” (within WPEngine). I was then able to see my site from Local.
My issue now is that Local <-> WPEngine doesn’t work for “multisite Wordpress”. Don’t get confused by the two things that sound the same… but are very different. Local doesn’t support pull/push of multisite Wordpress sites.
I’m quite confused now. I was responding to Julio’s comment as quoted below…
The Local team is aware of an issue where single environment sites aren’t being listed after connecting to WP Engine and a fix is being worked on. A current work around for this would be to convert to multi environment sites . To learn more about converting to multi environment sites here is a link to How to Convert Single-Environment Sites .
It sounds like you, lsubirana, are saying that Local still isn’t working even though you’ve followed Julio’s advice and switched your environment from single-site to multi-site. Geez, I hope that’s not the case. (I hope I’m just still confused. )
In either case, I just wanted to keep this thread from expiring and to be notified when this “…issue where single environment sites aren’t being listed…” is fixed so I can know to try to set my account up again then. I have no reason to use Local until that happens because I don’t want to switch my account to multi-site.
This issue can be resolved by converting your site to the Multi-Environment configuration within the User portal. Just to be clear, this is not a WordPress Multisite change, but is just a change that enables the access to the new Staging and Dev environments as well as portability to the Local client. For more info on that change you can see an article here that goes into detail about the Multi-Environment Sites and Environments - Support Center
There are not structural or functional changes to the site itself just enablement of the new features.
To enable the multi-environment setup you just need to go to your Sites page located at Login and then click on the 3 grey dots to the far right of your Install name and then choose the option listed as “Convert to site environment”
Once this is complete the site will be accessible in the Local client.
And to lsubirana’s point, yes the Local Client does not currently function with WordPress Multisite. So even though lsubirana was able to enable access to their environment by enabling the Multi-Environment option, previously described, once that was enabled the site lsubirana was trying to pull down was a WordPress Multisite, which currently isn’t supported with the Local Client.
If you read @msadler response carefully, he addresses all your questions. I’ll just emphasize that since your Wordpress site is NOT a multisite, changing your WPEngine site to a multi-environment setup will not change anything to the site itself, so I would not wait. You should be able to use Local right away.