Xfinity Forum Archive...
This is an archived section of the community.
Content in this area has been identified as outdated or irrelevant.
This change was done in an effort to make the forum easier to use and to keep only the most helpful and recent content active.
Post your questions in the Xfinity Community
im having the same problem its very frustrating.
Build number366OSWindows 10BrowserChrome 61.0.3163.79Flash version26.0.0Statusin homeEntitlementscvod, est, tve-vod, clinear, tve-linearLast fingerprintcloudtv_web_polymer_4.5.0_prod_1504811609215_18640Stream providerprimetimeVideo IDtvgrid/listing/2006004809071900109/detail/?channelId=8273577160132532104Stream IDtag:xfinitytv.comcast.net,2013:channel-station:6887098088320066117:chNum:1734:callSign:TOOND#stream:format:HLSError code3329.500Error descriptionError aux infohttp://ccr.linear-nat-pil-red.xcr.comcast.net/TOOND_HD_NAT_16548_0_5212050385360922163.m3u8?format=redirectVideo Provider1734 TOONDVideo SourceTVListingDetailVideo TitleBooty Scooty
This error just starting happening this afternoon. Appears chrome is blocking or not allowing the site to run scripts, and it is trying to run on http not https, but the mobile app is down as well.
same thing just started
Yup add me to the list of watching online and then cannot with the same error code given and no where to reference it either. Wish they would at least tell people what the issue is rather than having to wait for an eternity wondering what's going on.
We're experiencing an outage at the moment; teams are working to get everything back up asap. No need to report further—we're definitely on full alert already. Apologies for the interruption!
OK, everything should be back to normal now. Please let us know if you're still experiencing problems.
Thanks! I am back up. Ticket# CR......8147. Could you let us know what error 3329.500 mean? So we will know what to expect if this happens again. We love Comcast Streaming...
I was having the same problem earlier. I went on chat support, where they had me clear my cache, try another browser, and finally it just started working on its own. All the time you knew it was a problem on your end that would be fixed shortly. Why don't you pass that information on to the chat support people so I wouldn't waste about 45 minutes of my time?
The 500 part is a straight up server error (in this case, the license server was returning an error because it couldn't reach another server to check for playback entitlements). The 3329 part indicates that the 500 happened during a license request. On other platforms (iOS and Android, for example), we usually don't even show the 3329 part because it's not that useful for troubleshooting—it's a container error for many more-specific codes, and we care about the specific ones (in other words, we want to know why we weren't able to get a license :-). Among the 3329 errors you should never see but sometimes do because of an unexpected failure somewhere along the line: 3329.12007 (our content access system thinks you're out of home when trying to watch an in home-only stream), 3329.12015 (OnDemand asset not available), and 3329.12012 (not entitled to channel).
Hope that helps.
I work on the engineering team with the folks actually trying to fix the problem (which took less time than getting word out to the support folks). I'm one person, and I posted here as soon as I could.