Hi. I’m a new developer, trying to create a site in Local. I almost finished the homepage (haven’t taken a backup yet), went to open wp-admin the next day and it simply wouldn’t load and still won’t. It doesn’t even ask for my login details. It just says loading. I started a new test site to see if was all sites, but that one is fine. Local is up to date and I’m running Windows 10. It was suggested to me to create a zip of the wp-contents folder and SQL files and then import them into Local to start a new site but not sure if I’m getting the SQL files right - the person suggesting it uses Mac so couldn’t help more. I’ve attached screenshots of the folder and the file (within the SQL folder) I tried.
Are you using any other development software to build your site? In looking at your log file, it seems Local is trying to access port 10024, where your site’s database is supposed to be running. When it checks that port, it runs into a conflict (something else seems to be using it also) and aborts.
Quitting whatever tool is conflicting with that port should resolve this issue. If you’re not sure what that might be, I can help you with a command that will give us more information about what is trying to use port 10024.
Thanks for the welcome and speedy reply. I’m not using any other software. Just Local and building with a StudioPress theme. I definitely have no idea what tool would be the problem and don’t know what port 10024 is.
@Saromi No worries, we can try to figure it out! Based on your original screenshot, it looks like you’re using Site Domain routing mode - I can see your site’s URL ends in .local. If we’re running into a port conflict, switching Local to localhost routing mode might resolve the issue.
Localhost routing mode would mean your site is running on a specific port on your computer; when you open the site in a browser, the URL will look like localhost:10000. You can see my site here is using localhost mode -
@Saromi Thanks for sticking with me. Something on your machine is conflicting with Local’s ability to read from the database; I’m just not sure what. For you, that is running on port 10024.
Can you try finding (and turning off) whatever is running on that port? Here is a guide to doing so - 3 Ways to Find Which Linux Process Listening on a Port. On Windows, I would recommend using the netstat command in that help doc.
Try dropping the $ at the beginning of all of the commands and running again - you shouldn’t need to type that before the sudo apt-get for the command to run.
@austinwendt I’m not entirely sure if I’m doing the right thing. Is this correct? I’ve opened my pc’s command prompt and pasted in the command (first screenshot)? If yes, I’ve just tried it without the $ signs and it didn’t work (second screenshot).
@Saromi Since it appears you’re using Windows, when you open the command prompt, the only command you need to enter is:
netstat
You do not need the “sudo” command and related…that’s for Linux.
That will show all active connections. If there’s another application using the port that Local needs, it may or may not be running at the time you’re checking, so you need to list all active and inactive connections. If using just the “netstat” command doesn’t reveal something making use of port 10024 (which previous posts suggests is the one you’re looking for), then use this command:
netstat -a
That should list all connections.
You’ll want to go down the list until you find something that looks like:
0.0.0.0:10024
…under the Local Address section.
It won’t necessarily be “0.0.0.0” for the address part depending on your system’s configuration/networking, but the “:10024” part should be there somewhere. If you find that, take a screenshot showing it and post it here. That should let them help track things down.
@Saromi Samantha, I’m sorry, that wasn’t helpful. But just to clarify one thing, I had a typo in the previous post. The command for showing all should be:
netstat -a
…and not netstate -a. I edited/corrected the previous post. I just want to be sure that if you used netstate -a, that you try again with netstat -a.
