ring: v9.0.0 - Failed to Reach oauth.ring.com
Bug Report
Describe the Bug
Since installing v9.0.0, Ring plugin is no longer able to connect to Ring oauth URL. Everything was working great in the previous version, no issues. I’ve unlinked account multiple times. I’ve uninstalled the plugin multiple times. I’ve restarted my routers and I’ve also hit the https://oauth.ring.com/oauth/token URL successfully from the Raspberry directly. It can ping oauth.ring.com as well.
Is there a way to revert back to an older version of the Ring plug to confirm that one still works?
To Reproduce
Steps to reproduce the behavior:
- Start Homebridge
- Attempt to start Ring plugin
- See error [Ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token. Trying again in 5 seconds…
Expected behavior
It would connect to Ring oauth URL
Screenshots/Logs
[6/5/2020, 1:33:45 PM] Homebridge is running on port 51626. [6/5/2020, 1:33:45 PM] [Ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token. Trying again in 5 seconds… [6/5/2020, 1:33:50 PM] [Ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token. Trying again in 5 seconds… [6/5/2020, 1:33:55 PM] [Ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token. Trying again in 5 seconds… [6/5/2020, 1:34:00 PM] [Ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token. Trying again in 5 seconds… [6/5/2020, 1:34:36 PM] [Ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token. Trying again in 5 seconds… [6/5/2020, 1:34:41 PM] [Ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token. Trying again in 5 seconds… [6/5/2020, 1:34:46 PM] [Ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token. Trying again in 5 seconds… [6/5/2020, 1:34:51 PM] [Ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token. Trying again in 5 seconds… [6/5/2020, 1:34:56 PM] [Ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token. Trying again in 5 seconds…
Additional context
Add any other context about the problem here.Homebridge Ring Config
Post homebridge-ring platform config without sensitive information
{
"refreshToken": "xxxx",
"platform": "Ring"
}
Environment
- OS: Raspbian
- Node.js: 12.14.1
- NPM: 6.14.5
- homebridge-ring: 9.0.0
- homebridge: 1.1.0
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 1
- Comments: 26 (10 by maintainers)
To wrap this one up in case others run into the same thing.
Looks like in my Pi build, the systemd-networkd-wait-online.service was disabled which allowed the HomeBridge service to start before the network services were up. To fix this, run the command below as su in your Pi to enable the service then reboot the Pi. Once it comes back, this will force HomeBridge to wait for the network to be available before starting.
systemctl enable systemd-networkd-wait-online.service
9.3.2 totally fixed it for me. Restarted via config UI twice and it’s worked without error both times! Great work
No worries at all, it’s easy enough to delay the service start. I messed with so many setting yesterday to try and get this to work, it’s possible I screwed something else up. I’m just glad we got to the bottom of it.
Thanks for your quick work and assistance. Version 9 is so much quicker and cleaner with the live streams!