All of my local sites have changed to localhost:0000 (different port number) domains instead of the personalized ones originally set.
This breaks our custom development workflows, like BrowserSync and such, and we can’t rely on Local’s live reload since it doesn’t seem to pick up our file changes.
This is really proving to be disruptive as it’s a set-back, and so I’d love to find a solution to stop this happening again.
Hi there @elliottmangham - thank you for bringing your question to the Local forums!
Sounds like perhaps a preference was changed for the Router mode.
If you head to Preferences > Advanced > Router mode you can try changing it to “site domains” and see if that helps.
Let me know,
Thank you for bringing that setting to my attention! I’ve changed that, and it does indeed seem to switch them back.
However, it instantly began to flag an error: “There is a port conflict with this site’s domain.”.
The website then becomes inaccessible, showing a 404 “Site Not Found” error (Shared Upload (2022-07-20 at 9.54.21)).
It sends me to this page: What is Router Mode? - Local
I can confirm that this is the only local development environment running on this system, and there’s no other applications installed that would affect local domains or ports that I am aware, as it’s a new MacBook Pro M1 with a fresh Local installation.
When I follow the instructions to see whatever is on port 80, I get this:
Is this safe to kill? And will it remain off?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.