Apache virtual hosts don't work after installing pow about pow

[sstephenson]

Correct - Pow and Apache aren't compatible with each other.

You could try this for serving PHP locally: https://github.com/eric1234/rack-legacy
Or uninstall Pow: curl get.pow.cx/uninstall.sh | sh

[jathayde]

Is this the same for nginx? We have a hellaciously complex nginx setup for our main apps at work and I can't move to pow.cx yet for that. Those run on dev.domainname.com. Is there a way for pow to only handle *.dev requests?

[sstephenson]

@boboroshi, you could try running Pow without the ipfw rule and setting up an nginx reverse proxy to 127.0.0.1:20559 for *.dev.

[tal]

@sstephenson how do you install w/o the ipfw?

[jerodsanto]

Another option is switching Apache over to IPv6 which is pretty painless. I documented the process here.

[painteddigital]

Reluctantly had to uninstall for this reason. @sant0sk1 has a decent workaround, but it's no solution. I'd love it if you could reserve certain domains or omit folders from Pow's control.

[wizardwerdna]

I share painteddigital's reluctance in adopting an interesting product. I had an old-school Apache/Passenger/Control Panel scheme in effect. Net result was that after installing pow as instructed in the manual, I couldn't get myapp.dev to work, it said that the app wasn't found. Nor could I use the myapp.local, which invited me to do some kind of symlink. The error messages, whatever they meant, were not particularly helpful.

So uninstall it was, passenger worked fine again, and here I am.

You might want to mention this incompatibility in the installation portion, as I have no idea even how or what I need to do, if anything, to test pow in its native habitat.

[paulodeon]

This should be made clear at least on the github homepage. Ciao pow.

[spikex]

I've written up how to use rack-legacy with Pow here:

http://stuff-things.net/2011/05/16/legacy-development-with-pow/

[sstephenson]

@spikex - excellent, thanks! Would you like to add this to the FAQ as well?

[spikex]

Done!

[GoodWriteHQ]

Can't you just set export POW_DST_PORT=81 via .bash_profile?

[kojilab]

having the same issue. Installed Pow, which messed up my virtual hosts. I uninstalled, rebooted and am getting a 503 now. I just don't know where to go from there

[kojilab]

Figured it out. I removed the resolver file and rebooted. That fixed it.

[slant]

Oi, yeah. This is an issue. I need the ability to quickly access one-offs at localhost. Why does pow take over everything instead of only the *.dev hosts? Is there no way to configure pow to whitelist or even blacklist certain hosts from pow's evil, er, masterful clutches?

[itsmattsoria]

I can see this is a longshot, since it's been two years since the last comment. But I'm having the same issue! A friend recommend I try out Anvil, so I did without looking into it too much, and had POW installed with it, then realizing it doesn't work with PHP sites I uninstalled POW and Anvil, and now apache won't run. From the time I installed it to now I have a constant stream of the following message in my apache error log:
[error] Server should be SSL-aware but has no certificate configured [Hint: SSLCertificateFile] ((null):0) - been trying forever to remedy this and I can't figure it out. I tried @kojilab's suggestion of removing the resolver file and rebooting and didn't have the same luck. Anyone have any ideas on this one?

[guidobouman]

https://github.com/37signals/pow/wiki/Running-Pow-with-Apache

[itsmattsoria]

@guidobouman Thanks! I Resolved my own issue, and don't exactly know how (or if?) it relates to my installation of POW, but thanks for pointing out that resource!