And Kurt... you were right. When setting a pixelserver to do DNS-level ad-blocking, I set up a loopback interfaces 192.0.0.2 (It should have been 127.0.0.2) So... yes as github is 192.30... everything was directed to loopback iface, and my apache server was the one answering :S
Thank you for making me think! Felix On Wednesday, 30 December 2015 14:08:19 CET Kurt Roeckx wrote: > On Tue, Dec 29, 2015 at 08:35:49PM +0100, Felix Rubio Dalmau wrote: > > Hi all, > > > > I have been searching for some time for a solution and I can not > > manage to > > solve my problem. I have a computer that can not connect to some sites, > > e.g. > > github, by using openssl. I am running a debian testing with all the > > updates > > available as of today, and libssl used is v1.0.2. If I execute: > > > > > openssl s_client -connect github.com:443 > > The trace file you attached, which claims to go github.com:443, > did send a Client Hello. However the reply is a plain text > "400 Bad Request". It looks like you connected to port 80 and not > 443 for some reason. I suspect something is broken in your network. > > > Kurt > > _______________________________________________ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
