squarism
commented
8 years ago We have had the same thing. We used to have everyone (especially the non devs) install pow but now we're uninstalling pow from everyone's machine. With our VPN config or switching wifi, someone will get in a situation where facebook.com hits pow locally and they don't know what's going on.
We just have then turn off wifi and turn it back on (releasing dhcp will do the same). I assume it's dns cache. I don't have anything other than these useless anecdotes to add unfortunately.
We use pow for development locally and have intermittently been getting an error where people on the same wifi network are having trouble accessing our production website. So going to http://example.dev works fine in hitting the local instance, but going to http://www.example.com gets the "Pow is installed" message, or gets a 404. I've literally never seen this error in 5 years of using pow, but it's been happening with an increasing frequency in the last three months. When I tail the pow logs, I see requests for "www.example.com"
Wed Mar 23 2016 14:25:16 GMT-0700 (PDT)] INFO [192.168.0.18] GET www.example.com /favicon.ico [Wed Mar 23 2016 14:25:18 GMT-0700 (PDT)] INFO [192.168.0.18] GET www.example.com / [Wed Mar 23 2016 14:25:18 GMT-0700 (PDT)] INFO [192.168.0.18] GET www.example.com /favicon.ico
When it works for local dev, I get this:
[Wed Mar 23 2016 14:40:01 GMT-0700 (PDT)] INFO [127.0.0.1] GET example.dev / [Wed Mar 23 2016 14:40:01 GMT-0700 (PDT)] INFO [127.0.0.1] GET example.dev /welcome
The rest of the team is getting frustrated since they rely on the website to get anything done, but I really don't want to move away from Pow. Any ideas (or other debug information I can provide)?