Hey @zeth – From that screenshot of the browser, that looks like the default response from a newly installed Apache server. Local has a different, less “plain” page when it’s created, so what you’re seeing is likely some other piece of software.
Great work testing things out! All of the steps you’ve outlined are ones that I would recommend. I think what’s happening is that Big Sur ships with an Apache server. You should be able to get things working by doing:
-
Quit Local
-
Stop the default apache server
sudo apachectl stop
-
Verify that nothing is listening on port 80
These commands should give you an idea of all the processes that are listening on Port 80. Note that
sudo
is needed because some of these processes are run with elevated privileges.sudo lsof -i:80; sudo lsof -tnP -i:80 | xargs -n 1 ps -p
-
Start Local
Can you give that a shot and let me know if that fixes things for you? If you are still running into issues, can you share the output of the terminal after running the above commands?