Local can't pull down site # 460364 on Flywheel. The specific issue happens when Local is doing the search and replace job for the domain. Within the logs, the error that shows looks like this: {"stack":"RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stderr maxBuffer length exceeded\n at Socket.onChildStderr (child_process.js:387:14)\n at Socket.emit (events.js:223:5)\n at Socket.EventEmitter.emit (domain.js:475:20)\n at addChunk (_stream_readable.js:309:12)\n at readableAddChunk (_stream_readable.js:286:13)\n at Socket.Readable.push (_stream_readable.js:224:10)\n at Pipe.onStreamRead (internal/stream_base_commons.js:181:23)","level":"warn","message":"Unable to import site.","timestamp":"2021-05-06T21:42:06.222Z"} A clone of this site is able to be pulled down, though once the DNS has been pointed to the new site, the issue occurs again.

The One-click Admin is not using https despite trusting it. Users have to manually correct the protocol in the browser.

Forum post: https://localwp.com/community/t/unable-to-provision-site-due-to-special-characters-in-windows-username/14419

Users running High Sierra are unable to create new sites in Local. The general issue appears to be related to not being able to connect to MySQL. This was first reported in this Community Forum post: https://localwp.com/community/t/mac-high-sierra-local-hangs-on-starting-up-site-services/21462?u=ben.turner A workaround does exist: While creating a new site that is hanging Create a second, throw-away site By creating the second site, the first site is able to finish creating, and the second site is able to be deleted without any issues.

Forum posts: • https://localwp.com/community/t/firefox-still-doesnt-trust-local-beta-5-2-ssl-certs/16427 • https://localwp.com/community/t/ssl-not-remaining-trusted/17294/3

When my site is pushed from Local --> WPE, the database does not fully upload, resulting in error establishing a database connection. Verifying by phpMyAdmin, only about 2-3 db tables have uploaded to WPE. (Though Local always indicates success with "Site pushed! Your site has been pushed to WP Engine") This occurs even if I pull a working site down from WPE, verify that it's working properly in Local, and immediately push back to WPE without making any site changes. Contacted WPE support. They first verified that my API access was setup correctly and later found this is a known bug: "the SSH connection times out during the mysql import, resulting in only some tables getting imported," but I haven't seen it posted on here yet. They suggested that it would hopefully be fixed in this new version (5.6.1) but I just updated and this has not resolved it. Local log file: https://www.dropbox.com/s/z5mxhholwegsngk/local-lightning.log?dl=0 Local 5.6.1+4184 (and 5.5.3 too) MacOS 10.14.6

https://flywheelhelp.zendesk.com/agent/tickets/14472699 The Issue All sites on the user's computer would display the following warning message in the WP version section Warning: Version warning: Imagick was compiled against ImageMagick version 1799 but version 1802 is loaded. Imagick will run but may behave surprisingly in Unknown on line 05.5.3 This is because the user has ImageMagick installed locally and bound to local environment PATH var: C:\Program Files\ImageMagick-7.0.10-Q16-HDRI When removed the installation from the PATH, the issue disappeared. Expected Behavior The customer should be able to use their own ImageMagick installation without having conflict with Local's ImageMagick installation Actual Behavior The Local's ImageMagick versions would conflict with the local env PATH var installation.

In a recent update by Algolia, it requires a self-signed SSL cert to use cURL. I updated my php.ini with a work-around, but it could be an issue for everyone else still. Here is a full run down on the issue: https://github.com/WebDevStudios/wp-search-with-algolia/issues/87

During recent testing, we noticed that e-mails are not being sent due to an invalid from address ( wordpress@localhost ) in WordPress 5.5. We are looking into whether or not this is something that the Local team needs to address or if it's a WordPress bug as it used to work in WordPress 5.4.2. --- As a workaround, we recommend using the Site Domains Router Mode.

I have 12 sites listed as running despite none of them are on. Presumably it's because I have quit the app without stopping them first. I tried re-starting and stopping but they are still listed as running. I suggest adding a double confirmation on alt+q asking if the user wants to stop their websites before quitting. Similar to Chrome's double confirmation.