— Hi I just installed local it is my first time ever but i cant create a site i do all the steps then an error appears says Command failed and then it delete the site and take me back to the beginning when it says create a new site. Can you help me wit that, Thank you
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.
We have a Windows Troubleshooting guide below that goes over some common items worth checking. For example, make sure you’re running Local as an admin user, that you don’t have any security blockers, and that Local has access to update your Hosts file.
If you’re still having trouble can you share your Local log again? It doesn’t seem to have attached.
It seems like there might be some security and/or network connection issues.
What type of network are you connected to? When you’re using Local for the first time it will need to reach out and make some connections to download some necessary components. Are you using a VPN, proxy or office network of some kind?
Do you have any antivirus, security, or firewall applications that could be blocking Local still?
hi thanks for responding. no im using my computer normally no vpn i have proxy . I already turned off antivirus and firewall hoping for it to work but still
I’m not sure if it’s the exact same issue you’re having, but I thought I’d share my experience — maybe it’ll help.
I was struggling a lot with an error where MySQL wouldn’t start my sites. I tried several solutions, searched everywhere I could… but nothing worked. After a lot of trial and error, I decided to change the Router Mode to Site Domains — then I got a different error: “Local’s router is having trouble starting.”
With the help of Copilot, I discovered that port 80 was being used by Apache (httpd.exe). I ran the following commands:
netstat -aon | findstr :80
tasklist | findstr [PID]
In my case, Apache came from XAMPP, which I had installed before. I ended the process via Task Manager and restarted LocalWP. Since then, everything has been working smoothly without any headaches.
Update:
After two days running fine, the error came back…
Digging deeper, I found that the issue was related to MySQL’s startup time — it takes longer to start listening when the system is running on an HDD, which ends up causing the infamous timeouts in LocalWP.
I used Copilot to help optimize the database, and after some testing and adjustments, we managed to create a custom my.cnf file specifically tailored for startup on machines with HDDs.
And just to be safe, I also copied it into my sites’ folders and blueprints — to ensure each instance is ready to start quickly.
It’s been 10 hours since I applied it, I’ve opened several sites in a row... and so far, no errors. It finally seems stable.
I’m sharing the file content below — maybe it’ll help someone facing the same issue my.log (981 Bytes)
(I don’t speak English, I used AI to translate it. Sorry if there’s anything wrong.)
