Error could not load sites Local v6.1

Issue Summary

Troubleshooting Questions

  • Does this happen for all sites in Local, or just one in particular?

  • Are you able to create a new, plain WordPress site in Local and access it in a Browser?


  • Upgrade
  • Launch Local

System Details

This looks like an old bug which was fixed a while ago. The general issue is that Local is trying to get a list of sites from it’s GraphQL endpoint, but for some reason, that endpoint isn’t available.

I am seeing some odd lines in the Local log that makes me feel like something within the DNS of this computer isn’t resolving correctly:

{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2021-07-31T05:50:26.484336Z 0 [Note] Server hostname (bind-address): ''; port: 10028","timestamp":"2021-07-31T05:50:26.641Z"}
{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2021-07-31T05:50:26.485117Z 0 [Note]   - '' resolves to '';","timestamp":"2021-07-31T05:50:26.641Z"}
{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2021-07-31T05:50:26.485215Z 0 [Note] Server socket created on IP: ''.","timestamp":"2021-07-31T05:50:26.641Z"}

Note the part that says:

Server hostname (bind-address): ''; port: 10028
  - '' resolves to ''
Server socket created on IP: ''

From that error, it’s almost like the computer is trying to call itself by its IP address and not by localhost.

Can you try the steps outlined in this reply and see if there’s something already listening on the port that Local uses:

Also, can you let us know if you have any antivirus software installed, or other network configuration settings?

when I reboot my mac then everything works fine, but then when I exit Local and start it again then this error appears.

I do not have antivirus and other network configurations.

I am facing the same issue,
After running the kill command it seems that only local blocked the port 4000.

I am using apple m1

1 Like

I fixed the error.
this problem was due to the WARP app

to fix it for macos
sudo ifconfig lo0 -alias

Both of these things make sense in terms of why they resolve the issue – basically, Local was listening on port 4000, but then for some reason, the port wasn’t released correctly until manually killing the old process (like what mehedi did) or the computer restarted (what riodejaneiro did)

I wonder why Local isn’t able to fully close and release that port 4000?

When you closed Local, how did you do it? Was it using the little “x” in the upper left corner of the Local app, or did you use the quit command from the “Menu > Local > Quit”?

Were there any other processes running, like maybe a live link that was open, or a site wasn’t fully done being created?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.