406 Not Acceptable - attempting to authenticate

[GrahamReddie]

Is there an existing issue for this?

• I have searched the existing issues

Describe The Bug

This is running on a Synology box and originally worked for many months but then I think the token needed refreshing for some reason.

When I attempt to login either in the homebridge interface or in a terminal session using "ring-auth-cli" I'm prompted for the username and password but then it comes back with this:

TypeError: Cannot use 'in' operator to search for 'error' in

<title>406 Not Acceptable<title> 406 not Acceptable

---

openresty

at RingRestClient.getAuth (/volume1/@appstore/homebridge/app/lib/node_modules/ring-client-api/lib/rest-client.js:263:119)

To Reproduce

No response

Expected behavior

I'm expecting for a new token to be issued.

Relevant log output

No response

OS

Linux

Node.js Version

20.9.0

NPM Version

10.9.0

ring-client-api

13.2.1

Operating System

Linux DS1 4.4.302+ #69057 SMP Fri Jan 12 17:02:28 CST 2024 x86_64 GNU/Linux synology_geminilake_224+

[GrahamReddie]

[tsightler]

The 406 error generally means that your IP has been blocked. Usually this is caused by use of VPN or running the code in some service where Ring has banned entire IP blocks. However, Ring also sometimes temporarily blocks IPs based on what they would consider "abuse", for example, lots of connections for different accounts from the same IP, multiple attempts to request tokens too frequently, or access using an invalid token being attempted over and over. These blocks are generally temporary, if you stop all connections for 24 hours and try again it is usually fine.

In summary, unless the Ring API changes in a way that causes everyone to get 406 errors, there's generally not anything that can be done with it on the code side, however, when that happens, there will typically be dozens of reports in short order, so I don't think that is the case here.

[GrahamReddie]

Ah bugger ! I forgot I had that machine on a VPN !!!! You're 100% correct - sorry it just hadn't crossed my mind but obvious now you say it! I'll post back too to confirm if that turns out to be correct for me.

Thanks again, most appreciated

[GrahamReddie]

Yep! spot-on - VPN was still running on that machine! thanks you 👍