Don't know if it's related or if it's enough to cause what I'm seeing, but if I open up Chrome's Developer Tools once I'm signed into cox and trying to access my Profile, I see the following three errors for that page:

- Refused to execute script from 'https://s-vop.sundaysky.com/t/v1/j?a=cox&ap=1&m=uui&pb=f&sp=https%3A%2F%2Fw…yaccount:my-profile:home;~z/89149;~bu/res;~sid/476;~ct/existing%20customer' because its MIME type ('image/gif') is not executable.

- XMLHttpRequest cannot load https://idm.cox.com/SmMakeCookie.ccc?SMSESSION=QUERY&PERSIST=0&TARGET=-SM-H…t%2fselfservice2%2fsecure%2fajax--api%2fuser%2fprofile%3f_%3d1492197838219. Redirect from 'https://idm.cox.com/SmMakeCookie.ccc?SMSESSION=QUERY&PERSIST=0&TARGET=-SM-H…t%2fselfservice2%2fsecure%2fajax--api%2fuser%2fprofile%3f_%3d1492197838219' to 'https://idm.east.cox.net/selfservice2/secure/ajax-api/user/profile?_=149219…FaPxmze5dQQwgYiG2MWpZU0yVibZ67%2fowmHd3QR836AjfnjRSDkgyDKZfjJFLQ0NTHtHuvgj' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access.

- XMLHttpRequest cannot load https://idm.cox.com/SmMakeCookie.ccc?SMSESSION=QUERY&PERSIST=0&TARGET=-SM-H…t%2fselfservice2%2fsecure%2fajax--api%2fuser%2fprofile%3f_%3d1492197838221. Redirect from 'https://idm.cox.com/SmMakeCookie.ccc?SMSESSION=QUERY&PERSIST=0&TARGET=-SM-H…t%2fselfservice2%2fsecure%2fajax--api%2fuser%2fprofile%3f_%3d1492197838221' to 'https://idm.east.cox.net/selfservice2/secure/ajax-api/user/profile?_=149219…0y3PYO%2fJTExeauZI15GIxKkAgjJDEDMLvLbZaUYYAcxFmO3PS9pKYodZzTw7dOaU5HEtb4RK' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access.

Could you please provide us any sample login details to triage the issue from our end.
As the registration of the site asking account number and PIN.

Thanks,

Unfortunately, I can't do that.  That's my actual account with my ISP (i.e., address and billing information plus ability to order things).  I guess the only way for anyone to reproduce this is if they have their own Cox Communications account.  Sorry.

Thank you for providing more feedback. Adding requester "kavvaru@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Adding TE-NeedsTriageFromMTV, as the site requires SSN to sign up.

MTV@ Could any one from MTV please check this issue if any one have cox account.

Thanks,

Tentatively labeling this a network issue (Not necessarily the case, but may be a cookie issue).  If you clear all cookies, does this work?

Could you provide us with an about:net-internals log?  https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details (It will contain visited URLs, but won't contain cookies, passwords, or form data)

I'm almost positive this isn't a Chrome problem and is something (either my account or the server I sign into in Las Vegas) on Cox's end.  See:

https://www.dslreports.com/forum/r31365803-NV-Can-t-Do-Account-Activities-on-Cox-Site?group=NV

The end result of that thread is I now have problems in my Cox profile page with Chrome, Edge, and Firefox.  I haven't tried Edge and Firefox on my phone, but with the Chrome browser there, I get the same issue.  Still, it seems like a cox issue.

But, to answer your question, I've cleared everything repeatedly.  About net-internals, that page says it's being deprecated. Do you want the net-export one, instead?

I can't even log onto my Cox account at this time.  I'll try again later and get that report to you.

Thank you for providing more feedback. Adding requester "mmenke@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Thanks for the followup!  If you're seeing it with multiple browsers, then it's not a Chrome issue.  net-export would have been fine, but I'm going to go ahead and close this bug for now.  If you have reason to think there's a Chrome-specific issue, please comment on this bug (And attach a log!) and I'll reopen.  If you decide there's probably a Chrome issue more than a week or two from now, it's better just to file a new bug.