Thank you everyone who has chimed in and helps clarify this issue! The general problem is that when a Windows Username includes special characters (so an apostrophe ' or a non-ASCII character like é) it can break the commands Local uses to communicate with the MySQL database.
Usernames that have an apostrophe in them should be fixed, so update to the most recent version of Local if the username has an apostrophe in it.
Read on for what you can do if the username has other non-ASCII characters.
Upvote the Bug
If you are affected by this issue, please up-vote this bug by clicking the “Vote” button at the top of this topic. If you can, please leave a reply that mentions the username that is causing problems. This gives us a good idea of the various characters that are causing issues.
Workaround
Due to the nature of this bug, the main option we recommend is to create a new Windows user that doesn’t contain any special characters.
If you want to live a little dangerously, take a look at the solution proposed by @Danniemite :
Original Message:
Hello! I got this error when trying to create a new site.
I attached a screenshot of the error and the log file.
Hey all, sorry you’re having trouble with provisioning sites!
Would you try reinstalling/installing the latest beta build of local (5.0.7): https://localbyflywheel.com/community/t/5-0-7-beta/15063
Try right-clicking the installer and “Run as administrator” just to make sure that installer can get everything it needs in place without permissions issues.
OS: Windows 10
Downloaded the beta version and ran the installer as administrator. When trying to create a new site i get the same error as reported in this thread.
I had this same issue ( using Ubuntu ) I had to purge the file and reinstall it on my administrator account using the software installer. For some reason when I install Local using dpkg it errors.
Hey @d4rk3c - There is a limitation in Local right now that prevents it from working when there are special characters in the path, such as the accent in the username here. We are working on getting this fixed for future versions but currently you will need to use Local version 3 or create a user that has plain latin characters to avoid the path issue.
