[squid-users] failed to bump Twitter

[Amos Jeffries]

On 01/06/17 09:49, Vieri wrote:
> Hi,
>
> I can't seem to be able to bump Twitter.
>
> Whenever a client tries to browse https://twitter.com there's a connection refusal error page (111).
>
> Any clue as to what I could try?

Squid is simply not able to make outbound TCP connections to twitter.com 
(which according to your OS is hosted by 199.16.156.6). Without a TCP 
connection it cannot get the TLS cert details to use when bumping.


> # cat /var/log/squid/access.test.log
>
> 1496266616.296    200 10.215.144.48 TAG_NONE/200 0 CONNECT 199.16.156.6:443 - ORIGINAL_DST/199.16.156.6 -
> 1496266616.322      2 10.215.144.48 TAG_NONE/503 3902 GET https://twitter.com/ - HIER_NONE/- text/html
>
> # cat /var/log/squid/cache.test.log
>
> 2017/05/31 23:36:56.095 kid1| 11,2| client_side.cc(2345) parseHttpRequest: HTTP Client local=199.16.156.6:443 remote=10.215.144.48 FD 13 flags=17
> 2017/05/31 23:36:56.095 kid1| 11,2| client_side.cc(2346) parseHttpRequest: HTTP Client REQUEST:
> ---------
> CONNECT 199.16.156.6:443 HTTP/1.1
> Host: 199.16.156.6:443
>
>
> ----------

> 2017/05/31 23:36:56.293 kid1| 5,5| ConnOpener.cc(365) doConnect: local=10.215.144.48 remote=199.16.156.6:443 flags=25: * - ERR tried too many times already.

> 2017/05/31 23:36:56.293 kid1| 17,3| FwdState.cc(415) fail: ERR_CONNECT_FAIL "Service Unavailable"
> 199.16.156.6:443
> 2017/05/31 23:36:56.293 kid1| 17,3| FwdState.cc(616) retryOrBail: re-forwarding (0 tries, 0 secs)
> 2017/05/31 23:36:56.293 kid1| 17,3| FwdState.cc(386) startConnectionOrFail: 199.16.156.6:443
> 2017/05/31 23:36:56.293 kid1| 17,3| FwdState.cc(403) startConnectionOrFail: Connection failed: 199.16.156.6:443


Amos