Post
Topic
Board Announcements (Altcoins)
Re: BITCREDIT | URGENT UPDATE Dec. 11 2015
by
sulfurtank
on 15/12/2015, 15:50:08 UTC
2015-12-15 11:58:59 GUI: QSslSocket: cannot resolve TLSv1_1_client_method
2015-12-15 11:58:59 GUI: QSslSocket: cannot resolve TLSv1_2_client_method
2015-12-15 11:58:59 GUI: QSslSocket: cannot resolve TLSv1_1_server_method
2015-12-15 11:58:59 GUI: QSslSocket: cannot resolve TLSv1_2_server_method
2015-12-15 11:58:59 GUI: QSslSocket: cannot resolve SSL_select_next_proto
2015-12-15 11:58:59 GUI: QSslSocket: cannot resolve SSL_CTX_set_next_proto_select_cb
2015-12-15 11:58:59 GUI: QSslSocket: cannot resolve SSL_get0_next_proto_negotiated
2015-12-15 11:59:00 receive version message: /Section32:0.30.19.1/: version 70014, blocks=266996, us=73.153.116.122:8877, peer=1, blockchain=Bitcredit
2015-12-15 11:59:00 Added time data, samples 2, offset -1439 (-23 minutes)
2015-12-15 11:59:00 Misbehaving: 188.193.111.112:49710 (0 -> 1)
2015-12-15 11:59:00 ProcessMessage(version, 132 bytes) FAILED peer=1
2015-12-15 11:59:01 GUI: PaymentServer::LoadRootCAs : Loaded  48  root certificates
2015-12-15 11:59:01 GUI: libpng warning: iCCP: known incorrect sRGB profile
2015-12-15 11:59:01 GUI: libpng warning: iCCP: known incorrect sRGB profile
2015-12-15 11:59:01 GUI: libpng warning: iCCP: known incorrect sRGB profile
2015-12-15 11:59:01 GUI: libpng warning: iCCP: known incorrect sRGB profile
2015-12-15 11:59:01 GUI: libpng warning: iCCP: known incorrect sRGB profile
2015-12-15 11:59:01 GUI: libpng warning: iCCP: known incorrect sRGB profile
2015-12-15 11:59:01 GUI: libpng warning: iCCP: known incorrect sRGB profile

my log is quickly becoming gigs of nothing but  GUI: libpng warning: iCCP: known incorrect sRGB profile
my windows 10 machine does not make outgoing connection after this...
socket recv error An established connection was aborted by the software in your host machine.  (10053)
but no connection is attempted outside the program...


Seems like OS repeatedly closes the connection when reading response from a web server. I had the similar issue, something is up with your router / firewall settings. If you have any firewalls running you may wish to turn them off.