Hi there, just upgraded MacOS to the latest version (Sequoia), and it looks like Local is having port issues on my sites and is only able to run in localhost mode. Not sure if there is a workaround to get the *.local development domains working again or anything I can try?
Local Version: Version 9.0.5+6706
Operating System (OS) and OS version: MacOS Sequoia (15.0 (24A335))
Hi @theheartypixel!
Are you running other developer applications simultaneously? That could also cause similar issues. Apps like MAMP, XAMPP, or Docker for example.
Otherwise here are some steps to identify and address this:
Stop all sites that are running in Local
Force quit Local
(If using Mac) Run the command lsof -nP -iTCP -sTCP:LISTEN
What you’ll be looking for here is to see when sites are stopped and Local is properly shut down if there are still programs running on ports 80 and 443. These may be conflicting with Local or the system may be reporting Local is still running.
Once you run that command you should see a list of listening ports. If you see a particular program making use of those ports, you can then kill that process by running sudo kill -9 XXX where XXX is the PID number of that process.
After that, you should be able to retry. Keep us posted if you have any questions or continuing issues.
There are also some more details around this and other troubleshooting steps at this link if needed: Stopping Whatever Is Listening On Port 80.
Thanks for your reply! I’m not running any other dev apps simultaneously, so I went through the steps and ran the command to see if anything was running on ports 80 and 443. It doesn’t look like there’s anything else running on either of those ports, and the dev sites still aren’t loading when restarting Local. Here’s a screenshot of terminal after running that command:
The curious thing though now is Local does seem to be resolving in the browser, but it’s resolving to this page on every site instead of pulling up the actual sites, so not sure what’s going on there:
And still getting the port error message at the top of Local 
Do you want to share your full Local Log here @theheartypixel so we can take a deeper look?
Sure thing, I tried uploading my Local Logs zip file here, but it says it is over the 30MB limit, so I’ve put it on Google Drive: local-logs.zip - Google Drive
Thanks for this report, @theheartypixel.
I’m unable to reproduce this so far — Local and its domains work for me under Sequoia:
As Nick mentioned, your logs suggest an existing process may be running on Local’s router port or one of Local’s site-specific ports. A couple of things you could try:
Hey there, thanks for the suggestions. I’ve done a full reboot and searched Activity Monitor and there aren’t any other nginx or Apache processes running, and it’s still having the same issue.
I also went ahead and exported my sites from Local, uninstalled Local using this guide Uninstall Local - Local, restarted the computer, installed a fresh copy of Local, imported one of the sites I exported and tried running it, and it’s still having the same port issues.
My laptop is an Intel-based Macbook Pro and not one of the newer Apple Silicon laptops, so not sure if that has something to do with it.
Ended up moving away from Local and installed DevKinsta + Docker, and it is working great. Not really a solution to the Local problem I was facing, but I couldn’t get it working after upgrading the OS and trying multiple fixes, so there must’ve been something not quite right on my machine, even after a fresh install of Local.
I know this doesn’t really solve my original Local issue, but just wanted to follow up.
Thank you for your follow-ups here @theheartypixel! We have been a bit stumped because we can’t replicate, but we’ll continue to dig in and see if can spot anything out even just to help future users. We understand doing what is best for your needs and appreciate you giving Local your time to try and get working!
python - localhost:5000 unavailable in macOS v12 (Monterey) - Stack Overflow Have you tried this? I had set it off, but after last macos update it went on and caused this issue. After switching off, it is working ok and port is free.
