Local not opening after update to 5.10.3

Support
1

Issue Summary

After upgrade to version 5.10.3 my app wont start. I see the process in the task manager and also tried to reinstall and execute with admin privilegies.

Troubleshooting Questions

  • Does this happen for all sites in Local, or just one in particular?
    The problem is with the application.

  • Are you able to create a new, plain WordPress site in Local and access it in a Browser?
    No, because I cant open the app.

Replication

1 - Updated to version 5.10.3 from previous version using the auto updater

System Details

  • Which version of Local is being used?
    5.10.3

  • What Operating System (OS) and OS version is being used?
    |Edition|Windows 10 Pro|
    |—|—|
    |Version|20H2|
    |Installed on|‎22/‎12/‎2020|
    |OS build|19042.906|
    |Experience|Windows Feature Experience Pack 120.2212.551.0|

local-lightning.log (77.4 KB)

2

same issue .any solution

3

Hey @rejath – can you let us know a little more info about your system?

  • What OS is being used?
  • Are you able to see the Local process in the activity manager as well?
4

@feifles – Thanks for your patience with this, and sorry for the hassle!

The Local log has this error within it:

{"thread":"main","code":"EADDRINUSE","errno":"EADDRINUSE","syscall":"listen","address":"::","port":4000,"level":"error","stack":"Error: listen EADDRINUSE: address already in use :::4000\n    at Server.setupListenHandle [as _listen2] (net.js:1306:16)\n    at listenInCluster (net.js:1354:12)\n    at Server.listen (net.js:1442:7)\n    at GraphQLService.<anonymous> (%%appPath%%\\main\\graphql\\GraphQLService.js:16:1646)\n    at Generator.next (<anonymous>)\n    at i (%%appPath%%\\main\\graphql\\GraphQLService.js:1:132)\n    at processTicksAndRejections (internal/process/task_queues.js:94:5)","message":"listen EADDRINUSE: address already in use :::4000","timestamp":"2021-04-01T18:30:37.465Z"}

With the main bit of useful messaging being:

Error: listen EADDRINUSE: address already in use :::4000

The 4000 port is Local’s default GraphQL endpoint, so maybe Local didn’t clean up that process before trying to upgrade.

The first thing to try is to restart the computer. Hopefully that clears out whatever process is currently listening on port 4000.

If that doesn’t work, can you try manually killing that process and then restarting Local?

To do this, list what process is listening on port 4000 by opening a terminal and typing:

netstat -ano

From there, you should be able to match the process id to the actual application in the task manager, and kill that process. More info can be found in this Microsoft help doc:

Can you give that a try and let me know how that goes?

5

I had the same issue when updated to 5.10.3 on Windows 10.

I have restarted PC, uninstalled and reinstalled and the app still doesn’t open. Even just uninstalled and installed 5.10.1. But still the same issue…

6

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