Thank you all for the help!
www.engadget.com is also doing this:
"Performing a TLS handshake to www.engadget.com" then get the error page
"
The connection has timed out
The server at www.engadget.com is taking too long to respond.
"
for https://www.engadget.com/rss.xml
I researched TLS handshaking issues for days (week?) tracking it down; played with FF/Chrome security settings for various TLS levels without success until finally turning off AIProtection (AIP)/Malicious Site Blocking (MSB) fixed it. I was suspecting this might relate to the recent standards change in TLS but that is way beyond my feeble skills.
gave a window with the hostname in the title bar and a blinking cursor.
Then "q" [Note: some whitespace removed to condense]:
again, from Win10Pro client
result [Note: some whitespace removed to condense]
yielded telnet window with cursor that was unresponsive to "q" and "?"
engadget.com ip, direct hostname was same without www
Likely today with cut over to the replacement RT-AC86u with 384.7 but doubt that will make different here. THANKS for all the help. cheers
ISP is Comcast so is that likely? These are news feeds from Protopage custom landing page that aggregaes news feeds, weather etc.Could be your ISP's WAN IP that's blacklisted by them
www.engadget.com is also doing this:
"Performing a TLS handshake to www.engadget.com" then get the error page
"
The connection has timed out
The server at www.engadget.com is taking too long to respond.
"
for https://www.engadget.com/rss.xml
I researched TLS handshaking issues for days (week?) tracking it down; played with FF/Chrome security settings for various TLS levels without success until finally turning off AIProtection (AIP)/Malicious Site Blocking (MSB) fixed it. I was suspecting this might relate to the recent standards change in TLS but that is way beyond my feeble skills.
Sorry for being unclear. I ONLY have the Malicious Site Blocking (MSB) part of AIP turned on to trouble shoot the problem. With MSB off, these sites load fine. This was first step. When turning AIP off fixed the problem, I turnedif you have aiprotection turned off and its still happening, why do you think its aiprotection?
- MSB ON with
- Two-Way IPS (IPS) OFF and
- Infected Device Prevention and Blocking (IDPB) OFF .
Now: Firefox 62.0.3 64b, and since you asked, just tested Chrome 70.0.3538.67 (Official Build) (64-bit), just updated as well as the previous version. I hit this a month ago and misconfigured my systems chasing this before realizing it was in the router, related to MSB. Tested xubuntu clients running Firefox and chrome then with same results also. Yesterday, found misconfiguration of Win10Pro client dns and fixed it. Had messed up dns which seems fixed except this problem makes me suspect something is off still. Did not help that the new RT-AC86u burned out its 2.4G radio over the weekend, new one is ready to be cut in with FW 384.7. As below, using RT-AC3100u with 384.6what browser are you using?
Current Win10pro Defender. Just tried turning it OFF and accessing the site with same result so turned back on<G>. I believe I did a few weeks ago too. Even was on with MS tech support a few hours.what av are you using?
uBlock Origin 1.17 tried turning off, no joy, many times. I think I uninstalled it too with no help, but can do that again, no problem<G>. Was using uMatrix, but was too cumbersome. All these issues popped up in last month when bringing up the Synology NAS and went down the rabbit hole chasing my tail. I think I had AIP completely off up until then but thought it a good idea since adding the NAS and planning to open some ports for offsite backups (likely with Backblaze B2)Do you have skynet or any ad blockers?
from Win10Pro clientIf you can ping it, what ip did it resolve to?
Code:
C:\Users\rg>ping engadget.com
Pinging engadget.com [124.108.115.87] with 32 bytes of data:
Reply from 124.108.115.87: bytes=32 time=141ms TTL=46
...
Ping statistics for 124.108.115.87:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 141ms, Maximum = 141ms, Average = 141ms
C:\Users\rg>ping huffingtonpost.com
Pinging huffingtonpost.com [98.136.103.26] with 32 bytes of data:
Reply from 98.136.103.26: bytes=32 time=30ms TTL=50
....
Ping statistics for 98.136.103.26:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 30ms, Average = 29ms
Haven't used telnet in over a decade, then not much<G> but looked it up and did so in Win10Pro client.Next step is to telnet to it over port 80
Code:
C:\Users\rg>telnet huffingtonpost.com 80
Then "q" [Note: some whitespace removed to condense]:
Code:
HTTP/1.0 400 Invalid HTTP Request
Date: Thu, 18 Oct 2018 18:00:12 GMT
Server: ATS
Cache-Control: no-store
Content-Type: text/html
Content-Language: en
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Referrer-Policy: strict-origin-when-cross-origin
Content-Length: 220
<HTML>
<HEAD>
<TITLE>Bad Request</TITLE>
</HEAD>
<BODY BGCOLOR="white" FGCOLOR="black">
<H1>Bad Request</H1>
<HR>
<FONT FACE="Helvetica,Arial"><B>
Description: Could not process this request.
</B></FONT>
<HR>
</BODY>
Connection to host lost.
Code:
C:\Users\rg>telnet www.huffingtonpost.com 80
Code:
HTTP/1.0 501 Not Implemented
Content-Type: text/html
Content-Length: 357
Connection: close
Date: Thu, 18 Oct 2018 18:03:42 GMT
Server: ECDF (sjc/16CB)
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>501 - Not Implemented</title>
</head>
<body>
<h1>501 - Not Implemented</h1>
</body>
</html>
Connection to host lost.
Code:
C:\Users\rg>telnet www.engadget.com 80
Code:
C:\Users\rg>telnet 124.108.115.87 80
Code:
HTTP/1.0 400 Invalid HTTP Request
Date: Thu, 18 Oct 2018 18:24:36 GMT
Server: ATS
Cache-Control: no-store
Content-Type: text/html
Content-Language: en
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Referrer-Policy: strict-origin-when-cross-origin
Content-Length: 220
<HTML>
<HEAD>
<TITLE>Bad Request</TITLE>
</HEAD>
<BODY BGCOLOR="white" FGCOLOR="black">
<H1>Bad Request</H1>
<HR>
<FONT FACE="Helvetica,Arial"><B>
Description: Could not process this request.
</B></FONT>
<HR>
</BODY>
Connection to host lost.
Likely today with cut over to the replacement RT-AC86u with 384.7 but doubt that will make different here. THANKS for all the help. cheers
Last edited: