Pow suddenly stopped working

[bhardin]

Pow has been amazing. I've restarted multiple times, no problem.

I restarted yesterday and now pow doesn't seem to be working anymore. I tried searching the issues for a similar issue, but to no avail. I tried rm -rf ~/.pow and then reinstalling pow also according to the documentation. But, still no dice.

OSX Yosemite 10.10.5

Pow is running:

bhardin@brett-mbp ~/.pow  ᐅ ps aux | grep pow
bhardin         24025   0.4  0.0  2423356    200 s001  R+    2:12PM   0:00.00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn pow
bhardin           644   0.0  0.0  2461592    164   ??  S    Thu01PM   0:00.11 -zsh -i -c exec env > '/var/folders/7y/hlkqw_bn3bn604xgrxcxsvgw0000gn/T/pow.528.1446759918536.52764'
root              643   0.0  0.0  2468972    176   ??  S    Thu01PM   0:00.02 login -qf bhardin /bin/zsh -i -c exec env > '/var/folders/7y/hlkqw_bn3bn604xgrxcxsvgw0000gn/T/pow.528.1446759918536.52764'
bhardin           528   0.0  0.0  3050168    176   ??  S    Thu01PM   0:00.43 pow
root               48   0.0  0.0  2494844   1400   ??  Ss   Thu01PM   0:02.77 /System/Library/CoreServices/powerd.bundle/powerd

bhardin@brett-mbp ~/.pow  ᐅ ping core-app-rails.dev
ping: cannot resolve core-app-rails: Unknown host

bhardin@brett-mbp ~/.pow  ᐅ scutil --dns
...
resolver #8
  domain   : dev
  nameserver[0] : 127.0.0.1
  port     : 20560
  flags    : Request A records, Request AAAA records
  reach    : Reachable,Local Address
...

Any help or guidance is appreciated.

[eploko]

Experiencing the same issue on El Capitan. The DNS resolver seems to be configured correctly and the pow agent is running, but Chrome can't resolve the .dev domain name after a reboot.

[eploko]

Re-installing actually helped. Removed all the launch daemon/agent configs and pow itself. Re-installed pow and rebooted. Works fine now. Heh.

[spentacular]

@eploko curious, which launch daemon/agents did you remove? I'm having trouble as well, would love to give your method a try.

[antulik]

Reinstalling did work for me, still have to enable port forwarding manually as in https://github.com/basecamp/pow/wiki/Troubleshooting after every restart

sudo pfctl -f /etc/pf.conf; sudo pfctl -e

[spentacular]

@antulik I'm getting this output when I run that command:

pfctl: Use of -f option, could result in flushing of rules
present in the main ruleset added by the system at startup.
See /etc/pf.conf for further details.

No ALTQ support in kernel
ALTQ related functions disabled
No ALTQ support in kernel
ALTQ related functions disabled
pfctl: pf already enabled

Is that what yours looks like?

[antulik]

@spentacular yes, exactly that, after that pow starts to work

[eploko]

@spentacular I removed ~/Library/LaunchAgents/cx.pow.powd.plist and /Library/LaunchDaemons/cx.pow.firewall.plist.

[davidhq]

I cannot get it to work even after

sudo pfctl -f /etc/pf.conf; sudo pfctl -e

Reinstalled and rebooted twice already, no go... any ideas?

[mitoyarzun]

Thank you @antulik , that did the trick for me.

[JackNeto]

Any update on this? Tried every trick and it's still not working for me

[dramalho]

to be honest I've stopped trying and went for a much simpler nginx based proxy approach. it's more hands on (changing /etc/hosts, setting up nginx conf files, running rails s, etc) but pow was way to magical right now, especially when things stopped working.

As it is, if I was starting over, there might be some benefit in straight out changing pow's default domain away from the now official .dev TLD. I'm guessing that's part of the issue

On Sat, 12 Dec 2015, 06:37 David Krmpotic notifications@github.com wrote:

same here... So is there a good alternative to pow? Looks like abandonware

— Reply to this email directly or view it on GitHub https://github.com/basecamp/pow/issues/517#issuecomment-164115138.

[koenpunt]

I'm using .pow as an extension for my Pow domains, and they stopped working too. Although it seems it's not consistent; sometimes it still does work..

[dramalho]

ahh so it's not just the TLD . Probably El Capitain issues , gotcha.

[koenpunt]

I found a solution. Or at least for me.

The current PF command appends the rule to an anchor, which I assume doesn't exist (anymore).

echo "rdr pass proto tcp from any to any port {80,20559} -> 127.0.0.1 port 20559" | pfctl -a "com.apple/250.PowFirewall" -Ef -

By omitting that part it just binds to the main ruleset:

echo "rdr pass proto tcp from any to any port {80,20559} -> 127.0.0.1 port 20559" | pfctl -Ef -

[koenpunt]

And a PR #521, if anyone still got Yosemite running, could you please check if this fix works there too?

[hbrysiewicz]

This happens every time I reboot my computer (since El Capitan). I have to run the uninstall script and then reinstall it in order to fix it.

[davidhq]

After much search, this is the only thing that worked for me: https://github.com/basecamp/pow/issues/452

[jeroenj]

@koenpunt Thanks a lot. That fixed it for me. :+1:

[SteveAquino]

@antulik Thanks, you're solution worked for me!

For what it's worth, I have been using pow trouble free for about 2 months. Today I took my work laptop with me to lunch and was working while disconnected, and when I came back into the office I started seeing this error. I don't know enough about the underlying technologies to say if that's relevant, but I thought I'd share in case it helps debugging.

[andersennl]

Thanks @antulik , this finally made it work for me again.