basecamp / pow

Zero-configuration Rack server for Mac OS X
http://pow.cx/
MIT License
3.41k stars 259 forks source link

.dev domains are not working in El Capitan #532

Open jspooner opened 8 years ago

jspooner commented 8 years ago

I'm getting a connection refused error when trying to access a .dev domain

curl http://app.dev/ --verbose
*   Trying 127.0.0.1...
* connect to 127.0.0.1 port 80 failed: Connection refused
* Failed to connect to app.dev port 80: Connection refused
* Closing connection 0
curl: (7) Failed to connect to app.dev port 80: Connection refused

I found a similar issue but these solutions did not work. https://github.com/basecamp/pow/issues/415

KazW commented 8 years ago

I ran into this recently on a new macbook... Turns out I forgot to run one of the daemons: sudo launchctl load -w /Library/LaunchDaemons/cx.pow.firewall.plist

attilagyorffy commented 8 years ago

@jspooner I'm successfully running pow on El Capitan, version 10.11.5 without any problems. You may need to verify whether the pow daemon is running. A ps aux | grep -i pow might help.

joshuaswilcox commented 8 years ago

I have a similar issue on macOS public beta. They stopped working after the last beta update. It is running:

josh            68434   0.0  0.2  3057584  32188   ??  S     9:21PM   0:00.20 pow

but I get

@Josh ➜  ~ rvm:(ruby-2.1.5)  curl http://admin.ahbwellnessportal.dev --verbose
* Rebuilt URL to: http://admin.ahbwellnessportal.dev/
*   Trying 127.0.0.1...
* connect to 127.0.0.1 port 80 failed: Connection refused
* Failed to connect to admin.ahbwellnessportal.dev port 80: Connection refused
* Closing connection 0
curl: (7) Failed to connect to admin.ahbwellnessportal.dev port 80: Connection refused
joshuaswilcox commented 8 years ago

Got it working again with:

sudo pfctl -f /etc/pf.conf; sudo pfctl -e
Loremaster commented 8 years ago

@joshuaswilcox Thank you very much for that! It was broken for me and it looks like it happened after upgrading to newer version of El Capitan (10.11.6). This fixed it!

DarthMike commented 7 years ago

Thanks @joshuaswilcox Fixed it for me too!

bradens commented 7 years ago

What is going on here. That fix worked for me but i'd like to know why haha.

dombarnes commented 7 years ago

@bradens running man pfctl kinda answers that pfctl -f /etc/pf.conf is load rules from the given file pfctl -e just enables the packet filter /etc/pf.conf is probably the stock macOS one

Frank004 commented 7 years ago

@joshuaswilcox this work for me. great

alistairholt commented 7 years ago

This is getting really annoying to deal with. Does anyone know why it's broken? I'm on macOS 10.12.5. I've tried reinstalling Pow with no success. I have to run sudo pfctl -f /etc/pf.conf; sudo pfctl -e every time I reboot.

ngoue commented 6 years ago

I'm with @alistairholt – not sure what needs to change, but I don't like having to lookup this pfctl command every time I reboot.

alistairholt commented 6 years ago

@ngoue I've since switched to https://github.com/puma/puma-dev.