I use Lando alongside Local for specific environments that I need set up. Typically, I turn off one, then turn on the other and I’m good to go. They obviously can’t run at the same time.
After upgrading to Local 5.9.6, I can’t run Lando anymore. Even with Local completely closed (quit out of application), I still get the 404 Site Not Found Local screen (with the Local logo at the bottom). This is a big problem for me. I even tried changing the Local routing to localhost and it’s still preventing anything else from handling requests.
Is there some background process I have to kill or a configuration I need to change?
System Details
Which version of Local is being used? 5.9.6
What Operating System (OS) and OS version is being used?
@jasontheadams-- I know that you’re last post is only ~15 mins old – Once you start Local again and then try to change back to Lando, can you post back to this topic if Local still has issues killing those processes?
One of the changes that has happened lately for Local is updating Electron (what Local is built on – yeah security and performance!! Boo odd, breaking things like this!).
I know the team did some work on making those processes terminate correctly across the various systems, but I wonder if there’s a bug here given that your system is running on the new macOS – Big Sur?
Thanks for the explanation! I completely understand the thrill of updating dependencies only to discover what new tricks they brought.
Minutes after my last post I had to kill the processes again to start Lando. I actually made an alias out of Andy’s snippet for easy access in the future (as I flip back and forth regularly). It seems as though this issue is consistent on the latest version of Local — if I start the app, I have to run this script after closing it to kill nginx.
I think we’ve zeroed in on what might be going on. We don’t have a quick fix, but it’s on the radar to be dealt with soon. Thanks for bubbling this issue up so we were able to replicate it!
Thanks for busting out a release with that. I’m afraid it doesn’t seem to be resolving the issue. To be clear, I’m just using ⌘+Q to close Local, which historically killed the services. If I’m supposed to be doing something else let me know. Otherwise, I have a suspicion this has to do with me being on Big Sur.
That’s how I’m quitting Local too and the processes seem to be cleaned up (though I am on Catalina). I’m checking via the terminal using this pair of commands which basically
list what’s listening on port 80
pipe those processes to ps for more info on that process (props to @afragen for showing me this command )
@jasontheadams – Since Andy is having it work with Beta + Big Sur, I’m wondering if there’s something else that is preventing Local from cleaning up those processes.
When you’re working with those sites, are you connecting to them somehow with another tool? Things that come to my mind would be:
Instant Reload enabled (Local should be able to handle this but )
Your IDE is connected to the Xdebug for the site?
Some sort of build tool within a terminal like npm watch
So it turns out I just need to go back to the first page of the troubleshooting book:
Have you tried turning it off and on again?
I noticed I wasn’t able to even stop a site in Local from running (i.e. pressing the stop button ran indefinitely), which was odd. I then decided to just restart my computer to see if something was just all gunked up.
After restarting I noticed Local was working again, and then I just quit out of it, started up Lando, and it worked great.
)
)