[squid-users] ERR_TUNNEL_CONNECTION_FAILED

Ralf Hildebrandt Ralf.Hildebrandt at charite.de
Mon Oct 5 14:06:06 UTC 2020


I'm getting "ERR_TUNNEL_CONNECTION_FAILED" errors in Chrome when
connecting to https://securefiles.laborberlin.com/

Squid logs:

1601906504.874      0 141.42.231.251 NONE_NONE/500 0 CONNECT securefiles.laborberlin.com:443 - HIER_NONE/- - accessRule=- -
1601906505.047      0 141.42.231.251 NONE_NONE/500 0 CONNECT securefiles.laborberlin.com:443 - HIER_NONE/- - accessRule=- -
1601906505.225      0 141.42.231.251 NONE_NONE/500 0 CONNECT securefiles.laborberlin.com:443 - HIER_NONE/- - accessRule=- -

The squid process should be able to resolve the hostname...

I explicitly set an dns_nameservers entry, like this:
dns_nameservers 141.42.5.156 141.42.5.157

Testin on the squid machine:

# dig +short @141.42.5.156 securefiles.laborberlin.com 
607748248.dracoon.cloud.
# dig +short @141.42.5.156 607748248.dracoon.cloud
213.95.134.242

# dig +short @141.42.5.157 securefiles.laborberlin.com
607748248.dracoon.cloud.
# dig +short @141.42.5.157 607748248.dracoon.cloud
213.95.134.242

So what is the reason for the NONE_NONE/500 error?


Ralf Hildebrandt
Charité - Universitätsmedizin Berlin
Geschäftsbereich IT | Abteilung Netzwerk

Campus Benjamin Franklin (CBF)
Haus I | 1. OG | Raum 105
Hindenburgdamm 30 | D-12203 Berlin

Tel. +49 30 450 570 155
ralf.hildebrandt at charite.de
https://www.charite.de


More information about the squid-users mailing list