Netflix login issue

[Tomaso]

Are anyone else having problems logging in to Netflix now, using Pale Moon?
I keep getting a BS message that says "Incorrect password".
If I use Chromium-ungoogled, or a dedicated device, then the login works just fine.
A search on the web confirms that this is a known Netflix error, often related to their handling of multiple devices.
Apparently, this gets messed up sometimes, resulting in blacklisted "devices".
But since I also found reports which indicates that the error can be related to a whole lot of other things, I thought I'd check by here first, before contacting them about it.

[satrow]

Latest PMx32 on W7, logged out, cleared cookies, fresh reload, login successful.

Playback is another story, as usual. Some weeks it's fine, others impossible. Maybe next Tuesday it will decide to work again.

[billmcct]

I don't have a problem logging in, however I have all the relevant Netflix cookies related to login saved and protected. (as so for many many more sites)
Therefore every time I open Netflix I'm automatically logged in.

Try logging in, in Chrome and looking in the Netflix account settings and use "log out of all devices".
Don't know if it will help but can't hurt. You'll just have to log back in.
As Satrow said clearing cookies may help.

[Tomaso]

Thanks for testing, but I've already tried that, and all other "obvious" solutions.
Perhaps someone using the latest Pale Moon version, and who doesn't store cookies could try too?

[RealityRipple]

I use Self-Destructing Cookies for Pale Moon with a 1 second grace period, block third-party cookies from non-visited sites, and clear my history every time my browser closes, and I just logged into Netflix with no problem. 28.13 x64 on Win10.

[Tomaso]

OK, thanks for confirming!

[Tomaso]

As expected, it was "not possible" to get this solved through Netflix customer services, since "Pale Moon isn't a browser that they support", according to their "experts", as she called them.
That's it, apparently!.. and there wasn't room for any further discussions regarding the subject.
Although, they openly admitted that this was a known problem, which they've been getting several reports about lately!
(In hindsight, I guess I should have said that I was using Firefox)

--

EDIT:
Basilisk still works just fine BTW, after applying PM's new UA override for netflix.com / netflximg.net.
I'll simply log in at Netflix, using this browser, from now on.

[Kudalufi]

I just started having the exact same issue today. Frustrating.

[Kudalufi]

Interestingly this problem exists on all installations of Pale Moon in Windows or Linux. Running Pale Moon in safe mode in Linux allows me to log in to Netflix, though I of course cannot play anything because Silverlight is not available. Running in Safe Mode in Windows has the same problem. Have deleted cache, tried with a brand new profile, safe mode. Nothing works.

EDIT: And the fix shouldn't be switching to a new browser.

[Tomaso]

At least, for me, the problem isn't consistent anymore.
Usually, login still fails on the first attempt, but now it often works on the second one.
Whatever type of new verification check Netflix has adopted, it's obviously flawed, and they should look into fixing it!
At the very least, they should make sure that proper error messages are shown, instead of this misleading BS about having entered a "incorrect password"!!

There are several errors in Pale Moon's logger (including "Content Security Policy" warnings), when accessing https://www.netflix.com/login/
Don't know if any of them are directly related to this specific issue though.

[Kudalufi]

If I make enough attempts then it switches from incorrect login to "Sorry, something went wrong. Please try again later." But it never, ever works any more with Pale Moon.

Whatever type of new verification check Netflix has adopted, it's obviously flawed

And yet it works with Firefox, Chrome, and even actual Internet Explorer.

[ron_1]

Whatever type of new verification check Netflix has adopted, it's obviously flawed

And yet it works with Firefox, Chrome, and even actual Internet Explorer.

So what if it works in other browsers? You're implying that Tomaso's statement is wrong. I've been here long enough to know that that is not necessarily the case, and in all probability it's probably correct. The problem is with Netfix only supporting the "big boys." All complaints should be directed to them.

[Moonchild]

And yet it works with Firefox, Chrome, and even actual Internet Explorer.

And you somehow think this isn't an arbitrary check, but a technical issue, if MSIE is thrown into the mix?
Well, if you can tell me exactly what we're doing wrong on the browser side, I'll be more than happy to look into it, but you'll find that that will be fruitless because it's all server-side.
Only the server can compare credentials to what they have in the database and throw back a "wrong password" error. That is purely on their end.
On the browser side we are following standard rules for standard form controls for log-in. All of that is well-defined over the past few decades. Our connection and overall browser security is also tip-top. So what else is there to do for us? Not like we're some half-assed rebuild that has a broken engine because of bad configuration, here.

[Kudalufi]

If it were purely server side, then setting the user agent to mimic Firefox exactly should cause the exact same result as using Firefox, which is a successful login. As you well know, and shouldn't have to be recapitulated here, most login forms are not just straight posts any more. There is often scripting, sometimes complex scripting, involved on the client side for username and/or password pre-processing and sometimes also a complex interplay between the browser and several other servers for RECAPTCHA (or other login scrubbing system) purposes.

If this is the case, is Netflix part of the problem? Absolutely. Overly complex and fragile login systems are the responsibility of the site. But is Pale Moon also part of the problem? If something client-side is not behaving as expected, then yes, it is also part of the problem. Brushing it off as automatically Somebody Else's Problem is not helpful to anyone. Investigate, don't investigate, that's up to you. But just don't oversimplify the issue and brush it off.

[coffeebreak]

A thought occured, that I can't personally examine because I don't have a Netflix account, but here it is...

On loading their login page, I notice that they use reCaptcha.
Is it the silent variant of reCaptcha?

If so, is it possible that people are silently failing the reCaptcha?

[Tomaso]

is it possible that people are silently failing the reCaptcha?

Good catch, coffeebreak!
Indeed, this appears to be the very heart of the issue!!
..and luckely (and somewhat unexpected, I might add) the damn thing isn't required, because blocking it actually seems to solve the problem!

After having added this rule to my filters in uBO, Netflix login now works every time!:

Code: Select all

/recaptcha/$important,domain=netflix.com

PS: Depending on your filter combo, the $important syntax (not ABP-compatibe) is needed, to bypass various whitelistings and such.

We should test this for a while.
If the blocking rule doesn't cause any unforseen issues, I'll have it added to uBO's Legacy filter (unless someone comes up with an alternative solution, like possibly tweaking PM's UA overrides for Google?).

[coffeebreak]

the $important syntax (not ABP-compatibe) is needed, to bypass various whitelistings.
[...]
If the blocking rule doesn't cause any unforseen issues, I'll have it added to uBO's Legacy filter.

If reCaptcha is indeed the problem, that should help people who use uBO.
But it helps only them.

People with Netflix accounts should contact them specifically about reCaptcha being set up with discriminatory criteria.
Websites do, afaik, have choices about how reCaptcha is set up, and maybe if they hear from enough people, they'll improve it.

[adesh]

But is Pale Moon also part of the problem? If something client-side is not behaving as expected, then yes, it is also part of the problem. Brushing it off as automatically Somebody Else's Problem is not helpful to anyone. Investigate, don't investigate, that's up to you. But just don't oversimplify the issue and brush it off.

Off-topic:
Of course, Pale Moon is involved here but is it at fault? What is it that Pale Moon is doing wrong? You should know that debugging these modern websites is very hard and more so when they don't provide helpful messages about what went wrong. Also, primarily it's website owner's responsibility to make their websites work across browsers, and it's not difficult if they follow common web standards to write browser agnostic code. A browser cannot reasonably chase after millions of websites to be compatible.

[New Tobin Paradigm]

Don't forget it is all about the Google Monoculture here. Webkit doesn't matter and Gecko is just Google's second vote in WhatWG and the W3C is merely just Google's 3rd party documentation and has no real power anymore.

And we are just scum.

Besides, I seriously question why anyone these days wants to use Pedophile Netflix.

[Tomaso]

is Pale Moon also part of the problem?

Well, after blocking all of the recaptcha stuff, the Content Security Policy errors in Pale Moon's browser console (which I mentioned before) went away.
So, I guess if there's anything to investigate at Pale Moon's end, this would probably be it:

Code: Select all

Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified