After clicking [Add Site], an error message appears and building the WordPress environment fails.
I have checked the following by referring to the following topics.
I have uninstalled the security software (Norton).
I have checked “C:\Windows\System32\drivers\etc” and confirmed that the read-only setting for the “hosts” file is OFF.
What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc
Click [Create a new site].
Select [Create a new site] and click [Continue].
Enter the site name in [Site name] and click [Continue].
Click [Custom].
Select [PHP version], [Web server], and [Database] as follows and click [Continue].
PHP version: 7.4.30
Web server: Apache 2.4.43
Database: MariaDB 10.4.10
Set [WordPress username], [WordPress password], [WordPress e-mail] and click [Add Site].
Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.
It seems that the part with special characters is garbled text representing my username, which is written in Japanese (kanji). Since the PC where Local is installed is managed by my company, I cannot create a new user directory.
As a test, I tried installing it on my personal PC using the “Guest” user directory, and this error message did not appear, and it worked fine.
Would it be difficult to modify Local to support Japanese user directories?
I will also report this to my company’s system administrator and suggest creating the user directory in English.
We do have bugs filed to try and address this eventually but the problem is a bit more layered so we haven’t been able to give it priority over more urgent items. The easiest workaround for now will be to create a user without the special characters which hopefully your company’s IT will be able to help you with.
Sounds good @Kent-up. We don’t have any ETA to provide on when the bug will be addressed but we will share the news here in the forums and our releases page when it is.
