authentication error

[c3p0vsr2d2]

Seeing an authentication error for the past week or so ... is anyone else noticing similar issues?

[burner1024]

Doesn't work for me all.
Doesn't help that error messages are cryptic, even with debug settings on.

[twrecked]

@burner1024 not going to disagree, but what are you seeing? If you paste something in here I might be able to let you know what is going wrong.

[burner1024]

authentication failed
authentication failed

That's it.

[twrecked]

If you know your Arlo username and password this will be a cloudflare issue.

I guess I had been thinking about this recently. I just pushed a branch I've been working on - https://github.com/twrecked/pyaarlo/tree/better-errors

Can you try it? I started on it a few months ago and I'm not sure what state it is in and I won't get a change to try until later but it might help you.

[burner1024]

login failed: 403 - possible cloudflare issue
login failed: 403 - possible cloudflare issue

Strangely, sometimes I get

error in new response={'meta': {'code': 400, 'error': 9204, 'message': 'Browser is not trusted'}}
login failed: 2fa: no secondary choices available
login failed: 403 - possible cloudflare issue

When running exactly same code.

[twrecked]

Welcome to Cloudflare - where the errors are made up!

Try changing some of the values mentioned here.

These are done from with arguments to PyArlo not with aarlo.yaml, but I hope it makes sense.

[twrecked]

The 2fa thing might be working. Do you have 2fa set up for this account?

[burner1024]

Yes. I don't think there's an option to not set it up, is there?

[twrecked]

I need how you are calling PyArlo and some debug.

You can use this link to encrypt the output.

[burner1024]

Thank you for your assistance @twrecked.
It appears that the IP address from which I was testing was simply blocked by Cloudflare. Playing with ecdh_curve and user agent didn't help. (I finally just visited https://ocapi-app.arlo.com/ in browser, and it didn't even offer a captcha, just straight up block). Maybe due to multiple login failures, maybe just Cloudflare algos going crazy.

It works intermittently on another IP. I'll try some more debugging later.

Some suggestions:

• For bettter errors, if there's something like data-translate="blocked_why_detail">This website is using a in body, it's not a "possible" cloudflare issue, but a definite one.
• On the other hand, once there's pyaarlo - WARNING - error in new response={'meta': {'code': 401, 'error': 9015, 'message': 'Password not correct'}}, I think there's no point in retrying, can exit directly (right now it retries multiple times).

[twrecked]

Thanks for trying the new code. Cloudflare is always fun (!) to debug, I have 2 machines on the same network that need different setting to make them work...

Sometimes you just have to wait a few hours for Cloudflare to reset something. It might work later.

And suggestions noted, I'll get them into the error branch.