-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ssl-bump causes squid service to shutdown #53
Comments
Hello fifthsegment, what is in the squid log? Please post only relevant lines. |
Hi thanks for the fast response. My logs are both empty (access.log and cache.log) with the above configuration line. However if i remove the ssl-bump line and replace it with http_port 3128, both of the log files get filled with logging info. |
ok then what is shown when the following command is run 'squid -k parse' ? |
Can you run it with problematic settings for http_port? |
Thanks for that. I've fixed the cert file and squid now starts, but still I'm unable to browse using the proxy. Here's the cache.log: 2015/12/04 23:28:36 kid1| Set Current Directory to /var/cache/squid |
Turns out I had to initialize a SSL_db in D:/Squid/var/run/squid/lib/ssl_db, not in D:/Squid/var/run/squid/ssl_db, once I did, everything started working like a charm. Thanks for the help :) |
I've come across this problem. my error log: do you help me? |
Hello wanggaolin, Sorry we only build squid binaries and make MSI out of it. I vaguely remember there is a bug in cygwin that somehow prevents any squid external helper from functioning properly. See nodejs/node-v0.x-archive#6459 I am not sure what can be done. |
How to enable HTTPS description on Windows is described in the following tutorial |
I'm trying to perform MITM using Squid3 on Windows. Here's my ssl-bump line, which is copied from my working squid3 on ubuntu, I've just changed the cert path here:
http_port 3128 ssl-bump generate-host-certificates=on dynamic_cert_mem_cache_size=4MB cert=/cygdrive/d/Squid/etc/ssl/cert.pem
If I remove the ssl-bump line (and everything related to it) the proxy starts working fine. Does anyone else face this issue too?
The text was updated successfully, but these errors were encountered: