search

basecamp / pow

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

.dev domains only working on port 20559 #525

Open mattscilipoti opened 8 years ago

mattscilipoti commented 8 years ago

My .dev domains are not working as expected. They only work on port 20599. I have read many issues, from Mavericks to El Capitan Beta.

This gist has the output from many of the commands mentioned in those issues: https://gist.github.com/mattscilipoti/810b5f495ce20e5cf918

I have tried reinstalling, using powder, and rebooting. My apologies. I am trying to learn more about what is required for pow, but I am at the end of my knowledge.

If I can provide any more info, please let me know.

OSX 10.11.3

When installing pow, I got this error (full message in the above gist):

*** Performing self-test...
!!! Couldn't resolve configured domains (dev)
JDutil commented 8 years ago

I ran into a similar issue today, and was able to resolve it by enabling port forwarding manually per the DNS troubleshooting section of the wiki sudo pfctl -f /etc/pf.conf; sudo pfctl -e

The root cause being that I had installed docker for mac beta, but that workaround did the job fixing it.

mattscilipoti commented 8 years ago

Thanks @JDutil. I have tried that. No help. Results below. Since those instructions indicated that they were for Yosemite, I also attempted those listed for Mavericks.

You indicate that you found the root cause (docker, mac beta). I was playing with early docker versions too (and current versions). How did you identify the root cause?

Enable port forwarding (listed for Yosemite)

$ sudo pfctl -f /etc/pf.conf; sudo pfctl -e
Password:
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

Verify port-forwarding (list for Mavericks):

$ sysctl -w net.inet.ip.fw.enable=1
net.inet.ip.fw.enable: 1
sysctl: net.inet.ip.fw.enable=1: Operation not permitted
~/dev/great_enough/passport_scheduler (master)
$ sudo sysctl -w net.inet.ip.fw.enable=1
Password:
net.inet.ip.fw.enable: 1 -> 1
JDutil commented 8 years ago

@mattscilipoti there were numerous other bug reports in other issues on the repo pointing to docker beta being the cause and it just so happened that I had just installed docker beta as well. Sorry I don't have any ideas beyond the fix that worked for me, but you could try following the other troubleshooting tips in the wiki which is where I found my solution https://github.com/basecamp/pow/wiki/Troubleshooting

mattscilipoti commented 8 years ago

@JDutil Thanks, I have. Results are in the above comment and the referenced gist. I certainly appreciate your time and attention.

ivana-mcconnell commented 8 years ago

@mattscilipoti Any chance you've found a fix for this? I've come across the same problem, and no luck with the above.

mattscilipoti commented 8 years ago

Sorry, no. I never did get it working on that machine. There a few alternatives now: https://www.driftingruby.com/episodes/puma-dev-replacement-for-pow-and-prax, http://invoker.codemancers.com/, http://dysonsimmons.com/tradie/, https://ysbaddaden.github.io/prax/ puma-dev supports ssl and actioncable