Cloud drive!

atamee, are you trying to login via a browser at drive.cox.com?  Works for me so the server isn't down.  Are you using the primary id on your account?  Do you have cookies disabled, if you don't accept cookies, Cox login will act as you described.

Hi Atamme,

Please set your browser to accept cookies and then try to log in at drive.cox.com. Let us know what happens!

I seem to be having trouble accessing Cloud Drive (again) too. On my Win7 machine, trying to access via a web browser, I am getting the runtime error again. On a Win10 machine using the Drag N Drop Backup pc app, login authentication fails.

This same problem was occurring a couple weeks ago, and it seemed to get ironed out. Now it's happening again.

Hi bneertmoed, What browser/version are you using? Please make sure you are using the primary Cox user id to login with. Check to make sure that you have cookies enabled. For more information on which browsers/versions are supported, please feel free to visit our webpage: http://bit.ly/1idqYRk  Also, check to make sure you have the latest available updates for your operating system and Anti-Virus software. I hope this helps.
 

Micheal... at the moment I am able to access Cloud Drive using both a web browser and the Drag N Drop Backup App. I'm using Internet Explorer and Google Chrome on a Win7 laptop, Internet Explorer and Google Chrome on a Win8 desktop, and Microsoft Edge and Google Chrome on a Win10 desktop.

This is how it tends to happen...when I can't access, it doesn't work for any browser on any machine, nor does the DNDB app allow me access. I get a runtime error when using a browser, and I get an authentication error on the app. There is no rhyme or reason to it. When one method of access fails, the other tends to fail also. Then, once I can access with one method, the other tends to work also.

Like I said, right now I can access, so that's good. But, this is how it's happened in the past. It works for a while (maybe days), but then at some point the errors return. Cookies are enabled, and all updates are done to the OS and antivirus (those are always kept very up-to-date).

This just seems to be a sporadic issue.

Do you happen to be using google or a non Cox DNS? Or are you using IPv6? Those are the two things I have isolated it to when it happens to me. As of now, all is well.

Thank you for the information. What versions are you using for the browsers? Please check them against the information in the link I sent you to make sure they are compatible.

Using Cox DNS. Not using ipv6.

As for browser versions, IE 11 and Chrome 49.

I don't think this is an isolated computer or an isolated browser problem. Reason being, it's not constant. It just doesn't work every now and then. I would think that if it were a browser/pc issue, it wouldn't work at all (unless I made some changes to a pc/browser). Even if changes were made to a pc/browser, that doesn't explain why when it happens on one machine that it happens on another machine simultaneously. And when the problem stops, Cloud Drive is accessible on all machines using any browser. Add to the fact that when I can't access via a browser (getting a runtime error message), the Drag N Drop Backup app won't allow access either. I get a failed authentication error with the app. But when the app starts allowing access again, so does access via browser.

I did have a problem a while back that perhaps the app would allow access but a browser wouldn't. And on other occasions, a browser would allow access, but the app wouldn't (authentication error). Those 2 scenarios haven't happened in a while. For the past couple weeks, it has been 'all or nothing'. Either the app and browser access works, or neither work.

Don't get me wrong. This problem doesn't seem to be happening all the time. For the most part, access via browser or app seem to work. But, this problem does periodically happen. I just thought I'd make mention of it so Cox would know that 'something' may be happening, and might warrant checking into it. :)

Well to be honest, I actually had a friend at Cox try to sign into my account and he could, at the exact moment I could not. Then later we both could without me changing anything.  So I agree it's not a browser issue or computer issue, but it doesn't seem to be the cloud server just going up and down. There is another layer, I just don't know what it is. I agree trying with the app when the site is down is a good test, but its working for me now so I can't.

Yeah...that's what makes this so bizarre. There is no real continuity with the 'problem'. As you said, at one point you couldn't access your account, but someone else could access your account (so the system itself was functioning).

The only 'constant' that I've had continuously is if I can't access via a web browser, changing browsers and/or changing computers did no good. If it was down via browser, it was down using any browser on any pc. Once it came back via browser, it came back using any browser/pc.

The only thing different that I've noticed recently (and maybe this is just happenstance) is being down via browser is simultaneous with being down via the Drag N Drop Backup app for PC. A couple/few weeks ago, if it was down for browser access, it may have been accessible via the app...or if it wouldn't access via the app, maybe the browser would work. At the moment (and maybe I just simply haven't caught it at the 'right' time), if it's down via browser, it's down via app. And if it's up via browser, it's up via app.

Pretty quirky situation. That would be tough to fully diagnose.

Well I noticed it started happening around the time they applied the fix for the phone tool issue caused by the Cox website UI change. See thread here.  The Cox Cloud is a skin on Zayo's cloud product, and there is a system that handles the transition between the Cox domain and that system.

Hmm, well this just got bizarre. I went to tracert to drive.cox.com to inspect that connection and looks like Zayo changed the IP for the website on their network and forgot to change the PTR. It now points to a website to buy Japanese audio equipment. I am going to go post this on DSLR for a laugh. I bet that breaks HTTPS.
 

Tracing route to drive.cox.com [216.7.172.22] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 20 ms 15 ms 12 ms 10.2.48.1
3 9 ms 9 ms 9 ms ip98-190-33-125.ri.ri.cox.net [98.190.33.125]
4 11 ms 15 ms 8 ms ip98-190-33-125.ri.ri.cox.net [98.190.33.125]
5 14 ms 15 ms 13 ms nyrkbprj01-ae3.0.rd.ny.cox.net [68.1.5.157]
6 16 ms 15 ms 15 ms 68.105.31.78
7 15 ms 15 ms 16 ms ae8.cr1.lga5.us.zip.zayo.com [64.125.26.161]
8 62 ms 63 ms 63 ms ae27.cs1.lga5.us.eth.zayo.com [64.125.30.250]
9 65 ms 65 ms 65 ms ae3.cs1.ord2.us.eth.zayo.com [64.125.29.209]
10 32 ms 31 ms 32 ms ae27.cr1.ord2.us.zip.zayo.com [64.125.30.243]
11 67 ms 63 ms 62 ms ae12.mpr1.den1.us.zip.zayo.com [64.125.20.250]
12 64 ms 65 ms 65 ms 208.185.23.10.t01440-06.above.net [208.185.23.10]
13 57 ms 57 ms 57 ms 41.ae2.cen01-mls-dc-core-b.cen01.latisys.net [205.214.65.142]
14 58 ms 57 ms 57 ms 205-214-65-122.static.eng01.latisys.net [205.214.65.122]
15 58 ms 57 ms 57 ms vl17.mls-dc-dist-c.eng01.latisys.net [208.42.224.18]
16 57 ms 58 ms 57 ms audiocubes.com [216.7.172.22]
Trace complete.

Domain	Type	Class	TTL	Response Time	Answer
Answer section:
22.172.7.216.in-addr.arpa.	PTR	IN	3600	29ms	audiocubes.com.
Additional section:
ns01.ash01.latisys.net.	A	IN	900	29ms	67.217.164.34
ns01.eng01.latisys.net.	A	IN	900	29ms	65.38.161.20
ns01.oak01.latisys.net.	A	IN	38400	29ms	208.78.168.154
ns02.ash01.latisys.net.	A	IN	900	29ms	67.217.164.35
ns02.eng01.latisys.net.	A	IN	900	29ms	65.38.161.21
ns02.oak01.latisys.net.	A	IN	38400	29ms	208.78.168.155