Unable to login into Capital One Bank (capitalone.com) Topic is solved

[Pallid Planetoid]

Unable to login to the Capital One website.

Operating system: Win10
Browser version: 32.3.1
32-bit or 64-bit browser?: 32-bit
Problem URL: https://verified.capitalone.com/auth/signin?Product=ENTERPRISE.

I login monthly (to pay specific monthly bills) - the site has worked on Pale Moon within the past 30 days as I paid last months bills w/out any problems - note (FWIW), there have been two browser updates that fall within the time-frame of when I would possibly have successfully used the website last; v32.3.1(2023-07-18) and v32.3.0(2023-07-11).

The site hangs (never ending spinning circle) at this point (see screen-shot).

Tested using Safe-Mode (left website w/ spinning circle indicator [pointed out] that remained displayed as illustrated in the screen-shot below for over 10 minutes before finally closing the tab).

Works on other browsers of course (tested on Vivaldi).

Error Console (every time attempting to login):

Code: Select all

Timestamp: 8/4/2023 11:34:07 AM
Error: DataCloneError: The object could not be cloned.

seemingly a rather peculiar error

Login Screen-shot:

cap-1 login fails using Pale Moon.png

[njren]

This is the error I get using Pale Moon 32.3.1 on Win 7 64:

Code: Select all

ERROR DOMException [InvalidStateError: "An attempt was made to use an object that is not, or is no longer, usable"                     main-es2015.faf07e5c4cf7b6b0b4c6.js:1:201643
code: 11
nsresult: 0x8053000b
location: https://verified.capitalone.com/auth/main-es2015.faf07e5c4cf7b6b0b4c6.js:1]

Was able to access using Firefox on the same machine.

[Pallid Planetoid]

So njren, am I correct to assume you do have an account with Capital One 360? (otherwise you wouldn't be able to attempt a login ).

And if so, then I'm also assuming you are getting the never ending "spinning circle" indicator (see my screen-shot) - right? And do you recall when the last time you were able to successfully login using Pale Moon?

I know the site had to have worked for me on Pale Moon within the last 2-4 weeks for sure (and has worked for many years going back in time) - so whatever is the problem, it is a relatively recent issue (in my case).

Btw, is the "error" you get off the Pale Moon "Error Console"?

[Cassette]

I also saw the same issue as Pallid Planetoid with the same error in the console. Same O.S., but I'm using 64 bit Pale Moon. I know that I was able to log in somewhat recently, but I can't say when. It was after the web component/shadow dom being implemented for sure.

[Pallid Planetoid]

... I know that I was able to log in somewhat recently, but I can't say when. It was after the web component/shadow dom being implemented for sure.

In regards to "It was after the web component/shadow dom being implemented..." (as to an attempt to estimate when the issue might have started).
So I tried toggling dom.webcomponents.enabled to "false" - but it didn't help unfortunately (worth a try though).

[njren]

So njren, am I correct to assume you do have an account with Capital One 360?

Yes.

And if so, then I'm also assuming you are getting the never ending "spinning circle" indicator

Yes.

And do you recall when the last time you were able to successfully login using Pale Moon?

First week of July. I update Pale Moon upon notification, so I'm assuming I was using 32.2.1 at the time.

Btw, is the "error" you get off the Pale Moon "Error Console"?

Yes.

[therube]

Is the "Product=ENTERPRISE" part required?

Are you able to successfully log in from, https://verified.capitalone.com/auth/signin?

[Pallid Planetoid]

^ same (never ending in process spinning circle) result using your suggested alternative URL (https://verified.capitalone.com/auth/signin).

Thanks for the idea though.

To answer:

Is the "Product=ENTERPRISE" part required?

Probably not - I get the same login Interface either way (w/ either of the two URL's).

btw, circle still spinning - after about 6-7 minutes - so I'll close the tab at this point....

[MHartfield]

^ same (never ending in process spinning circle) result using your suggested alternative URL (https://verified.capitalone.com/auth/signin).

I'm not very "techie," but I just tried, using the "verified" url which I've been using, and I'm getting the endless "green circle. I'm accessing from Arizona, USA.

I've been using the "verified" url for some time now... last login couldn't have been more than a week or so ago and it was fine...

[Galaxy]

After disabling UBlock Origin from the Add-ons Manager, I am able to login to Capital One Bank using https://verified.capitalone.com/auth/signin

I am not using any other ad-blocker.

My User Agent Mode in Preferences is set to Firefox Compatibility.

I am not using a general.useragent.override for Capital One.

[Pallid Planetoid]

^ I'm unable to duplicate your results.

Using same "Firefox Compatibility" and not using a Useragent Override for the website login page (both of which I've been doing all along).

If I disable uBlockOrigin for the site I still get the spinning progress circle and nothing more.

If I disable the entire uBlockOrigin add-on I get the same thing as well.

If I run Pale Moon in Safe-Mode I can't even get the Capital One login page to render at all (using your URL link once again) - all I get is a completely blank login page (hence "Safe-Mode" is even worse).

I had previously tested all of the above - but did test once again, hoping that perhaps something changed.

[Pallid Planetoid]

Doing some more testing I did the following once again (had done this previously as well - but learned something I wasn't aware of).

1) Cleared all the Capital One cookies in Pale Moon.
2) Cleared all browser cache in Pale Moon.

What I noticed is if I leave the Capital One website tab open with the Capital One Bank login (so I am not loading or refreshing the bank login page) - I find that after removing all cookies from the website on Pale Moon the cookies remain removed (each time I check) until I close the "Page info" interface for the website and then once again using the "Page info" Interface again to check the cookies, I find the cookies have repopulated the site without my either loading or refreshing the page in the tab I leave open (I wasn't previously aware of this) - see asterisk (*) below.

Maybe this is to be expected - I would have thought that website cookies once removed would not repopulate until the website were either loaded or refreshed.

*It appears just checking the website for cookies again after closing the previously opened cookies "Page info" Interface causes the cookies to get repopulated. (again perhaps to be expected of which if that's the case then, I wasn't aware of this until now)

Regardless - nothing I can think to do makes any difference in my case.

[Pallid Planetoid]

For the record, using the alternate URL (some users have posted in this topic): https://www.capitalone.com/.

I get this:

using alternate URL.png

[Galaxy]

Update: Since switching from Crush Those Cookies 1.4.0 to Self-Destructing Cookies for Pale Moon 1.0.4.13, I can now use uBlock Origin 1.16.4.30 and still login to https://verified.capitalone.com/auth/signin without issue.

When I get logged in, it takes me to https://myaccounts.capitalone.com/accountSummary and uBlock Origin is blocking 44 requests on my Account Summary page.

I have the Self-Destructing Cookies add-on set up as follows:

Grace Period for cookies: 5 seconds
Notifications: check mark
Include LocalStorage for cleaning: check mark
Undelete for Cookies: not checked
Clear Browser Cache when idle: 1 minute
Strict Cookie Access Policy: not checked
Allow 3rd Party Tracking: not checked
Icon and Menu Entries: check mark

[Pallid Planetoid]

Hey Galaxy - what version of Pale Moon are you using? (going to "Help">"About Pale Moon" is where you'll find the version)

Btw, I've been using Self-Destructing Cookies for years and am using the same version of the add-on as you are with generally similar settings that in my case are likely "default" settings for the most part (I frankly can't see how much of any of your settings would make any difference actually - the impact of the add-on and settings occur after the fact, that is they impact the site after loading the website, not before - that is the website hangs, with spinning circle, as a result of initiating the login).

But I am curious what version of the Pale Moon browser is that you're currently using (depending on this - that could explain why the bank site works for you).

[Galaxy]

I am using 32.3.1 (64-bit) on Windows 7.

I changed my settings to the default on Self-Destructing Cookies and I can still sign in so you are correct, the settings are not that critical.

I should mention after entering my username and password, I get the following message which you never see because you can't get past the spinning circle: We noticed something different about this sign in. To provide you with the best protection, choose a 2-Step Verification method to verify your identity.

So apparently they are checking for something before they will let you log in.

But to your point, why changing from Crush Those Cookies to Self-Destructing Cookies even affects anything such as allowing uBlock Origin is unusual.

[Pallid Planetoid]

I am using 32.3.1 (64-bit) on Windows 7.

Hmm, so your on Windows 7 - I've only been trying the login on Window 10 (I wouldn't expect this to make a difference however)... but, let me check.

WOW - talk about "unusual" - this IS!!

The login works just fine on WINDOWS 7!!

So this has been the problem all this time? -- apparently so!

Hey Moonchild - here's an interesting development - the Capital One login that produces a never ending spinning circle (for a number of users, I might add) - is apparently a problem that exists when using WINDOWS10 - the problem doesn't exist on WINDOW7!! (at least for me).

Using my Windows 7 machine the Capital One login worked quick and flawlessly.

So myself and the other users with this problem logging into Capital One is apparently specific to Windows 10 (not sure about Win8 or Win11).

Now that I review the topic I see njren is also using Windows 7 (others with the problem have not specified OS) but is reporting the "spinning circle" issue... The one thing I don't know is if njren is using 32-bit or 64-bit for Pale Moon (I'm using 32-bit and the website works fine on Windows 7 for me).

So that's odd - I guess this issue is still a bit random (regarding OS).

OK, all I can say for sure is that I can login to Capital One using Windows 7 (64-bit) - but cannot on Windows 10 (get the problem reported in this topic) on Windows 10 (64-bit).

In my case this is using Pale Moon 32.3.1 (32-bit) on both my Windows 7 desktop and Windows 10 laptop.

So in my case the only difference is the Operating system all other parameters are the same; Windows 7 works, Windows 10 does not work in regards to the issue discussed in this topic.

[Pallid Planetoid]

Hey njren, you've reported having this issue discussed here with Capital One using windows 7 - question: are you using 32-bit or 64-bit for Pale Moon version 32.3.1?

I ask, because in my case the Capital One login works on Windows 7 using Pale Moon 32.3.1 (32-bit).

[Pallid Planetoid]

I am using 32.3.1 (64-bit) on Windows 7.

I should mention after entering my username and password, I get the following message which you never see because you can't get past the spinning circle: We noticed something different about this sign in. To provide you with the best protection, choose a 2-Step Verification method to verify your identity.

Thanks for all of your helpful feedback Galaxy - interesting (and unusual) development in that we are able to login to Capital One on Windows 7 (I've only been trying Windows 10 up until I noticed you were using Windows 7).

FWIW, however - I don't get the message about using "2-Step Verification method..." like you do on Windows 7. My login goes directly and very quickly to the bank without delay.

Makes me wonder if the hang-up on Windows 10 is this "2-Step Verification method..." message that is perhaps having an issue getting displayed on Windows 10 (but then I can't explain why I don't get the message on Windows 7, but would get it on Windows 10).

I've just now tested once again in Safe-Mode using Pale Moon 32.2.1 on Windows 10 to see if I still get the same unusual error in my Error Console.

Yep, still get the error:

Code: Select all

Timestamp: 8/15/2023 7:59:02 AM
Error: DataCloneError: The object could not be cloned.

There is a delay - after getting the "spinning circle" for awhile - however, the error does eventually show up.

[Pallid Planetoid]

It occurs to me that I should be comparing apples to apples here.

That is, I'm testing on Windows 10 (that has the problem with logging into Capital One, i.e. spinning circle issue) while using "Safe-Mode" (although the issue still exists on Windows 10 not using Safe-Mode as well).

But I haven't tested on Windows 7 (that so far does work regarding the Capital One website) using "Safe-Mode" (so the comparisons aren't exactly equivalent) - so here's the results comparing apples to apples.

As reported on Windows 10 - results are still "Spinning Circle" testing on Pale Moon using "Safe-Mode".

While I get successful Capital One logins (testing multiple times) on Windows 7 not using "Safe-Mode" hence with add-ons in use.

Here's my results on Windows 7 using "Save-Mode" (again, that does work flawlessly not using "Safe-Mode") I get different (failed) results (multiple times). The results are what you see below:

PM using 'Safe-Mode' logging into Cap1.png

I notice that without using "Safe-Mode" (i.e. using add-ons such as UblockOrigin for example) then the login is quick and works flawlessly. However, if I use "Safe-Mode" with Pale Moon then the login will momentarily (for a few seconds) delay (stutter) and then all I get is what you see in the screen-shot above. Basically fails to successfully login - what does render is what can be observed at the bottom of a successfully logged in page (see below) Notice what you see is the same thing at the bottom of a successfully logged in page.

Cap1- what you get at the bottom of a successful login.png

So the body of the page - that is all the account information fails to render when using Pale Moon using "Safe-Mode" on Windows 7.
However if doing the same (using Pale Moon on Windows 7) without using "Safe-Mode" the website renders successfully and without any delay or stuttering observed at all - basically a very quick and successful login under "normal" conditions on Windows 7 (yet on Windows 10 the best that happens is a forever "spinning circle").

I've tested all of this multiple times and find the results to be totally consistent.

Conclusion: Capital One will login successfully on Windows 7 however add-ons are necessary for the successful Capital One login to occur (absent add-ons the entire body of the website that consists of customer account information fails to render).