Host File Not Restored on Exit Causing 502 Error

Windows 10/Latest Local Version

I created a new site in Local. It matches my “live” website. The URLs are similar, site.com vs. site.local. Before I created the site in Local, I was able to get to site.com without a problem. After I created the site in Local, all I get when I access site.com is a 502 error. Even after I stop the site and exit Local, I still get the 502 error. I next edited the “host” file and removed the entry created by Local, and now I can access site.com. This totally makes using Local a pure pain in the rear! What genius programmer thought it was a good idea to allow Local to not restore the “host file” upon exit? How does something this devastating get past code review? I appreciate your efforts, and I love Local, but this is a deal-breaker.

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