Community Forum

Can only browse HTTPS SSL sites (Google Facebook) not unencrypted ones - modem SB6121

Frequent Visitor

Can only browse HTTPS SSL sites (Google Facebook) not unencrypted ones - modem SB6121

Does anyone have this problem at the moment? I have a Comcast/Xinfinity cable connection with a Motorola/Arris modem SURFBoard SB6121. Two days ago I lost connectivity to IPv4  non-encrypted (HTTP) websites. I can access normally Google, Facebook, Youtube, Netflix - websites with a IPv6 encrypted address (SSL, HTTPS). But I can't access Apple, Amazon and other IPv4 websites with unencrypted addresses.

 

Update. I initially thought this was a IPv6 / IPv4 issue (an IPv6 website reported that my IPv4 connection was wrong). But in fact it's a SSL / HTTPS vs HTTP issue. I can connect to *encrypted* adresses, but not unencrypted ones. For instance, I cannot access the Amazon webpage (below), but if I start from the https sign-in page, it works.

 

I'm able to connect to a VPN. From there I can access any website, including unencrypted ones.

The problem doesn't depend on device or router. I get it if I connect to the modem through WiFi router or directly by cable, without router.

The problem doesn't depend on system or browser. I get it with Linux, Windows 7 and 8, Android, iOS. I can browse unencrypted websites through VPN.

I've tried restarting the router, doing a "power cycle", resetting it to defaults. I called Comcast support who restarted the router and said they would call us back. All failed.

One thing that puzzles me is that I can ping some, but not all, of the websites I cannot see. For instance, I can ping www.apple.com or www.hulu.com or my employer's websites but I can't browse them. Most often I can't ping IPv4 websites at all, e.g. www.amazon.com.  (Update: I can ping their encrypted version.) For some websites, e.g. Google, I can get the encrypted version (https://), but not the unencrypted one.

 

Another weird thing is that if I restart the modem, everything works normally for 1-2 mins and then unencrypted websites go down.


Another user with the same modem had a similar problem one and half year ago:, except that that (if I understand correctly) they were able to get IPv4 connectivity when they connected to the modem through the cable. They don't say how they solved it (or I don't get it). UPDATE: not sure this is relevant, since my issue is with SSL/HTTPS rather than IPv4.

That user suspected that their problem was due to a firmware update to the modem pushed by Comcast as they switched to IPv6 in their area. My modem info suggests that the firmware hasn't recently changed (see below).

Does anybody get the same problem? What can I do?

Here's the modem info:

 

Model Name: SB6121
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.14-SCM01-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3
Hardware Version: 5.0
Serial Number: 3590...EDITED
Firmware Build Time: Mar 6 2014 15:23:55

Configuration
Frequency Plan:     North American Standard/HRC/IRC
Custom Frequency Ordering:     Default
Upstream Channel ID:     66
Favorite Frequency (Hz)     717000000
DOCSIS MIMO     Honor MDD IP Mode
Modem's IP Mode     IPv6 Only
DHCP Server Enabled

Status
DOCSIS Downstream Channel Acquisition     Done
DOCSIS Ranging     Done
Establish IP Connectivity using DHCP     Done
Establish Time Of Day     Done
Transfer Operational Parameters through TFTP     Done
Register Connection     Done
Cable Modem Status     Operational
Initialize Baseline Privacy     Done

Adresses
Serial Number     359079329...EDITED
HFC MAC Address     30-...EDITED
Ethernet IP Address     192.168.100.1
Ethernet MAC Address     30-60-23-DB-89-8F

#    Known CPE MAC Address (Max 1)     Status
1    E8:DE:27:BB:E7:57    Dynamic

 

 

Here are the parameters the Wifi router gets. I redacted my public IP address, it's in the 98.224.224.XXX range, which are comcast IPs.

 

WAN
MAC Address:    E8-...EDITED
IP Address:    98.224.224...EDITED
Subnet Mask:    255.255.248.0    
Default Gateway:    98.224.224.1    
 
DNS Server:    75.75.76.76 , 75.75.75.75

System routing table:
ID    Destination Network    Subnet Mask    Gateway    Interface
1    192.168.0.0    255.255.255.0    0.0.0.0    LAN & WLAN
2    98.224.224.0    255.255.248.0    0.0.0.0    WAN
3    239.0.0.0    255.0.0.0    0.0.0.0    LAN & WLAN
4    0.0.0.0    0.0.0.0    98.224.224.1    WAN

 

I don't know much about networking but these look normal to me.


Now here's a dns lookup for www.apple.com

:~$ host www.apple.com
www.apple.com is an alias for www.isg-apple.com.akadns.net.
www.isg-apple.com.akadns.net is an alias for www.apple.com.edgekey.net.
www.apple.com.edgekey.net is an alias for e3191.dscc.akamaiedge.net.
e3191.dscc.akamaiedge.net has address 23.196.238.174
e3191.dscc.akamaiedge.net has IPv6 address 2600:141b:5:286::c77
e3191.dscc.akamaiedge.net has IPv6 address 2600:141b:5:289::c77

 
Here's a traceroute to www.apple.com (192.168.0.1 is the Wifi router, 98.224.224.1 is a comcast gateway). I can reach/ping it, but I can't browse it:

t

traceroute to www.apple.com (23.196.238.174), 30 hops max, 60 byte packets
 1  192.168.0.1 (192.168.0.1)  0.896 ms  1.752 ms  1.722 ms
 2  98.224.224.1 (98.224.224.1)  12.403 ms  17.049 ms  17.025 ms
 3  xe-11-1-1-0-sur02.sannarbor.mi.michigan.comcast.net (68.87.184.93)  16.990 ms  16.963 ms  16.934 ms
 4  te-0-4-0-12-ar02.pontiac.mi.michigan.comcast.net (68.87.190.45)  19.320 ms  19.546 ms te-0-4-0-14-ar02.pontiac.mi.michigan.comcast.net (69.139.254.89)  18.179 ms
 5  he-4-3-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.90.109)  26.476 ms * he-4-6-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.94.241)  25.361 ms
 6  hu-0-16-0-1-pe03.350ecermak.il.ibone.comcast.net (68.86.88.2)  24.612 ms  18.179 ms  19.440 ms
 7  66.208.216.62 (66.208.216.62)  28.411 ms  30.305 ms  29.315 ms
 8  * a23-196-238-174.deploy.static.akamaitechnologies.com (23.196.238.174)  27.271 ms  26.940 ms

 


You'd think that I can ping apple.com because it has an Ipv6 address. But there are also IPv4 only websites that I can ping - even though I can't browse them. Here's hulu:

 

host www.hulu.com
www.hulu.com is an alias for www.hulu.com.edgesuite.net.
www.hulu.com.edgesuite.net is an alias for a1700.r.akamai.net.
a1700.r.akamai.net has address 23.67.60.123
a1700.r.akamai.net has address 23.67.60.154

traceroute 23.67.60.123
traceroute to 23.67.60.123 (23.67.60.123), 30 hops max, 60 byte packets
 1  192.168.0.1 (192.168.0.1)  2.165 ms  2.902 ms  3.046 ms
 2  98.224.224.1 (98.224.224.1)  14.235 ms  16.287 ms  17.212 ms
 3  xe-11-1-1-0-sur02.sannarbor.mi.michigan.comcast.net (68.87.184.93)  23.210 ms  26.145 ms  24.166 ms
 4  te-0-4-0-12-ar02.pontiac.mi.michigan.comcast.net (68.87.190.45)  21.068 ms te-0-4-0-13-ar02.pontiac.mi.michigan.comcast.net (68.85.222.166)  19.844 ms  20.820 ms
 5  he-4-6-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.94.241)  28.121 ms * be-33668-cr01.350ecermak.il.ibone.comcast.net (68.86.90.45)  27.033 ms
 6  pos-1-8-0-0-pe01.350ecermak.il.ibone.comcast.net (68.86.87.166)  26.017 ms  18.848 ms  19.311 ms
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * a23-67-60-123.deploy.static.akamaitechnologies.com (23.67.60.123)  18.618 ms  19.853 ms

 


Finally there are IPv4 websites that I can't even ping. Here's a dns lookup and traceroute for www.amazon.com. The last servers on the route are Amazon's (50.240.XXX.XXX, 72.21.220.XXX, 205.251.245.XXX). But I can't ping or browse www.amazon.com:

:~$ host www.amazon.com
www.amazon.com has address 176.32.98.166

traceroute to www.amazon.com (176.32.98.166), 30 hops max, 60 byte packets
 1  192.168.0.1 (192.168.0.1)  0.794 ms  1.663 ms  1.645 ms
 2  98.224.224.1 (98.224.224.1)  9.833 ms  16.306 ms  16.298 ms
 3  xe-11-1-1-0-sur02.sannarbor.mi.michigan.comcast.net (68.87.184.93)  16.278 ms  16.264 ms  16.562 ms
 4  te-0-4-0-14-ar02.pontiac.mi.michigan.comcast.net (69.139.254.89)  18.420 ms  19.400 ms  19.675 ms
 5  he-6-14-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.166.93)  25.636 ms * he-4-6-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.94.241)  27.953 ms
 6  be-10206-cr01.newyork.ny.ibone.comcast.net (68.86.86.225)  41.676 ms  39.891 ms  33.780 ms
 7  he-0-13-0-0-pe03.111eighthave.ny.ibone.comcast.net (68.86.85.182)  39.492 ms  39.606 ms  40.518 ms
 8  as16509-3-c.111eighthave.ny.ibone.comcast.net (50.242.148.118)  39.948 ms  39.963 ms  39.728 ms
 9  54.240.229.76 (54.240.229.76)  39.924 ms  38.195 ms 54.240.229.88 (54.240.229.88)  40.583 ms
10  54.240.228.202 (54.240.228.202)  48.404 ms 54.240.228.192 (54.240.228.192)  48.391 ms 54.240.228.202 (54.240.228.202)  47.221 ms
11  54.240.229.219 (54.240.229.219)  48.133 ms 54.240.229.221 (54.240.229.221)  49.214 ms  50.163 ms
12  54.240.228.181 (54.240.228.181)  41.490 ms 54.240.228.171 (54.240.228.171)  41.452 ms 54.240.228.167 (54.240.228.167)  41.212 ms
13  72.21.220.181 (72.21.220.181)  46.876 ms  44.771 ms 72.21.220.173 (72.21.220.173)  44.652 ms
14  205.251.245.232 (205.251.245.232)  44.621 ms 205.251.245.226 (205.251.245.226)  43.687 ms  44.551 ms
15  * * *
16  * * *
17  * * *

 


Anybody has a suggestion? Why can't I browse websites that I can ping? Why can't I ping or browse www.amazon.com even though I browse their servers? Is it possible that the problem comes from the modem?

Frequent Visitor

Re: Can only browse IPv6 sites (Google Facebook) not IPv4 (Amazon) - modem SB6121

I guess signal strength is irrelevant but just in case here you go:

 

Downstream   Bounding Channel Value

Channel ID 11  12  13  14 

Frequency 717000000 Hz  723000000 Hz  729000000 Hz  735000000 Hz 

Signal to Noise Ratio 36 dB  35 dB  36 dB  32 dB 

Downstream Modulation QAM256  QAM256  QAM256  QAM256 

Power Level  -7 dBmV   -8 dBmV   -7 dBmV   -8 dBmV 

 

Upstream     Bonding Channel Value
Channel ID     66      65      67
Frequency     27900000 Hz     34800000 Hz     22600000 Hz
Ranging Service ID     15179     15179     15179
Symbol Rate     5.120 Msym/sec     5.120 Msym/sec     2.560 Msym/sec
Power Level     54 dBmV     54 dBmV     54 dBmV
Upstream Modulation     [3] QPSK[3] 64QAM    [3] QPSK[3] 64QAM     [3] QPSK[3] 64QAM
Ranging Status     Success     Success     Success

Signal Stats (Codewords)     Bonding Channel Value
Channel ID     11      12      13      14
Total Unerrored Codewords     548157876     548154254     548154685     247682741
Total Correctable Codewords     3446     3734     3575     346606
Total Uncorrectable Codewords     5773     9114     8851     603476

Diamond Problem Solver

Re: Can only browse IPv6 sites (Google Facebook) not IPv4 (Amazon) - modem SB6121

You should also edit out your modem's MAC address and serial number. The downstream power is marginal, the SNR is low, and the upstream power is out of spec. No further IPv6 troubleshooting should be done until the connection quality is fixed.

 

Things that you can try;

 

In an effort to try to obtain better connectivity, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1000 MHz, bi-directional, and no gold colored garbage from Radio Shack, Home Depot, Target, etc. Splitters shoud be swapped with known to be good / new ones to test.

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two way splitter connected directly off of the drop from the street/pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.


Frequent Visitor

Re: Can only browse IPv6 sites (Google Facebook) not IPv4 (Amazon) - modem SB6121

HI EG, thanks a lot for the quick answer, I'll look into that. But can it really be that weak signal causes the following:

 

- no problem browsing everything through VPN

- no problem browsing selected IPv6 sites

- systematically impossible to browse IPv4 sites and some IPv6 sites?

 

I'm puzzled. Our cables are long, but they have been so for 6 months without noticeable issues.

Diamond Problem Solver

Re: Can only browse IPv6 sites (Google Facebook) not IPv4 (Amazon) - modem SB6121


landed wrote:

HI EG, thanks a lot for the quick answer, I'll look into that. But can it really be that weak signal causes the following:

 

- no problem browsing everything through VPN

- no problem browsing selected IPv6 sites

- systematically impossible to browse IPv4 sites and some IPv6 sites?

 


I can not say for certain, I can only say that that is what a CC employee here (if they see this thread) will tell you. It's only logical that this should be fixed first as it is a problem waiting to get worse.

Frequent Visitor

Re: Can only browse IPv6 sites (Google Facebook) not IPv4 (Amazon) - modem SB6121

Ok, useless splitter removed, signals levels are within specs now (I think, http://www.dslreports.com/faq/16085), but my problems persists!

 

Downstream     Bonding Channel Value
Channel ID     11      13      14      15
Frequency     717000000 Hz     729000000 Hz     735000000 Hz     741000000 Hz
Signal to Noise Ratio     38 dB     37 dB     38 dB     37 dB
Downstream Modulation     QAM256     QAM256     QAM256     QAM256
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
    -1 dBmV      -2 dBmV      -2 dBmV      -4 dBmV  

Upstream     Bonding Channel Value
Channel ID     66      65      67
Frequency     27900000 Hz     34800000 Hz     22600000 Hz
Ranging Service ID     15187     15187     15187
Symbol Rate     5.120 Msym/sec     5.120 Msym/sec     2.560 Msym/sec
Power Level     50 dBmV     50 dBmV     50 dBmV
Upstream Modulation     [3] QPSK
[3] 64QAM
     [3] QPSK
[3] 64QAM
     [3] QPSK
[3] 64QAM
 
Ranging Status     Success     Success     Success

Signal Stats (Codewords)     Bonding Channel Value
Channel ID     11      13      14      15
Total Unerrored Codewords     9867945     9089971     9090061     9090030
Total Correctable Codewords     12     0     0     16
Total Uncorrectable Codewords     649     505     563     735

 

 

Diamond Problem Solver

Re: Can only browse IPv6 sites (Google Facebook) not IPv4 (Amazon) - modem SB6121

FWIW, the 50dB is still marginal and doesn't allow much wiggle room for normal / seasonal / daily signal fluctuations.

 

Try  contacting Comcast John about the IPv6 problem via a private message here;

 

http://forums.comcast.com/t5/notes/privatenotespage/tab/compose/note-to-user-id/3115233

 

He may be able to help you with this.

Frequent Visitor

Re: Can only browse IPv6 sites (Google Facebook) not IPv4 (Amazon) - modem SB6121

Thanks, EG! Important updates:

 

My problem is with (the lack of) HTTPS / SSL, not IPv4. On a closer look what's going on is that I can't browse unencrypted (HTTP) websites.

 

However note that it doesn't come from browser or laptop blocking unencrypted trafic: the problem arises on various platforms, browsers, and doesn't arise when browsing unencrypted websites through VPN.

 

It looks like it could be a MTU issue. (The MTU setting is what fixes the maximum sizes of internet packets, I gather.) In various settings some people have a had the same behaviour due to a MTU setting higher than what their router/modem/ISP allows, so small packets go through (that's why you can ping) but big ones are lost. 

 

I've check my MTU settings (router and laptop): 1500, which is the default and is supposed to be good for Comcast. I set the MTU of the router and the laptop to 1400, no effect. (The modem doesn't have a MTU setting).

 

Waiting from Comcast's "higher fix team" to come back. Anybody with similar issues?

 

 

Diamond Problem Solver

Re: Can only browse IPv6 sites (Google Facebook) not IPv4 (Amazon) - modem SB6121

FWIW, changing the default ethernet MTU value of 1500 that the network uses is just covering up for a larger problem and should not need to be done. Good luck with this !

Frequent Visitor

Re: Can only browse IPv6 sites (Google Facebook) not IPv4 (Amazon) - modem SB6121

Ok! Anyway, I just did some tests: whether I ping with big packets or small ones make no difference. Some sites I can't ping at all, no matter what the packet size, and some times I can ping with big packets (1472, 1500) but cannot browse. So not sure the problem has anything to do with packet size / MTU.

 

Something somewhere between my modem and the outer world blocks unencrypted traffic.

Frequent Visitor

Re: Can only browse HTTPS websites - ports 80 filtered

Update: the issue is that the port 80 of any IP (beyond the local ones: modem, router, self) is "filtered". This shows up with nmap on Linux:

 

:~$ nmap -p 443 www.google.com

Starting Nmap 6.40 ( http://nmap.org ) at 2015-03-06 20:00 EST
Nmap scan report for www.google.com (216.58.216.68)
Host is up (0.024s latency).
rDNS record for 216.58.216.68: ord30s21-in-f4.1e100.net
PORT    STATE SERVICE
443/tcp open  https

 

:~$ nmap -p 80 www.google.com

Starting Nmap 6.40 ( http://nmap.org ) at 2015-03-06 20:00 EST
Nmap scan report for www.google.com (216.58.216.228)
Host is up (0.023s latency).
rDNS record for 216.58.216.228: ord31s22-in-f4.1e100.net
PORT   STATE    SERVICE
80/tcp filtered http

 

 

80 is the HTTP port, 443 is the HTTPS one. For any website I get the same thing: 443 open, 80 filtered. This works even with websites that I can't ping, like www.amazon.com.

 

"Filtered" means that my connections are dropped without reply. This is why my browsers hang when I try to connect. That's what you normally do to an attacker / spammer etc. But I've checked public blacklists and my IP is not listed.

 

I hope that I've narrowed the problem enough for Comcast to figure out where the black hole is.

Frequent Visitor

Re: Can only browse HTTPS websites - ports 80 filtered

Update: found this, which is exactly the same issue (espectially the 1min of normal functioning before port 80 breaks down): http://forums.comcast.com/t5/Basic-Internet-Connectivity-And/Upstream-port-80-Blocked-on-modem-or-ne...

 

Basically, something has triggered an automatic "in-browser notification" which was supposed to redirect me to a Comcast page where I'd have seen the notification and clicked "yes, thank you for the notification" and my traffic would have been restored to normal. But the redirect is dysfunctional, so I don't get the chance to clear that up. The only solution seems to be to send a PM to a Comcast team member that knows what the issue is. I'll post if that works.

Gold Problem Solver

Re: Can only browse HTTPS websites - ports 80 filtered

Comcast Security Assurance might be able to help you with this if you can get past the first-line reps. Call them at 1-888-565-4329 (from http://constantguard.comcast.net/dedicated-support/contacts#s5_nav).

Frequent Visitor

Re: Can only browse HTTPS websites - ports 80 filtered

Thanks BruceW!

 

Update: spent two hours with "higher fix" rep on the phone yesterday. They claimed the "in browser notification" thing should be cleared up when they reset the modem. So they did that and we tried everything and their best hypothesis was that somehow firewalls had appeared on our router and computers simultaneously two days ago or where "interefering" in various ways. (Not to mention the firewalls in question kicking in exactly 1min after modem reset, on port 80 only and e.g. not 8080.) And we tried everything related to that again and nothing worked.

 

Looking again at BillK303's post (http://forums.comcast.com/t5/Basic-Internet-Connectivity-And/Upstream-port-80-Blocked-on-modem-or-ne... it's clear that resetting the modem *didn't work* for his "in-browser notifcation" bug. So if you have that problem and reps tell you that they can clear the "in-browser notification" thing by resetting the modem, insist that they can't!

 

Luckily I've got a quick PM reply from ComcastJohnN who solved the issue for other people (cf post linked above). He forwarded my info the the networking team in charge of this. It isn't fixed yet but I'd rather wait more than go through lines of support again yet!

Gold Problem Solver

Re: Can only browse HTTPS websites - ports 80 filtered


landed wrote: ... spent two hours with "higher fix" rep on the phone yesterday. ...

Ugh. Unfortunately, finding a Comcast rep at the regular customer service numbers who has even heard of the notification system is, I would imagine, a very long shot. Finding one there who has even a feeble understanding of it would be like finding a unicorn. Even calling CSA, it isn't easy to get past the first-line folks, and they don't seem to know much either.

 

Let's hope that ComcastJohnN gets this fixed up for you. If not, let us know, and maybe one of the forum Experts can help you out.

Frequent Visitor

Re: Can only browse HTTPS websites - ports 80 filtered

Issue solved! ComcastJohnN send a second email to the relevant networking team, they finally called us back, removed the failed notification, and everything is back up to normal.

 

So if you get the same problem (standard HTTP browsing systematically times out, but HTTPS browsing, VPN, IMAP email and anything that doesn't use port 80 ok, and when you reset your modem you get full connectivity for 1 minute only), then you need to send the MAC address of your modem to ComcastJohnN  (http://forums.comcast.com/t5/user/viewprofilepage/user-id/1125291 ), as several people with the same issue did (see this other post: http://forums.comcast.com/t5/Basic-Internet-Connectivity-And/Upstream-port-80-Blocked-on-modem-or-ne... ).

Regular Visitor

Re: Can only browse HTTPS websites - ports 80 filtered

Thanks for this, issue started on the 10th for me, very annoying. Just messaged Comcast John

New Poster

Re: Can only browse HTTPS websites - ports 80 filtered

 Hi, just wondering is this issue being solved?

 

I just encountered same problem since yesterday.

New Poster

Re: Can only browse HTTPS websites - ports 80 filtered

We are having this issue as well for too too long. If this doesn't work, we will be switching to a new company.

 

***Just sent a msg to ComcastJohnN. Hope to hear something. I will update my results if I hear back or anything changes.

 

At the moment I have the same as everyone, all wireless clients can only acscess faceook, netflix hulu, google etc.

New Poster

Re: Can only browse HTTPS websites - ports 80 filtered

I have had this problem off and on for over a year now.  I am using multiple systmes in my home.  All are Windows systems.  Windows 8.1, Windows 7, and Windows Vista.  The systems that I seem to have this recurring problem on are the Windows Vista and Windows 7 systems.  The problem ALWAYS occurs for me right after an automated Windows update.  The first time it happened, it took me nearly a week to resolve.  I was only able to resolve it after restoring to an earlier restore point, prior to the Windows update.  But the next time the automated Windows update ran, the problem returned.  I did the restore point and it again fixed the problem, so I turned off the automated update in Windows and the problem didn't return.  This works, but it doesn't identify what the problem is!  And it creates another problem.  If I cannot do Windows updates, my system will be left open to security issues that are fixed in subsequent Windows updates.  I am hoping that, by posting this message, someone will be able to finally identify what this real problem is and how to fix it permanently.

New Poster

Re: Can only browse HTTPS websites - ports 80 filtered

I had this probem today and it took me four hours on the phone to get it fixed. I finally talked with a higher level tech who seemed to know something. I assumed she fixed this but I will never know for sure because I got cut off before she could come back to talk with me. I got cut off several times during this process. It eventually worked when I tried it a bit later in the afternoon. Customer service is a disaster. Essentially everyone except the last person knew nothing about how to fix this or even trouble shoot in a basic way. IT IS A ABSOLUTE DISGRACE. I can't believe a major company treated me this way. This is exactly what happens when you have a near monopoly on cable service in the community.   PS I did not go the this board first to look for hints. Obviously I should have. ComcastJohnN would have been a helped I'm sure but why him and not the general technical support staff?

Contributor

Can Only Browse Https:// Sites

I had a previous thread set up regarding my issues (https://forums.xfinity.com/t5/Your-Home-Network/Connectivity-issues/td-p/3106381) but I am starting this one since it appears I have narrowed down the problem.

I am only able to browse secure websites.  This is true across all of my devices.  If I attempt to go to a website which is http:// the connection times out.  I can browse https:// sites without issue.

I have seen a few other references to people with similar problems on Comcast.  Apparently something was triggered which causes non-secure traffic to be blocked.  Can anyone assist with a fix?  Thank you.

 

Please see https://forums.xfinity.com/t5/Your-Home-Network/Can-only-browse-HTTPS-SSL-sites-Google-Facebook-not/... for reference to a similar problem to what I am experiencing.

Official Employee

Re: Can Only Browse Https:// Sites

Hello evanstok. I have responded to your duplicate post located: http://forums.xfinity.com/t5/Your-Home-Network/Connectivity-issues/m-p/3107311#M283468

 

Please refrain from creating duplicate posts about the same topic, as doing so is a violation of Comcast Forum Guidelines.