Cannot login via web - "429 Client Error: Too Many Requests for url: https://ocapi-app.arlo.com/api/

[MichaelUrs]

Hi,

I cannot login to Arlo via the Website any more. The web requests fail with the error

"429 Client Error: Too Many Requests for url: https://ocapi-app.arlo.com/api/auth"

If I use a VPN so that I do have another IP address, then I can login without a problem.

What is the reason for this? Could you please urgently re-enable my IP address to be able to login again?

I can login via the Arlo app on the iPhone however. Although both are using the same Internet-facing IP.

Thanks a lot,
Michael

P.S. Unfortunately I can also no send a message to support via the web portal. It always say "Something went wrong. Please contact support" 😞

[StephenB]

---

@MichaelUrs wrote:

I cannot login to Arlo via the Website any more. The web requests fail with the error

"429 Client Error: Too Many Requests for url: https://ocapi-app.arlo.com/api/auth"

---

I haven't seen this one before.  What browser are you using?  

You might try using the private/incognito browsing mode, and see if that works differenty.

---

@MichaelUrs wrote:

P.S. Unfortunately I can also no send a message to support via the web portal. It always say "Something went wrong. Please contact support" 😞

---

This is with https://www.arlo.com/en-us/support/contact.aspx ?

[MichaelUrs]

Private mode and also other browser did not work .. As I said, only changing my Internet IP address did help. However, in the meantime I am able to login agin. Strange ....

[MichaelUrs]

Unfortunately I do have the same issue again this morning ;-(

[StephenB]

---

@MichaelUrs wrote:

Unfortunately I do have the same issue again this morning ;-(

---

Do you have internet security software running on the PC (for instance Kaspersky)?

[MichaelUrs]

No, I do not. Only Windows 10 Defender. Currently it is working again. So I have really no idea what the reason could be. Maybe it is nothing on my side but just something on the Arlo server side?

[StephenB]

---

@MichaelUrs wrote:

Maybe it is nothing on my side but just something on the Arlo server side?

---

No one else is reporting this symptom, and I am not experiencing it myself.

Support might be worth a try: https://www.arlo.com/en-us/support/contact.aspx