Cox Webmail Issue

25 Dec 2022 | US Navy Vet

[US Navy Vet]

Has anyone else had issues with Cox Webmail? I get this Error Message, "There was an unexpected internal error. Please try again.".

[US Navy Vet]

Anyone else have this issue?

[US Navy Vet]

Any help will be GREATLY Appreciated!

[House Atreides]

https://www.isitdownrightnow.com/cox.net.html

[Repeal The 17th]

“Please try again”

[Bloody Sam Roberts]

A Momentary Lapse of Reason...er...I mean server access.

[Pollard]

Try a different, “approved” browser. A lot of sites have issues with anything but the latest Chrome/Firefox browsers. I run Waterfox and as of the last update, can’t log in to substack with it. Can log in just fine with Brave though. Brave seems to be the best alt browser.

[joebobsr]

I did a few days ago. Went on for a few hours before resolving itself. They are most likely doing maintenance or are in need of some hardware/capacity upgrade.

[linMcHlp]

Cox.com (Cox.net) webmail:

https://www.cox.com/content/dam/cox/okta/mail.html

Using Developer Tools of my Chromium -based Internet browser, one of the HTTPS connections made, is to:

https://global.oktacdn.com/okta-signin-widget/3.8.2/js/okta-sign-in.min.js

What is(?):

“global.oktacdn.com”

Some command line toolwork:

dig -t cname global.oktacdn.com
;; QUESTION SECTION:
;global.oktacdn.com. IN CNAME
;; ANSWER SECTION:
global.oktacdn.com. 300 IN CNAME d1ril57tlz9ev4.cloudfront.net.

I am not an expert, but “global.oktacdn.com” seems to be a fits-all name for “d-multi-character-string-part.cloudfront.net” that are sources at Cloudfront.net (part of Amazon).

Maybe there was some DNS problem, somewhere along the connection pathways, I wondered? But, no such problem.

Looking elsewhere for trouble . . .

In the browser Developer Tools window, reading some of the Console fine print, found:

DevTools failed to load source map:

Could not load content for

https://global.oktacdn.com/okta-signin-widget/3.8.2/css/okta-sign-in.css.map:

HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

Also found:

DevTools failed to load source map:

Could not parse content for:

https://webcdn.cox.com/content/dam/cox/common/externalcss/override/overrides.min.css.map:

Unexpected token in JSON at position 0

So, there are 2 instances of:

“failed to load source map”

In the first instance, “Could not load content”

In the second instance, “Could not parse content”

Probably, there is something about the Internet browser, that is blocking / interfering with loading one or more source maps.

The problem(s) might be AdBlock or some other add-on / extension.