On 11/1/21 7:55 AM, David Touzeau wrote: > The Squid uses the loopback as a parent. > > The same problem occurs: > 06:19:47 kid1| TCP connection to 127.0.0.1/2320 failed > 06:15:13 kid1| TCP connection to 127.0.0.1/2320 failed > 06:14:41 kid1| TCP connection to 127.0.0.1/2320 failed > 06:14:38 kid1| TCP connection to 127.0.0.1/2320 failed > 06:13:15 kid1| TCP connection to 127.0.0.1/2320 failed > 06:11:23 kid1| TCP connection to 127.0.0.1/2320 failed > cache_peer 127.0.0.1 parent 2320 0 name=Peer11 no-query default > connect-timeout=3 connect-fail-limit=5 no-tproxy It is impossible to tell for sure what is going on because Squid does not (unfortunately; yet) report the exact reason behind these connection establishment failures or even the context in which a failure has occurred. You may be able to tell more by collecting/analyzing packet captures. Developers may be able to tell more if you share, say, ALL,5 debugging logs that show what led to the failure report. Alex. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users