basecamp / powprox Goto Github PK

After running the bin/powprox install,
chrome (and safari) is not trusting the cert, I get a

NET::ERR_CERT_AUTHORITY_INVALID

Subject: Pow development server

Issuer: Pow development root

I do see a the test root CA cert Pow development root in my Keychain and it is trusted.

My workaround is to manually import the server cert and mark it as trusted.

Is there any way around this?

The script seems to be waiting for some sort of input, but I have no idea what to enter:

$ ./bin/powprox
Pow server names unchanged. Using existing server certificate.
Checking for Nginx… installed with HTTP/2 support.
Checking Nginx config…
nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Launching Nginx
Nginx self-test…
Pow upstream: {"pid":1219,"version":"0.6.0","requestCount":169}
Pow with pf port forward: {"pid":1219,"version":"0.6.0","requestCount":170}
Nginx TLS proxy:

(this is on High Sierra 10.13.6)

Cool repo. Everything works for me, except that I have to touch ~/.pow/restart.txt after every page load. If I don't, every subsequent page load request seems to go off in the weeds and generally 504's. If I switch over to HTTP, everything works as expected - it only happens with HTTPS. Any ideas?

On OSX 10.10.5 Yosemite MBP Mid 2015 at 0f7c102

I've had issues with chrome not trusting the server cert

powprox-create-root-cata runs security add-trusted-cert -d -r trustRoot -k "$HOME/Library/Keychains/login.keychain" "$POWPROX_DIR/ssl/ca/pow-root-ca.crt"

but powprox-create-server-certificate does not.

I had been doing some manual stuff

# UNTRUSTED CERT IN CHROME
# Search pow in Keychain.
# If present, click, command+I, edit trust settings to always trust
# Else,
#  1. click on the https with the / through it in the address bar
#  2. click view certificate
#  3. drag the picture of the cert to the desktop (or another folder)
#  4. double click it to import it to the Keychain
#  5. edit trust settings to always trust as above
#
# Else restart chrome
# go to 'chrome://flags' and
# Try: Enable 'Allow invalid certificates for resources loaded from localhost.'
# Try: 'Mark non-secure origins as non-secure' as 'neutral'

but why doesn't the script sudo security add-trusted-cert -d -r trustRoot -k "$HOME/Library/Keychains/login.keychain" "$POWPROX_DIR/ssl/certs/pow-server.crt". Am I doing something wrong?

Also, I had to

  # https://github.com/basecamp/pow/issues/480#issuecomment-62254317
  sudo sysctl -w net.inet.ip.forwarding=1;
  sudo echo "rdr pass proto tcp from any to any port {80,20559} -> 127.0.0.1 port 20559" | sudo pfctl -a "com.apple/250.PowFirewall" -Ef -
  # sudo pfctl -f /etc/pf.conf; sudo pfctl -e

to get the port 80 forwarding working.

In debugging this, I ended up writing a setup-pow script to uninstall everything, reinstall it, and confirm success. It's not perfect but has worked for me when something goes wrong for unknown reasons.

Thanks for this!

I am getting the following when attempting to run bin/powprox:

nginx: [emerg] "http" directive is duplicate in /usr/local/etc/nginx/conf.d/powprox.conf:4
nginx: configuration file /usr/local/etc/nginx/nginx.conf test failed

Any ideas what I might be able to do to fix?

Thanks again.

Upon cloning and running ./bin/powprox as per instructions I'm met with the following error:

mktemp: too few X's in template ‘generate-nginxreloader-launchdaemon’.

I will submit a pull request with a fix imminently.

Thanks for making powprox, it's made development easier for me. Unfortunately I'm currently running into some issues which I've traced down to powprox. I'm running osx 10.11.4.

Accessing the .dev domain with http it works, but with https some of the "later" resources (such as @imports in css files & images) fail with a 503 result. The images & css files aren't big (< 1MB), and there are only about 20 total requests, of which ~6 fail.

I've updated the nginx config to write an error log, in which the following message matches requests returning 503: an upstream response is buffered to a temporary file /usr/local/var/run/nginx/proxy_temp/1/16/0000000161 while reading upstream. I tried applying various fixes I found online to no avail.

The requests in question - I'm looking in the browser's network inspector - have the same request headers, but fewer response headers, specifically: status: 503, server: nginx/1.10.2, date, content-type, and x-pow-template:application_not_found. My guess is that the proxy configuration isn't setup to handle file buffered responses, but I'm not sure how to verify or resolve it.

I installed powprox in August, and am not sure how to update or uninstall it.

Thanks,
Magnus

Thanks for creating powprox! -

I tried a plain vanilla setup with nginx installed via homebrew, and get an error running powprox:

Checking Nginx config…
nginx: [emerg] "user" directive is not allowed here in /usr/local/etc/nginx/servers/powprox.conf:2
nginx: configuration file /usr/local/etc/nginx/nginx.conf test failed

any help?