Yeah, great idea...now the log looks a little different: CRL: verification passed 2011.11.18 14:33:22 LOG5[2517:3077962608]: VERIFY OK: depth=2, /C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=(c) 2006 VeriSign, Inc. - For authorized use only [...and so on...] But at the end, same as usual: 2011.11.18 14:33:22 LOG3[2517:3077962608]: SSL_connect: 14094415: error:14094415:SSL routines:SSL3_READ_BYTES:sslv3 alert certificate expired 2011.11.18 14:33:22 LOG5[2517:3077962608]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket Maybe there is another reason, why I cant connect? Maybe the lines 2011.11.18 14:33:22 LOG5[2517:3077962608]: connect_blocking: connected example.com:443 2011.11.18 14:33:22 LOG5[2517:3077962608]: https connected remote server from my_outsid_ip:38491 are messing something? -Rolf ________________________________ From: "[email protected]" <[email protected]> To: Rolf Ruediger <[email protected]> Sent: Friday, November 18, 2011 2:18 PM Subject: Re: [stunnel-users] expired certificate problem Rolf, Try verify = 0 Regards -----Original Message----- From: Rolf Ruediger <[email protected]> Sender: [email protected] Date: Fri, 18 Nov 2011 05:15:33 To: [email protected]<[email protected]> Reply-To: Rolf Ruediger <[email protected]> Subject: Re: [stunnel-users] expired certificate problem _______________________________________________ stunnel-users mailing list [email protected] http://stunnel.mirt.net/mailman/listinfo/stunnel-users