Using secure proxies with Google Chrome
Posted
by
cYrus
on Super User
See other posts from Super User
or by cYrus
Published on 2012-10-17T16:46:50Z
Indexed on
2012/10/17
17:05 UTC
Read the original article
Hit count: 413
Whenever I use a secure proxy with Google Chrome I get ERR_PROXY_CERTIFICATE_INVALID
, I tried a lot of different scenarios and versions.
The certificate
I'm using a self-signed certificate:
openssl genrsa -out key.pem 1024
openssl req -new -key key.pem -out request.pem
openssl x509 -req -days 30 -in request.pem -signkey key.pem -out certificate.pem
Note: this certificate works (with a warning since it's self-signed) when I try to setup a simple HTTPS server.
The proxy
Then I start a secure proxy on localhost:8080
. There are a several ways to accomplish this, I tried:
- a custom Node.js script;
- stunnel;
- node-spdyproxy (OK, this involves SPDY too, but later... the problem is the same);
- [...]
The browser
Then I run Google Chrome with:
google-chrome --proxy-server=https://localhost:8080 http://superuser.com
to load, say, http://superuser.com
.
The issue
All I get is:
Error 136 (net::ERR_PROXY_CERTIFICATE_INVALID): Unknown error.
in the window, and something like:
[13633:13639:1017/182333:ERROR:cert_verify_proc_nss.cc(790)] CERT_PKIXVerifyCert for localhost failed err=-8179
in the console.
Note: this is not the big red warning that complains about insecure certificates.
Now, I have to admit that I'm quite n00b for what concerns certificates and such, if I'm missing some fundamental points, please let me know.
© Super User or respective owner