thanks Alex
seems like one client (it shows the ip) is trying to get to this site but i
havnt added it to my white list, so thats why its getting blocked
events.gfe.nvidia.com
thanks a bunch alex, your awesome
On Wed, 30 Jun 2021 at 17:09, Alex Rousskov <
rouss...@measurement-factory.com>
On 6/30/21 11:48 AM, robert k Wild wrote:
> How do I enable all 9 debugging to find out what client ip it is thats
> sending all these tls errors.
0. Start Squid if necessary.
1. Locate your Squid log file or equivalent. In this example, we will
call it cache.log.
2. Run "tail -f cache.log > pa
Cool, so I put this in squid.conf
debug_options 9
And then restart squid and tail the cache.log
On Wed, 30 Jun 2021, 16:48 robert k Wild, wrote:
> Thanks Alex,
>
> How do I enable all 9 debugging to find out what client ip it is thats
> sending all these tls errors.
>
> There's a lot of mac/p
Thanks Alex,
How do I enable all 9 debugging to find out what client ip it is thats
sending all these tls errors.
There's a lot of mac/pcs that are connected to this squid server and I have
added the myca.der file to there machines as I'm doing ssl bumping.
Thanks,
Rob
On Wed, 30 Jun 2021, 16
On 6/30/21 6:41 AM, robert k Wild wrote:
> never really noticed this as i rarely "tail -f" the cache log but im
> noticing these lines like every second
> 2021/06/30 11:39:13 kid1| Error negotiating SSL connection on FD 266:
> error:0001:lib(0):func(0):reason(1) (1/-1)
> 2021/06/30 11:39:13 k
hi all,
never really noticed this as i rarely "tail -f" the cache log but im
noticing these lines like every second
2021/06/30 11:39:13 kid1| Error negotiating SSL connection on FD 266:
error:0001:lib(0):func(0):reason(1) (1/-1)
2021/06/30 11:39:13 kid1| Error negotiating SSL connection on FD
On 2/04/20 5:42 pm, saiyan_gc wrote:
> Hi, thank you for reply me. Really appreciated!
>
> I modified the squid conf file to:
>
> http_port 2128 ssl-bump cert=/etc/squid/ssl_cert/example.com.cert \
> key=/etc/squid/ssl_cert/example.com.private \
> generate-host-certificates=on \
> dyn
Hi, thank you for reply me. Really appreciated!
I modified the squid conf file to:
http_port 2128 ssl-bump cert=/etc/squid/ssl_cert/example.com.cert \
key=/etc/squid/ssl_cert/example.com.private \
generate-host-certificates=on \
dynamic_cert_mem_cache_size=4MB
https_port 3130 cert=/et
On 30/03/20 11:58 am, saiyan_gc wrote:
> Hi, I am trying to setup a https proxy server, and after I followed some
> tutorial,
Which tutorial?
> created self signed certificate, configure the squid.conf, I also
> copied the certificate to the client host
Which certificate?
Where did you put it
Hi, I am trying to setup a https proxy server, and after I followed some
tutorial, created self signed certificate, configure the squid.conf, I also
copied the certificate to the client host and setup the https_proxy global
environment variable, I can do *curl https://www.google.com*. I saw
"172.16
Hi,
for know... how you do
Amos Jeffries wrote
> define some ACL to identify the qtox traffic you might be
> able to splice it.
i mean, that kind of ACL·
Thanks
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Error-negotiating-SSL-tp4680491p4680538.htm
On 17/11/2016 5:58 a.m., piequiex wrote:
>> On Mon, 2016-11-14 at 16:12 +, piequiex wrote:
>>> What mean this error and how to fix it?
>>> Error negotiating SSL on FD 29:
>>> error::lib(0):func(0):reason(0) (5/-1/104)
>>> Error negotiating SSL on FD 30:
>>> error::lib(0):func(0)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> On Mon, 2016-11-14 at 16:12 +, piequiex wrote:
> > What mean this error and how to fix it?
> > Error negotiating SSL on FD 29:
> > error::lib(0):func(0):reason(0) (5/-1/104)
> > Error negotiating SSL on FD 30:
> > error::lib(0):fu
On Mon, 2016-11-14 at 16:12 +, piequiex wrote:
> What mean this error and how to fix it?
> Error negotiating SSL on FD 29:
> error::lib(0):func(0):reason(0) (5/-1/104)
> Error negotiating SSL on FD 30:
> error::lib(0):func(0):reason(0) (5/-1/104)
Hi,
Please provide more inform
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What mean this error and how to fix it?
Error negotiating SSL on FD 29: error::lib(0):func(0):reason(0)
(5/-1/104)
Error negotiating SSL on FD 30: error::lib(0):func(0):reason(0)
(5/-1/104)
- --
0x16E684E1A170D8A3
~~~
This PGP sign
On 4/02/2016 4:11 p.m., xxiao8 wrote:
> I'm running squid/3.5.13/sslbump/intercept and saw the below when
> visiting gmail.com from Chrome 48, gmail.com can not be opened.
>
> However Firefox works fine, no errors in the log, gmail.com opens as
> expected.
>
> Error in the log:
> ==
>
I'm running squid/3.5.13/sslbump/intercept and saw the below when
visiting gmail.com from Chrome 48, gmail.com can not be opened.
However Firefox works fine, no errors in the log, gmail.com opens as
expected.
Error in the log:
==
Error negotiating SSL on FD 22:
error:140920F8:lib
Thanks a lot for your Answer Amos,
My mistake,
I have to use intercept and use squid as transparent proxy (I was lazy to
setup a router, setup transparent proxy m/c. I should do it now.).
I have changed the configuration to use http_port instead of https_port and
then removed "intercept". this w
On 6/05/2015 10:31 p.m., Ashish Behl wrote:
> I an encountering the same issue.
>
> Using squid 3.5.4 inside docker container, I have set up proxy in my browser
> to point to the squid proxy port.
> I have also seperated the HTTP and HTTPS ports in squid as well as in
> browser.
> Full details of
I an encountering the same issue.
Using squid 3.5.4 inside docker container, I have set up proxy in my browser
to point to the squid proxy port.
I have also seperated the HTTP and HTTPS ports in squid as well as in
browser.
Full details of the error are on stackoverflow:
http://stackoverflow.com/q
You're experiencing http://bugs.squid-cache.org/show_bug.cgi?id=4236 -
give the patch on there a try and see if it helps. It should tell you
what's really failing.
You'll start getting messages like this:
Error negotiating SSL connection on FD 439:
error:0005:lib(0):func(0):DH lib (5/-1/0)
W
Hi
I created privste & public keys for squid , but it still give me error for
negotiating
https_port 443 accel key=/root/CA/myCA/private/squid.local.key
cert=/root/CA/myCA/certs/squid.local.crt
cache.log
2015/05/04 11:59:08 kid1| Error negotiating SSL connection on FD 12: Succes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm ignoring this message.
All pages are loading. This is error 131 from openssl.
12.04.15 0:09, mattatrmc пишет:
> Hi Yuri,
>
> I just got my Squid up and running on a fairly active test
environment, and
> am seeing the same error printed. Did
Hi Yuri,
I just got my Squid up and running on a fairly active test environment, and
am seeing the same error printed. Did you ever figure out what was causing
the errors? It appears that the pages that are requested are still loading,
it just appears to be happening more slowly.
Cheers,
Matt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Not yet. Works on it.
29.01.2015 4:54, HackXBack пишет:
> You solve It ?
>
>
>
> --
> View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Error-negotiating-SSL-connection-on-FD-20-error--lib-0-func-0-reason-0-5-1
You solve It ?
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Error-negotiating-SSL-connection-on-FD-20-error--lib-0-func-0-reason-0-5-1-131-tp4669338p4669397.html
Sent from the Squid - Users mailing list archive at Nabble.com.
__
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
131 error means:
CONNECTED(0003)
write:errno=131
- ---
no peer certificate available
- ---
No client certificate CA names sent
- ---
SSL handshake has read 0 bytes and written 148 bytes
- ---
New, (NONE), Cipher is (NONE)
Looks like something i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I suggest we are asking in wrong place :)
This is OpenSSL error stack, not squid.
Also, man, which root CA bundle you are use in your installation?
27.01.2015 2:49, HackXBack пишет:
> when you know tell me because i asked this question before here
when you know tell me because i asked this question before here and i didnt
get any answer
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Error-negotiating-SSL-connection-on-FD-20-error--lib-0-func-0-reason-0-5-1-131-tp4669338p4669351.html
Sent from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After a bit Google-Fu ;)
I found this:
http://stackoverflow.com/questions/14770100/libssl-read-error-131-causing-an-application-crash
Is that it?
26.01.2015 23:22, Yuri Voinov пишет:
>
> Hi gents,
>
> who know, what this log messages mean:
>
> 20
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi gents,
who know, what this log messages mean:
2015/01/26 22:02:34 kid1| fwdNegotiateSSL: Error negotiating SSL
connection on FD 20: error::lib(0):func(0):reason(0) (5/-1/131)
2015/01/26 22:02:41 kid1| fwdNegotiateSSL: Error negotiating S
with this error https pages some times open and some times no
maybe there is any solution ?
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Error-negotiating-SSL-connection-tp4668748p4668801.html
Sent from the Squid - Users mailing list archive at Nabble.com
2014/12/18 06:16:13 kid1| fwdNegotiateSSL: Error negotiating SSL connection
on FD 86: error::lib(0):func(0):reason(0) (5/0/0)
2014/12/18 06:16:13 kid1| fwdNegotiateSSL: Error negotiating SSL connection
on FD 91: error::lib(0):func(0):reason(0) (5/0/0)
2014/12/18 06:16:13 kid1| fwdNe
33 matches
Mail list logo
