Re: [squid-users] No valid signing SSL certificate configured for HTTPS_port

2023-09-28 Thread Alex Rousskov
On 2023-09-28 00:52, Bud Miljkovic wrote: # Intercept tranparent HTTPS traffic https_port 3129 intercept ssl-bump ssl_bump splice all This should be refactored into two lines: https_port 3129 intercept ssl-bump ... ssl_bump splice all After that, replace "..." above with cert=...

[squid-users] No valid signing SSL certificate configured for HTTPS_port

2023-09-27 Thread Bud Miljkovic
Would you know anything about this Squid problem? Given the squid-ota.conf file: ``` # An ACL named 'whitelist' acl whitelist dstdomain '/etc/squid/whitelist.ota' # Allow whitelisted URLs through http_access allow whitelist # Block the rest http_access deny all # Intercept tranparent HTTPS

[squid-users] No valid signing SSL certificate configured for HTTPS_port [::]:3128 (SSL Bump)

2017-05-09 Thread Mohammed al-jakry
Hi, I am facing an issue with Squid 3.5 with SSL Bump configuration, i already configure it without SSL bump and it works fine. but after configuring intercept process it shows the below error: *No valid signing SSL certificate configured for HTTPS_port [::]:3128* below snippet from the Squid

Re: [squid-users] No valid signing SSL certificate configured for HTTPS_port

2016-11-08 Thread konradka
Hi Amos, This could be the problem. I built another VM based on Debian and ended up creating my own CA / PKI. Self-signed certificates worked and I was able to move on at last. Great learning experience to see how SSL / openssl works. Now I am stuck with Windows client unable to connect to

Re: [squid-users] No valid signing SSL certificate configured for HTTPS_port

2016-11-07 Thread Amos Jeffries
On 6/11/2016 7:52 a.m., Garri Djavadyan wrote: > On 2016-11-05 23:10, konradka wrote: >> Hi Garri, >> >> Thanks for your responses mate ! >> >> I did not realize that the squid was compiled with proxy user. Well >> spotted >> ! >> >> It looks like permission's issue but squid error message is not

Re: [squid-users] No valid signing SSL certificate configured for HTTPS_port

2016-11-05 Thread Garri Djavadyan
On 2016-11-05 23:10, konradka wrote: Hi Garri, Thanks for your responses mate ! I did not realize that the squid was compiled with proxy user. Well spotted ! It looks like permission's issue but squid error message is not giving away any more details. I will configure debug_options to

Re: [squid-users] No valid signing SSL certificate configured for HTTPS_port

2016-11-05 Thread Garri Djavadyan
On 2016-11-05 22:09, Garri Djavadyan wrote: 1. Does your certificate signed by StartSSL CA (/home/kk/ssl/cert-mail/mail.contoso.com.pem) corresponds to your private key (/home/kk/ssl/cert-mail/mail.contoso.com.key)? For the 'corresponds' I mean, does CSR for StartSSL was generated using

Re: [squid-users] No valid signing SSL certificate configured for HTTPS_port

2016-11-05 Thread Garri Djavadyan
On 2016-11-05 21:24, Konrad Kaluszynski wrote: Hi All, My goal is to configure a reverse proxy for Outlook Anywhere clients using squid. http://wiki.squid-cache.org/ConfigExamples/Reverse/ExchangeRpc This will replace existing TMG that my client is currently using. However, when I run squid I

[squid-users] No valid signing SSL certificate configured for HTTPS_port

2016-11-05 Thread Konrad Kaluszynski
Hi All, My goal is to configure a reverse proxy for Outlook Anywhere clients using squid. http://wiki.squid-cache.org/ConfigExamples/Reverse/ExchangeRpc This will replace existing TMG that my client is currently using. However, when I run squid I get an error "No valid signing SSL certificate