ContributionsMost RecentMost LikesSolutionsRe: CANCELLATON You can just log into your account online and schedule a cancellation date there. Re: Email Yeah, definitely not the best experience using Cox email. Clunky and slow, with pages often needing to be refreshed to load properly. Now I'm finding all the spam emails - hundreds of them - in my inbox. They've all clearly been marked as SPAM, but instead of going to the spam folder they're all ending up in my inbox. Re: Contour Error code ftde.0001 Yep, there you go. I sure hope they aren't blocking it. I tried Google's dns and had no problems, it's apparently just Cloudflare's - and only when trying to use it with Contour. Re: Contour Error code ftde.0001 Well, needless to say, if you're using Cloudflare, or even another dns, try setting your dns to default to see if that fixes it. I'm convinced they've been messing around with something. Even though I'm having no trouble now accessing Contour and watching content, there have been several brief intermittent service interruptions in the last couple hours. Re: Contour Error code ftde.0001 Think you missed my last post. It's a problem with Cloudflare dns, or maybe specifically a problem with Cox Contour and Cloudflare. I thought things were still working after changing my dns back to 1.1.1.1, but when I finally got around to actually trying to watch something I found that nothing was happening when I clicked the Watch button, and when I tried refreshing the page it was actually disconnecting my internet - kept connecting and disconnecting. Since I'm not noticing any problems with using Cloudflare dns when doing anything else EXCEPT trying to use Contour, it's looking like some kind of recent change with Contour is causing the issue when using Cloudflare. Might want to pass it on to whoever. Thanks Re: Contour Error code ftde.0001 Okay, finally figured it out: it was my DNS. Should have checked that first, I guess, but I had completely forgotten that I'd changed it - months ago. I was using Cloudflare: 1.1.1.1. If Cox isn't now blocking it for some reason, I can only assume it's due to a temporary outage. (Although I would think that would affect my internet in general, so maybe Cox Contour IS blocking it...?) EDIT: No, just put the Cloudflare dns back and Contour is still working now, so apparently NOT being blocked - didn't really think it likely, but good to know. Anyway, I guess I know what to try first if it happens again.... Re: Contour Error code ftde.0001 Okay, it seems to have something to do with my IP address. I had previously run ipconfig /release /flushdns /renew without it making any difference, but I've found that after actually changing my IP address I can sign in to Contour. The only problem now, though, of course, is that I can't access most of the channels because I'm using a different IP address. But some are better than none, I guess. Re: Contour Error code ftde.0001 Done all those things, nothing has changed. I've even added the address and set to allow under the Flash settings in Chrome. In Edge I don't have any addon's at all because I rarely use it, still doesn't work. I'll just wait it out, I guess. This happened one day last week and resolved after a while. Thanks Re: Contour Error code ftde.0001 I've been getting this too, since last night, trying to watch Contour via browser. The full message is: "Please clear your browser's cache Sorry, we're having some trouble. Please clear your browser's cache and then refresh this page. Learn how to clear your cache by clicking here. (Error ftde.0001)" Except clearing my cache, including cookies and everything else, does no good: I keep getting that error. And I get it with three different browsers: FF, ME, and Chrome. So I'm pretty sure if doesn't actually have anything to do with my cache. I've also tried rebooting my computer and modem, just in case, and that also made no difference. Right now in Chrome, though, I can see the login box on watchtv.cox.com, but when I enter my credentials and click the sign in button I get this: Whitelabel Error Page This application has no explicit mapping for /error, so you are seeing this as a fallback. Sat Aug 25 14:49:11 UTC 2018 There was an unexpected error (type=Unauthorized, status=401). Authentication Failed: Error validating SAML message Re: Not so Gigablast - Wichita, KS Might be better to post this over on dslreports.