[squid-users] To many ERR_CANNOT_FORWARD

[Amos Jeffries]

On 24/08/23 00:42, Andre Bolinhas wrote:
> Hi
> 
> I'm using squid 5.2 but stating yesterday I'm getting too many errors 
> ERR_CANNOT_FORWARD for random websites.
> 

FYI, current Squid is 6.2 with 6.3 due out next week. Squid-5.x are 
officially end-of-life now.


> What's could be the issue?
> 
> This is an extract of debug log
> 


> 2023/08/22 15:50:28.564 kid1| 5,4| AsyncCallQueue.cc(61) fireNext: 
> leaving TunnelBlindCopyReadHandler(conn6384669 local=10.100.16.37:18006 
> remote=20.90.216.0:443 HIER_DIRECT flags=1, data=0x56227564b5a8, size=0, 
> buf=0x562275f76900)

One endpoint (20.90.216.0) of a CONNECT tunnel delivered the "end of 
connection" signal to Squid.

It looks like the server disconnected. Likely without having sent any 
actual protocol level response.


> 2023/08/22 15:50:28.564 kid1| 5,4| AsyncCallQueue.cc(59) fireNext: 
> entering tunnelServerClosed(FD -1, data=0x56227564b5a8)
> 2023/08/22 15:50:28.564 kid1| 5,4| AsyncCall.cc(42) make: make call 
> tunnelServerClosed [call56950820]
> 2023/08/22 15:50:28.564 kid1| 26,3| tunnel.cc(752) noteClosure: 
> conn6384669 local=10.100.16.37:18006 remote=20.90.216.0:443 HIER_DIRECT 
> flags=1
> 2023/08/22 15:50:28.564 kid1| 46,5| access_log.cc(308) stopPeerClock: 
> First connection started: 1692715828.514861, current total response time 
> value: -1000
> 2023/08/22 15:50:28.564 kid1| 26,4| tunnel.cc(1338) saveError: [none] ? 
> ERR_CANNOT_FORWARD


That negative response time looks a bit weird. Maybe just a display bug, 
or your machines NTP clock doing some "time travel" that makes Squid 
think an error happened.


Amos