Strange errors / HTTPS handshake failed / fiddler.network.readresponse.failure errors / etc.
3,316 views
Skip to first unread message
Raduc
Dec 23, 2014, 5:53:24 AM12/23/14
to httpf...@googlegroups.com
Hi,
I am starting tot get these weird errors from some time now for some domains.
Without any change to custom rules or anything else in Fiddler I start receiving errors such as the above on three servers all running Windows Standard 2012 R2 server. No changes were done on clients browsers and PCs - I am running Windows 7, as well as Windows 8.1 - nor in the server configuration if that matters.
I use Fiddler4 (vers. v4.4.9.8) on three different servers using Windows Standard 2012 R2. I removed the certificate and reissue another one using the documentation. Installed the new certificate in the client browser (Firefox last vers. - 34.0.5) as per documentation (adding it in the Options > Advanced > Certificates > Authorities and marking its trust for websites only) I also uninstalled and reinstalled Fiddler.
I even changed some things as suggested on some sites to about:config prefs. Please find attached a screenshot.
Some sites are giving errors as such from below while others do not. It seems to me that errors are random because sometimes I don't get any from the domains I browse to, and then suddenly they come back for the same domains!
Fiddler Web Debugger (v4.4.9.8)
Built: Thursday, December 18, 2014
64-bit AMD64, VM: 62.00mb, WS: 89.00mb
.NET 4.0.30319.34014 WinNT 6.3.9600.0
You've run Fiddler: 14 times.
Running ELEVATED on: win-efqkh6hsk2g:8888
Listening to: DefaultLAN
Gateway: No Gateway
Start list of errors:
Fiddler.CertMaker> Root Certificate located; private key in container '7b90a71bfc56f2582e916a51aed6df9a_96646cf4-fa2c-4279-b935-066b9872443b'
11:02:17:3074 /Fiddler.CertMaker> Invoking makecert.exe with arguments: -pe -ss my -n "CN=blahblahblah, O=DO_NOT_TRUST, OU=Created by http://www.fiddler2.com" -sky exchange -in DO_NOT_TRUST_FiddlerRoot -is my -eku 1.3.6.1.5.5.7.3.1 -cy end -a sha256 -m 132 -b 12/22/2013
11:02:17:5418 /Fiddler.CertMaker>153-CreateCert(site.com) => (0).
11:02:20:3843 [Fiddler] No HTTP request was received from () new client socket, port 57792.
11:02:22:3785 [Fiddler] No HTTP request was received from () new client socket, port 57802.
11:21:50:9640 [Fiddler] No HTTP request was received from () new client socket, port 50865.
11:22:04:8576 fiddler.network.https> HTTPS handshake to site.com failed. System.IO.IOException Authentication failed because the remote party has closed the transport stream.
11:22:14:1995 fiddler.network.https> HTTPS handshake to site.com failed. System.IO.IOException Authentication failed because the remote party has closed the transport stream.
11:22:42:3274 [Fiddler] No HTTP request was received from () new client socket, port 50906.
11:22:42:3274 [Fiddler] No HTTP request was received from () new client socket, port 50905.
11:22:42:3274 [Fiddler] No HTTP request was received from () new client socket, port 50896.
11:22:42:3274 [Fiddler] No HTTP request was received from () new client socket, port 50914.
11:22:42:3274 [Fiddler] No HTTP request was received from () new client socket, port 50902.
11:22:42:3274 [Fiddler] No HTTP request was received from () new client socket, port 50915.
11:22:42:3431 fiddler.network.readresponse.failure> Session #15679 raised exception System.IO.IOException Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. < An existing connection was forcibly closed by the remote host
11:22:43:1243 fiddler.network.readresponse.failure> Session #15693 raised exception System.IO.IOException Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. < An existing connection was forcibly closed by the remote host
11:23:03:6460 fiddler.network.https> HTTPS handshake to site.com failed. System.IO.IOException Authentication failed because the remote party has closed the transport stream.
11:23:05:3189 fiddler.network.https> HTTPS handshake to site.com failed. System.IO.IOException Authentication failed because the remote party has closed the transport stream.
11:23:05:6466 fiddler.network.https> HTTPS handshake to site.com failed. System.IO.IOException Authentication failed because the remote party has closed the transport stream.
11:23:07:4432 [Fiddler] No HTTP request was received from () new client socket, port 52325.
11:23:25:3327 fiddler.network.readresponse.failure> Session #15817 raised exception System.IO.IOException Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. < A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
11:23:52:6380 [Fiddler] No HTTP request was received from () new client socket, port 61327.
I read a lot about this kind of errors and tried all given solutions (even if just similarly with mines) without luck.
If anybody can shade some light on what's going one here, that will be great.
Thanks.
I am starting tot get these weird errors from some time now for some domains.
Without any change to custom rules or anything else in Fiddler I start receiving errors such as the above on three servers all running Windows Standard 2012 R2 server. No changes were done on clients browsers and PCs - I am running Windows 7, as well as Windows 8.1 - nor in the server configuration if that matters.
I use Fiddler4 (vers. v4.4.9.8) on three different servers using Windows Standard 2012 R2. I removed the certificate and reissue another one using the documentation. Installed the new certificate in the client browser (Firefox last vers. - 34.0.5) as per documentation (adding it in the Options > Advanced > Certificates > Authorities and marking its trust for websites only) I also uninstalled and reinstalled Fiddler.
I even changed some things as suggested on some sites to about:config prefs. Please find attached a screenshot.
Some sites are giving errors as such from below while others do not. It seems to me that errors are random because sometimes I don't get any from the domains I browse to, and then suddenly they come back for the same domains!
Fiddler Web Debugger (v4.4.9.8)
Built: Thursday, December 18, 2014
64-bit AMD64, VM: 62.00mb, WS: 89.00mb
.NET 4.0.30319.34014 WinNT 6.3.9600.0
You've run Fiddler: 14 times.
Running ELEVATED on: win-efqkh6hsk2g:8888
Listening to: DefaultLAN
Gateway: No Gateway
Start list of errors:
Fiddler.CertMaker> Root Certificate located; private key in container '7b90a71bfc56f2582e916a51aed6df9a_96646cf4-fa2c-4279-b935-066b9872443b'
11:02:17:3074 /Fiddler.CertMaker> Invoking makecert.exe with arguments: -pe -ss my -n "CN=blahblahblah, O=DO_NOT_TRUST, OU=Created by http://www.fiddler2.com" -sky exchange -in DO_NOT_TRUST_FiddlerRoot -is my -eku 1.3.6.1.5.5.7.3.1 -cy end -a sha256 -m 132 -b 12/22/2013
11:02:17:5418 /Fiddler.CertMaker>153-CreateCert(site.com) => (0).
11:02:20:3843 [Fiddler] No HTTP request was received from () new client socket, port 57792.
11:02:22:3785 [Fiddler] No HTTP request was received from () new client socket, port 57802.
11:21:50:9640 [Fiddler] No HTTP request was received from () new client socket, port 50865.
11:22:04:8576 fiddler.network.https> HTTPS handshake to site.com failed. System.IO.IOException Authentication failed because the remote party has closed the transport stream.
11:22:14:1995 fiddler.network.https> HTTPS handshake to site.com failed. System.IO.IOException Authentication failed because the remote party has closed the transport stream.
11:22:42:3274 [Fiddler] No HTTP request was received from () new client socket, port 50906.
11:22:42:3274 [Fiddler] No HTTP request was received from () new client socket, port 50905.
11:22:42:3274 [Fiddler] No HTTP request was received from () new client socket, port 50896.
11:22:42:3274 [Fiddler] No HTTP request was received from () new client socket, port 50914.
11:22:42:3274 [Fiddler] No HTTP request was received from () new client socket, port 50902.
11:22:42:3274 [Fiddler] No HTTP request was received from () new client socket, port 50915.
11:22:42:3431 fiddler.network.readresponse.failure> Session #15679 raised exception System.IO.IOException Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. < An existing connection was forcibly closed by the remote host
11:22:43:1243 fiddler.network.readresponse.failure> Session #15693 raised exception System.IO.IOException Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. < An existing connection was forcibly closed by the remote host
11:23:03:6460 fiddler.network.https> HTTPS handshake to site.com failed. System.IO.IOException Authentication failed because the remote party has closed the transport stream.
11:23:05:3189 fiddler.network.https> HTTPS handshake to site.com failed. System.IO.IOException Authentication failed because the remote party has closed the transport stream.
11:23:05:6466 fiddler.network.https> HTTPS handshake to site.com failed. System.IO.IOException Authentication failed because the remote party has closed the transport stream.
11:23:07:4432 [Fiddler] No HTTP request was received from () new client socket, port 52325.
11:23:25:3327 fiddler.network.readresponse.failure> Session #15817 raised exception System.IO.IOException Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. < A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
11:23:52:6380 [Fiddler] No HTTP request was received from () new client socket, port 61327.
I read a lot about this kind of errors and tried all given solutions (even if just similarly with mines) without luck.
If anybody can shade some light on what's going one here, that will be great.
Thanks.
EricLaw
Dec 24, 2014, 12:54:40 PM12/24/14
to httpf...@googlegroups.com
It's not clear what problem you're having, specifically? What do you see in your browser? What errors occur in the browser?
The error messages you've shown above could all be explained by routine operation of a browser, where it speculatively opens a connection, decides it isn't needed, and closes the connection.
Raduc
Dec 24, 2014, 1:14:00 PM12/24/14
to httpf...@googlegroups.com
Hi Eric,
The sites just keep loading and then I see the following message:
Server not found
Firefox can't find the server at www.etc.com
Check the address for typing errors such as ww.example.com instead of www.example.com
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
However, if I try loading the sites without using Fiddler all works just fine.
I used Fiddler for a long time but never seen those errors in my logs nor had issues with any sites at all. All of the sudden, I start getting those errors and some sites are having issues loading. Sometimes they load and sometimes not - all happens randomly.
Thanks very much.
(By the way, I found your book very helpful)
The sites just keep loading and then I see the following message:
Server not found
Firefox can't find the server at www.etc.com
Check the address for typing errors such as ww.example.com instead of www.example.com
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
However, if I try loading the sites without using Fiddler all works just fine.
I used Fiddler for a long time but never seen those errors in my logs nor had issues with any sites at all. All of the sudden, I start getting those errors and some sites are having issues loading. Sometimes they load and sometimes not - all happens randomly.
Thanks very much.
(By the way, I found your book very helpful)
Raduc
Dec 24, 2014, 1:32:21 PM12/24/14
to httpf...@googlegroups.com
I first thought I have a wrong Firewall rule for Fiddler on the server but I don't think this is the issue - if you could have a look at this screen-cast that will be great: http://www.screencast.com/t/fMcqdfTo16
Thanks.
Raduc
Dec 24, 2014, 3:46:28 PM12/24/14
to httpf...@googlegroups.com
I also read about this - http://www.hyper-v.nu/archives/mvaneijk/2013/11/vnics-and-vms-loose-connectivity-at-random-on-windows-server-2012-r2/ And I read something similar on this group but not how the user solved his problem but only that this was the problem.
Shortly, the network interface controller can in some scenarios lose connectivity at random. But I still can't understand how this happened on three different (hardware) servers simultaneously. I tried using the first solution a user found (is the first comment on that page) but to no avail whatsoever.
Raduc
Dec 26, 2014, 7:27:52 PM12/26/14
to httpf...@googlegroups.com
I changed the OS to windows server 2008 R2 standard edition and reinstalled Fiddler4 but the errors are still the same.
Is there anybody that had these issue and can provide a fix?
Thanks,
Raduc
Dec 27, 2014, 1:43:42 PM12/27/14
to httpf...@googlegroups.com
After some more reading I thought I should start using the certificate maker plugin for debugging and got this log:
20:08:37:5096 Fiddler Running...
20:08:37:5096 Setting upstream gateway to none
20:08:40:8792 Fiddler ICertificateProvider v1.4.9.4 loaded.
fiddler.certmaker.bc.Debug: True
ObjectID: 0x232854a
20:08:40:8792 Using BCMakeCert.dll v2.0.7.0
20:08:40:8792 Fiddler.BCCertMaker> Asked to MakeNewCert(SITE.COM) from thread 20...
20:08:40:8792 Proceeding to generate (SITE.COM) on thread 20.
20:08:40:8792 Fiddler.BCCertMaker> Asked to MakeNewCert(SITE.COM) from thread 21...
20:08:40:8948 Fiddler.BCCertMaker> Asked to MakeNewCert(SITE.COM) from thread 22...
20:08:40:8948 /Queue indicated that creation of certificate [SITE.COM] was in-progress. Waiting up to 25000ms on thread: #21
20:08:40:8948 /Queue indicated that creation of certificate [SITE.COM] was in-progress. Waiting up to 25000ms on thread: #22
20:08:40:8948 Fiddler.BCCertMaker> Asked to MakeNewCert(SITE.COM) from thread 23...
20:08:40:8948 /Queue indicated that creation of certificate [SITE.COM] was in-progress. Waiting up to 25000ms on thread: #23
20:08:41:0040 Fiddler.BCCertMaker> Loaded root certificate and key from Preference. SubjectDN:OU=Created by http://www.fiddler2.com,O=DO_NOT_TRUST_BC,CN=DO_NOT_TRUST_FiddlerRoot
20:08:41:0040 Fiddler.BCCertMaker> CreatingCert for: SITE.COM
20:08:41:0040 Reusing the RootKey as the EEKey.
20:08:41:0196 Fiddler.BCCertMaker> PrivateKey Generation took: 8ms; 2048-bit key.
20:08:41:1288 Fiddler.BCCertMaker> Asked to MakeNewCert(SITE.COM) from thread 29...
20:08:41:1288 /Queue indicated that creation of certificate [SITE.COM] was in-progress. Waiting up to 25000ms on thread: #29
20:08:41:1444 Fiddler.BCCertMaker> Asked to MakeNewCert(SITE.COM) from thread 30...
20:08:41:1444 /Queue indicated that creation of certificate [SITE.COM] was in-progress. Waiting up to 25000ms on thread: #30
20:08:41:1444 Fiddler.BCCertMaker> Asked to MakeNewCert(SITE.COM) from thread 31...
20:08:41:1444 /Queue indicated that creation of certificate [SITE.COM] was in-progress. Waiting up to 25000ms on thread: #31
20:08:41:1600 Fiddler.BCCertMaker> Asked to MakeNewCert(SITE.COM) from thread 32...
20:08:41:1600 /Queue indicated that creation of certificate [SITE.COM] was in-progress. Waiting up to 25000ms on thread: #32
20:08:41:5344 Fiddler.BCCertMaker> EECert Generation took: 519ms in total.
20:08:41:5344 Fiddler.BCCertMaker> Converting BCKey to DotNetKey using CSP Provider type: 24
20:08:37:5096 Setting upstream gateway to none
20:08:40:8792 Fiddler ICertificateProvider v1.4.9.4 loaded.
fiddler.certmaker.bc.Debug: True
ObjectID: 0x232854a
20:08:40:8792 Using BCMakeCert.dll v2.0.7.0
20:08:40:8792 Fiddler.BCCertMaker> Asked to MakeNewCert(SITE.COM) from thread 20...
20:08:40:8792 Proceeding to generate (SITE.COM) on thread 20.
20:08:40:8792 Fiddler.BCCertMaker> Asked to MakeNewCert(SITE.COM) from thread 21...
20:08:40:8948 Fiddler.BCCertMaker> Asked to MakeNewCert(SITE.COM) from thread 22...
20:08:40:8948 /Queue indicated that creation of certificate [SITE.COM] was in-progress. Waiting up to 25000ms on thread: #21
20:08:40:8948 /Queue indicated that creation of certificate [SITE.COM] was in-progress. Waiting up to 25000ms on thread: #22
20:08:40:8948 Fiddler.BCCertMaker> Asked to MakeNewCert(SITE.COM) from thread 23...
20:08:40:8948 /Queue indicated that creation of certificate [SITE.COM] was in-progress. Waiting up to 25000ms on thread: #23
20:08:41:0040 Fiddler.BCCertMaker> Loaded root certificate and key from Preference. SubjectDN:OU=Created by http://www.fiddler2.com,O=DO_NOT_TRUST_BC,CN=DO_NOT_TRUST_FiddlerRoot
20:08:41:0040 Fiddler.BCCertMaker> CreatingCert for: SITE.COM
20:08:41:0040 Reusing the RootKey as the EEKey.
20:08:41:0196 Fiddler.BCCertMaker> PrivateKey Generation took: 8ms; 2048-bit key.
20:08:41:1288 Fiddler.BCCertMaker> Asked to MakeNewCert(SITE.COM) from thread 29...
20:08:41:1288 /Queue indicated that creation of certificate [SITE.COM] was in-progress. Waiting up to 25000ms on thread: #29
20:08:41:1444 Fiddler.BCCertMaker> Asked to MakeNewCert(SITE.COM) from thread 30...
20:08:41:1444 /Queue indicated that creation of certificate [SITE.COM] was in-progress. Waiting up to 25000ms on thread: #30
20:08:41:1444 Fiddler.BCCertMaker> Asked to MakeNewCert(SITE.COM) from thread 31...
20:08:41:1444 /Queue indicated that creation of certificate [SITE.COM] was in-progress. Waiting up to 25000ms on thread: #31
20:08:41:1600 Fiddler.BCCertMaker> Asked to MakeNewCert(SITE.COM) from thread 32...
20:08:41:1600 /Queue indicated that creation of certificate [SITE.COM] was in-progress. Waiting up to 25000ms on thread: #32
20:08:41:5344 Fiddler.BCCertMaker> EECert Generation took: 519ms in total.
20:08:41:5344 Fiddler.BCCertMaker> Converting BCKey to DotNetKey using CSP Provider type: 24
The SITE.COM can be any URL on gstatic.com or other content hosted on CDNs such as akamaiedge.net ...
I also see this log:
20:26:45:5491 Fiddler.BCCertMaker> Asked to MakeNewCert(ajax.googleapis.com) from thread 7...
20:26:45:5491 Proceeding to generate (ajax.googleapis.com) on thread 7.
20:26:45:5491 Fiddler.BCCertMaker> CreatingCert for: ajax.googleapis.com
20:26:45:5491 Fiddler.BCCertMaker> PrivateKey Generation took: 0ms; 2048-bit key.
20:26:45:5491 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
20:26:45:5491 Fiddler.BCCertMaker> Asked to MakeNewCert(ajax.googleapis.com) from thread 61...
20:26:45:5491 /Queue indicated that creation of certificate [ajax.googleapis.com] was in-progress. Waiting up to 25000ms on thread: #61
20:26:45:5647 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
20:26:45:5647 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
20:26:45:5647 Fiddler.BCCertMaker> EECert Generation took: 26ms in total.
20:26:45:5647 Fiddler.BCCertMaker> Converting BCKey to DotNetKey using CSP Provider type: 24
20:26:45:5803 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
20:26:45:5803 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
20:26:45:5803 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
20:26:45:5959 ContainerInfo for ajax.googleapis.com's Certificate's PrivateKey
KCName:FiddlerBCKey
Exportable:True
IsMachine:False
Protected:False
Removable:False
Provider:Microsoft Enhanced RSA and AES Cryptographic Provider (24)
UniqueName:6126ce6d65fe3c035ce2d7d51f5a45f2_d377b244-40a6-40a2-a415-dafa0db47865
RandomlyGenerated:False
20:26:45:5491 Proceeding to generate (ajax.googleapis.com) on thread 7.
20:26:45:5491 Fiddler.BCCertMaker> CreatingCert for: ajax.googleapis.com
20:26:45:5491 Fiddler.BCCertMaker> PrivateKey Generation took: 0ms; 2048-bit key.
20:26:45:5491 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
20:26:45:5491 Fiddler.BCCertMaker> Asked to MakeNewCert(ajax.googleapis.com) from thread 61...
20:26:45:5491 /Queue indicated that creation of certificate [ajax.googleapis.com] was in-progress. Waiting up to 25000ms on thread: #61
20:26:45:5647 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
20:26:45:5647 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
20:26:45:5647 Fiddler.BCCertMaker> EECert Generation took: 26ms in total.
20:26:45:5647 Fiddler.BCCertMaker> Converting BCKey to DotNetKey using CSP Provider type: 24
20:26:45:5803 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
20:26:45:5803 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
20:26:45:5803 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
20:26:45:5959 ContainerInfo for ajax.googleapis.com's Certificate's PrivateKey
KCName:FiddlerBCKey
Exportable:True
IsMachine:False
Protected:False
Removable:False
Provider:Microsoft Enhanced RSA and AES Cryptographic Provider (24)
UniqueName:6126ce6d65fe3c035ce2d7d51f5a45f2_d377b244-40a6-40a2-a415-dafa0db47865
RandomlyGenerated:False
20:26:45:5959 Fiddler.BCCertMaker> BC-to-.NET Conversion took: 20ms.
20:26:45:5959 Fiddler.BCCertMaker> Caching EECert for ajax.googleapis.com
20:26:45:5959 /Signaling [ajax.googleapis.com] is ready, created by thread 7.
20:26:45:5959 /Got Signal that certificate [ajax.googleapis.com] was ready. Returning to thread #61.
20:26:45:5959 Fiddler.BCCertMaker> Caching EECert for ajax.googleapis.com
20:26:45:5959 /Signaling [ajax.googleapis.com] is ready, created by thread 7.
20:26:45:5959 /Got Signal that certificate [ajax.googleapis.com] was ready. Returning to thread #61.
The creation of the certificates pretty much looks as the one from above but it happens randomly to see the log from above as is. To me it looks like something is not right but I don't know what.
Sometimes I don't see this part in the creation certificate log for the same site where I've seen it before : /Queue indicated that creation of certificate [SITE.COM] was in-progress. Waiting up to 25000ms on thread: #Number
Also, sometimes I don't see this part in the creation certification log for the same site where I've seen it before: HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
What it bothers me is that I think the logs from above have something to do with the slower Internet speed that I get in the browser.
Any help or pointers to where to dig for more info is much appreciated. Fiddler was working just fine until 1-2 weeks ago.
Reply all
Reply to author
Forward
0 new messages