We set up a new website for an organization I'm involved with and I'm unable to view the website on my PC (ERR_SSL_PROTOCOL_ERROR). Same behavior using multiple browsers, and others have experienced the same (no idea who their IPSs are). However, some people can see the site just fine and I can on my phone.
When I turn on VPN in my browser -- magic! -- the site appears just fine. Makes me think that Comcast is blocking the site somehow. Any idea why or how, or, more importantly, what we need to do on the site to prevent that from happening. The site is www.midwestaikidocenter.org.
Solved! Go to Solution.
I kind of doubt it's a Comcast issue. I just used your link and got right onto the site with no issues. I'm running Windows 10 and Vivaldi. I also tried with Edge------got right on with no problem. I don't use a VPN.
Are you using a rented Comcast gateway device ? If so, try disabling the Xfi Advanced Security feature as a work-around for now and see. It's buggy ! And there is currently no way for an end-user to be able to whitelist anything;
Hmmm, ok. So perhaps a router issue. I'm using UniFi from Ubiquiti. Will have a poke around there, but strange that I've never encountered this issue before on any other sites.
Your Comcast issued public / WAN IP address may be being blocked somewhere. The output of a traceroute to the domain may reveal where the blockage is.
The results of my tracert:
1 4 ms 1 ms 1 ms 192.168.1.1
2 30 ms 15 ms 12 ms 126.96.36.199
3 51 ms 13 ms 27 ms po152-rur02.nchicago.il.chicago.comcast.net [188.8.131.52]
4 69 ms 27 ms 40 ms be-162-ar01.area4.il.chicago.comcast.net [184.108.40.206]
5 * * * Request timed out.
6 24 ms 28 ms 22 ms ae-0-11.bar4.Minneapolis2.Level3.net [220.127.116.11]
7 49 ms 38 ms 38 ms SPIRE-CREDI.bar1.Minneapolis2.Level3.net [18.104.22.168]
8 41 ms 35 ms 42 ms port-channel-3.gw-distd-sh-1.slr.lxa.us.oneandone.net [22.214.171.124]
9 49 ms 49 ms 48 ms 74-208-236-162.elastic-ssl.ui-r.com [126.96.36.199]
Not sure if that middle 'request timed out' is the issue?
Are there anymore hops after hop 9 (trace complete) ? And can you please show the IP address of the domain that is being traced (tracing route to).
The timed out hop is simply a hop that does not respond to ping trace probes.
No, after hop 9, just the 'trace complete' message. The destination IP is 188.8.131.52 (www.midwestaikidocenter.org). Thanks much for your attention.
Ok, think I figured it out ... and had nothing to do with any router/firewall/domain issues. Sorry for the bother.
The guy who set up our site, let the default timezone of GMT, I changed to our local timezone and reissued the SSL certificate and seems to load ok for me, and hopefully others.
Apologies again for wasting your time, but greatly appreciate the attempted assitance!!
No prob ! Well you were far beyond Comcast webspace anyway, so they had nothing to do with it.
Glad you got it figured out ! Good luck ! Now closing this thread.