Failed to reach Ring server error #497

jmac0027 · 2020-11-21T05:04:24Z

I've tried everything with no success. I am still getting the error: Failed to reach Ring server at https://oauth.ring.com/oauth/token. unable to verify the first certificate. Trying again in 5 seconds...

DNS is working fine. Network working fine. Restarted everything. Error began after most recent ring and config ui x update.

homebridge-ring v9.12.5
homebridge-config-ui-x v4.34.0
Node.js Version v14.15.1
NPM Version v6.14.9

Originally posted by @jmac0027 in #496 (comment)

dgreif · 2020-11-21T05:19:19Z

This error is related to ssl and missing certificates. I haven't ever seen it before and as far as I know you are the only use that has run into this. Do you have anything weird set up with ssl certificates? What version of node are you on?

jmac0027 · 2020-11-21T05:23:07Z

Negative regarding ssl. I am running a basic setup.
Versions are:
homebridge-ring v9.12.5
homebridge-config-ui-x v4.34.0
Node.js Version v14.15.1
NPM Version v6.14.9

jmac0027 · 2020-11-21T07:12:22Z

As much as I hated to do it, I had to delete the plugin because the error was hitting every 5 seconds. All other plugins are working without issue. I even tried: npm config set strict-ssl false. It's very strange. I never setup SSL. The only other installation on the Pi is a Unifi Controller. The IP is fixed as well.

dgreif · 2020-11-21T14:38:51Z

If it was working fine on 9.12.4, I'd suggest you try downgrading to that version to see if you still have errors. You can install specific versions through the homebridge ui. Let me know if that version works.

jmac0027 · 2020-11-21T17:10:51Z

From testing, v9.12.2 and lower work without any errors. When I try v9.12.3 the plugin won't even start. Version above that cause the certificate error. Prior to this testing I did a full removal of the plugin.

mac-n-cheese-uk · 2020-11-21T19:14:44Z

I'm seeing this on v9.12.5 too - I'm running HOOBS v3.2.10/Node v12.19.0.

Going to try downgrading now to see what works

dsrigby · 2020-11-21T20:50:24Z

I too have been getting this error starting with 9.12.4 and now 9.12.5

Running vanilla homebridge with same versions as jmac0027

paqpaqpaq · 2020-11-22T10:37:32Z

Same issue here, went back to 9.12.2, since that seems to be 'bug-free' for/to me.

dgreif · 2020-11-22T21:15:32Z

What's weird is the only impactful changes after 9.12.2 were dependency updates. It's going to be a challenge to track down exactly which dependency is causing the issue, especially since I can't recreate the unable to verify the first certificate issue. I just bumped all the dependencies again in 9.12.6. If someone could give that version a try and let me know if it's any better than 9.12.5, that would be great!

dsrigby · 2020-11-22T22:07:34Z

Upgraded to 9.12.6 and it seems to be behaving much better in my situation. Not sure if it's just my imagination, but it seems to be more responsive too as I go in/out of live view.

mac-n-cheese-uk · 2020-11-22T22:34:14Z

No dice for me I'm afraid - still getting a sea of errors although it's altered slightly and I now get:

[Ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token. Client network socket disconnected before secure TLS connection was established. Trying again in 5 seconds...

schpeen · 2020-11-23T01:45:48Z

11/22/2020, 8:44:16 PM [Ring] Failed to reach Ring server at https:// oauth.ring.com/oauth/token. connect ECONNREFUSED 127.0.0.1:443. Trying again in 5 seconds...

That's what I keep getting even after updating

schpeen · 2020-11-23T01:52:29Z

How do i roll back to a previous versions ?

jmac0027 · 2020-11-23T02:24:59Z

I also receive the error with version 9.12.6. Reverted back to v9.12.2.

jmac0027 · 2020-11-23T02:34:07Z

Schpeen if you are using config ui there will be a circle arrow. Click that and select the version you want. As I stated, v9.12.2 works for me.

dgreif · 2020-11-23T03:46:20Z

@dxdc @Sunoo @smockle @apexad any of you running into issues on the versions 9.12.4/9.12.5? I can't recreate any of the issues other than the original NGHTTP2_ENHANCE_YOUR_CALM in #496 and would appreciate any help in debugging this unable to verify the first certificate error if any of you are seeing it.

Sunoo · 2020-11-23T03:49:28Z

Haven’t noticed any problems lately, I just quickly tested the latest version and all functionality appears to be working fine.

apexad · 2020-11-23T03:52:03Z

No issue here.
Curious if it is possibly a Node 12 issue? I am on 14.15.1

Sunoo · 2020-11-23T03:52:42Z

I’m still on 12.

dgreif · 2020-11-23T03:54:45Z

I tried both with no issues and I think some users are having issues on both. Reverting to ring 9.12.2 seems to fix it for those having issues. Basically just dependency bumps since then so it's not clear what went wrong. Thanks for checking for me!

paqpaqpaq · 2020-11-23T05:50:56Z

Upgraded to 9.12.6 and it seems to be behaving much better in my situation. Not sure if it's just my imagination, but it seems to be more responsive too as I go in/out of live view.

Same here!
Seems faster than ever.

Edit:
No srsly, on ring pro:
< 1 sec. locally, and about 2 sec. from a different network

Ring 2 is about 1 sec. 'slower'.

schpeen · 2020-11-23T14:32:55Z

@jmac0027 I am using Hoobs how could I do it using that? thanks for help.

dxdc · 2020-11-23T16:59:08Z

No issues here. Few ideas, @jmac0027

Confirm time/date is set correctly. If time/date is wrong, it can cause SSL verification issues.
Are you running through a proxy server or have some kind of firewall set up?
sudo apt-get update && sudo apt-get -y --reinstall ca-certificates

schpeen · 2020-11-23T18:35:32Z

@dxdc Time is correct, nothing changed on my network all was working well before the update. Also tried to run sudo command you posted and it said it was unable to download. I am using hoobs any easy way for me to roll back update? I am still learning with all this homebridge stuff so appreciate help.

dxdc · 2020-11-23T18:49:01Z

Maybe try sudo update-ca-certificates

dxdc · 2020-11-23T19:04:30Z

it said it was unable to download

This may be another issue affecting your install

schpeen · 2020-11-24T00:31:06Z

can anyone please tell me how to re install version 9.12.2 using hoobs. I tried to run the npm for that version and copied and put in terminal but thats not working I must be doing something wrong.

apexad · 2020-11-24T01:01:47Z

can anyone please tell me how to re install version 9.12.2 using hoobs. I tried to run the npm for that version and copied and put in terminal but thats not working I must be doing something wrong.

You'll have to consult HOOBS support.

jmac0027 · 2020-11-24T03:29:17Z

Thanks for the suggestions dxdc. I did try those prior to posting. I don't run a proxy and firewall is on my USG.

dxdc · 2020-11-24T04:28:59Z

Seems like a HOOBS -related issue, relating to SSL verification. There's a seemingly related issue here:
hoobs-org/HOOBS#478

I imagine that you'll trigger the same error using a basic curl request too.

Please post the results of this command:
openssl s_client -showcerts -connect oauth.ring.com:443

Maybe something there will be diagnostic. You can also try:
curl -kvvv https://oauth.ring.com

dgreif · 2020-12-12T19:44:57Z

@LordZork @mreassassin 9.12.9-beta.1,2 and 3 are up. Each updates some of the dependencies. I expect that you will see the NGHTTP2_ENHANCE_YOUR_CALM error after one of the updates, so let me know which work and which fail (including the error message you get when it fails). If they all work fine, then there is one more dependency change I can make, but wanted to start with these first. I also noticed that the NGHTTP2_ENHANCE_YOUR_CALM error didn't always happen right away, so if they all seem good, trying running them for a little while to make sure. Thanks in advance!

DMBlakeley · 2020-12-12T20:29:33Z

This is an observation that I have on my network ... I have been running the last several releases of homebridge-ring without issue including the 9.12.8 version. Snapshots and live video worked just fine.

This morning I changed my network mask from 255.255.224.0 to 255.255.255.0 based on another app's recommendation. Snap shots continued to work but live video stopped. I tried 9.12.7, 9.12.6, 9.12.5, 9.12.9-beta.1 and beta.3. Sill the same behavior. I then changed the mask back to 255.255.224.0 and both snap shots and live are back working with 9.12.8.

Why did I have the mask at 255.255.224.0 you may ask? A couple months ago I moved from an Apple AirPort Time Capsule to a Linksys MR9600 WiFi-6 router. I had all sorts of issues so I started troubleshooting by copying over the configuration that I had on the AirPort and this is how the Linksys settings have remained. 255.255.224.0 was the default for the AirPort.

Not sure if related but thought I would pass on.

mreassassin · 2020-12-12T21:14:59Z

@dgreif beta2 seemed to work for a bit then stopped responding on HK and started this

If I wait for a few Minutes it comes back online.

Beta 1 and 3 never seemed to respond for me.

mreassassin · 2020-12-12T21:30:25Z

Beta 3 gave these errors.

LordZork · 2020-12-12T21:38:48Z

@dgreif

[FIRST TRY]

9.12.9-beta.1

Installed...

reboot – no errors or issues
reboot – no errors or issues

9.12.9-beta.2

Installed...

reboot – errors (below), but no [noticeable] issues:

[12/12/2020, 15:04:20] [Ring] 404 from endpoint https://api.ring.com/clients_api/ring_devices
[12/12/2020, 15:04:20] [Ring] Session hardware_id not found. Creating a new session and trying again.

reboot – no errors or issues

9.12.9-beta.3

Installed...

reboot – no errors or issues
reboot – no errors or issues

[SECOND TRY]

9.12.9-beta.2

Installed...

reboot – no errors or issues
reboot – no errors or issues

[NOTES]

I will leave 9.12.9-beta.2 running for the rest of the afternoon, until sometime this evening (unless I encounter issues), and then revert to 9.12.9-beta.1 and let that run over night. Then I will run 9.12.9-beta.3 tomorrow morning, and I will report back.

dgreif · 2020-12-13T14:12:58Z

@DMBlakeley you issue is definitely unrelated. Changing the subnet mask will impact which devices on your network have access to each other. 255.255.255.0 means 192.168.1.xxx can see each other. 255.255.224.0 is a bigger range of ips that can see each other. This is 100% specific to your network and not related to the plugin in any way.

@mreassassin @LordZork I ran beta.3 over night and woke up to a log full of NGHTTP2_ENHANCE_YOUR_CALM errors. The good news is this means I can reproduce the remaining issue on my end and won't be as dependent on your responses to continue working on a fix. If either of you ran beta.2 for an extended period of time, please let me know how it went. Either way, this is definitely helping to narrow down the dependency that caused the issue.

LordZork · 2020-12-13T18:16:34Z

@dgreif

I had intended on running beta.2 for only part of yesterday (until the evening), then switching. However, I forgot and left it running over night (until now). I just scrolled through the logs, and I only see one error:

[12/12/2020, 16:56:44] [Ring] Ring beams_bridge_v1 XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX is offline or on cellular backup. Waiting for status to change

[I replaced the alphanumeric string with Xs]
I'm guessing this is my Ring Bridge. A few minutes later, it came back online:

[12/12/2020, 16:59:44] [Ring] Ring beams_bridge_v1 XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX has come back online

Everything seems to be running fine with no issues and no other errors.

I just now reinstalled beta.1 (still no errors after reboot) and will let it run over night. I plan to report back tomorrow.

LordZork · 2020-12-14T07:30:47Z

@dgreif

I've been running beta.2 for about 13 hours, and I just checked the logs and am showing a few errors:

[13/12/2020, 17:16:52] [Ring] Request to https://api.ring.com/clients_api/snapshots/timestamps failed with status 504. Response body: {"error":"Gateway Timeout","status_code":504}
[13/12/2020, 17:16:52] [Ring] Response code 504 (Gateway Timeout)
[13/12/2020, 17:16:52] [Ring] Failed to cache snapshot for Side (3.313s), The camera currently reports that it is online

[13/12/2020, 18:23:53] [Ring] Request to https://app.ring.com/api/v1/mode/location/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX failed with status 500. Response body: <html>
<head><title>500 Internal Server Error</title></head>
<body>
<center><h1>500 Internal Server Error</h1></center>
</body>
</html>

HTTPError: Response code 500 (Internal Server Error)
    at Request.<anonymous> (/usr/local/lib/node_modules/homebridge-ring/node_modules/got/dist/source/as-promise/index.js:117:42)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5) {
  code: undefined,
  timings: {
    start: 1607905431821,
    socket: 1607905431822,
    lookup: 1607905431822,
    connect: 1607905431822,
    secureConnect: 1607905431822,
    upload: 1607905431822,
    response: 1607905433862,
    end: 1607905433862,
    error: undefined,
    abort: undefined,
    phases: {
      wait: 1,
      dns: 0,
      tcp: 0,
      tls: 0,
      request: NaN,
      firstByte: 2040,
      download: 0,
      total: 2041
    }
  }
}
HTTPError: Response code 500 (Internal Server Error)
    at Request.<anonymous> (/usr/local/lib/node_modules/homebridge-ring/node_modules/got/dist/source/as-promise/index.js:117:42)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5) {
  code: undefined,
  timings: {
    start: 1607905431821,
    socket: 1607905431822,
    lookup: 1607905431822,
    connect: 1607905431822,
    secureConnect: 1607905431822,
    upload: 1607905431822,
    response: 1607905433862,
    end: 1607905433862,
    error: undefined,
    abort: undefined,
    phases: {
      wait: 1,
      dns: 0,
      tcp: 0,
      tls: 0,
      request: NaN,
      firstByte: 2040,
      download: 0,
      total: 2041
    }
  }
}

[I replaced the alphanumeric string with Xs]

Everything seems to be working fine currently, though. Also, I just rebooted and got no errors. I think I will revert back to beta.0 (though I may wait until the morning) – let me know if you need me to test any of these again, or any others.

jmac0027 · 2020-12-17T03:49:20Z

Good Day - After updating my node to v14.15.2 from 14.15.1 I tried the default upgrade for Ring. Again I was getting the same unable to verify the first certificate error. Then I tried v9.12.9-beta.3 and I am very happy to say the error has gone away!!! Thank you dgrief for your relentless hard work. I also updated myQ plugin. Other than those three things nothing else was changed in my config to get it working. Hope this helps. JM

dgreif · 2020-12-26T15:08:27Z

I have done a bunch of testing with the 9.12.9 betas and here's what I've found so far:

The unable to verify the first certificate error goes away if we use HTTP2 for requests. HTTP2 was disabled in 9.12.5 to fix a different issue - NGHTTP2_ENHANCE_YOUR_CALM from 9.12.4 no longer talks to server reliably #496.
The NGHTTP2_ENHANCE_YOUR_CALM error seemed to have started in 9.12.4, but I was able to reproduce the issue on older versions like 9.12.2. I think this is actually caused by changes on Rings servers, and they are now terminating connections under certain conditions with rate limiting or session expiration. I haven't pinned down the exact issue yet, but if I can get that figured out, then I can re-enable HTTP2 and the unable to verify the first certificate issue should go away for everyone.

For now, anyone having the unable to verify the first certificate issue can install 9.12.2

jmac0027 · 2021-01-01T17:57:46Z

I installed version 9.13.0 and it immediately began giving me the "unable to verify the first certificate error" I had to revet back to v9.12.9-beta.6.

lishan89uc · 2021-01-07T14:37:06Z

9.13.0
every day around 11:45 am and 11:45 pm:

[1/6/2021, 11:47:54 PM] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/ring_devices.  queryAaaa ENOTIMP api.ring.com.  Trying again in 5 seconds...
[1/6/2021, 11:47:54 PM] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/dings/active.  queryAaaa ENOTIMP api.ring.com.  Trying again in 5 seconds...

dgreif · 2021-01-08T17:31:11Z

@jmac0027 @LordZork can you give 9.14.1-beta.1 a try? Seems like Ring isn't causing issues with http2 anymore, so we should hopefully be able to merge this back in. I'm going to run it for a few days and see if I get any issues

lishan89uc · 2021-01-08T22:02:01Z

I have been on 9.14.1 beta 1 for a day or so. The live view is hit and miss however at least it is semi working. I still am getting many errors saying it can’t connect but it actually can. Lol

jmac0027 · 2021-01-09T07:17:41Z

@dgreif 9.14.1 beta 1 is working just fine.

LordZork · 2021-01-09T07:46:20Z

@dgreif, I have been on 9.14.1-beta.1 for a few hours. As @lishan89uc mentioned, the live view is hit and miss, but mostly working. Sometimes it's video only (no audio) on the first attempt. Once or twice the live stream did not work, at all, but then worked after closing the Home app and trying again. I've only noticed one error (below), but it seems to happen almost every time – if not every time – I activate a live stream.

[09/01/2021, 01:34:40] [Ring] Ding XXXXXXXXXXXXXXXXXXX is expired (480).  Fetching a new ding and trying video stream again
err:  Error: remote peer disconnected
    at TLSSocket.<anonymous> (/usr/local/lib/node_modules/homebridge-ring/node_modules/sip/sip.js:584:43)
    at TLSSocket.emit (events.js:327:22)
    at endReadableNT (internal/streams/readable.js:1327:12)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)

#497

dgreif · 2021-01-11T05:29:18Z

Ok, 9.14.1 has been released and uses http2 without any dns caching or keepalive agents. Let me know how it works for you @jmac0027.

@LordZork @lishan89uc the live stream issues are unrelated to this issue, and are something I'll hopefully get to in the near future. Short explanation is that Ring is slowly rolling out new media servers that I have working but not working perfectly. That's why the streams are hit or miss. Same can be said for audio even if the video stream works. I'll probably open a new issue to track that problem.

jmac0027 · 2021-01-15T00:31:28Z

Dgrief - 9.14.1 is working great! Thank you.

steveura · 2021-01-15T18:39:59Z

Unfortunately I have 9.14.1 and am getting the dreaded NGHTTP2_ENHANCE _YOUR_CALM error when I try to look at my Ring Pro or Ring 2. If I restart Homebridge, I can successfully view the camera once, but then I get this error on the subsequent viewing. Any thoughts?

dgreif · 2021-01-15T18:51:20Z

@steveura Please see #548 (comment). You just need to update NodeJS and the error will go away.

steveura · 2021-01-15T22:06:37Z

Thanks for the quick reply - that did the trick!

mreassassin · 2021-01-15T23:40:51Z

I did a npm update now I'm getting this anytime I try to view the live camera feed.

dgreif · 2021-01-16T06:19:07Z

@mreassassin that error may happen occasionally but shouldn't happen every time. 480's normally happen when you try multiple streams in close succession. If it continues, open a new GitHub issue

fredsocial · 2021-05-04T20:32:04Z

I have the same issue on a brand new installation. See #633

fredsocial · 2021-05-04T20:38:27Z

@dxdc Running the command on a new RPi4 installation: openssl s_client -CApath /etc/ssl/certs/ -connect oauth.ring.com:443
I got the following:
CONNECTED(00000003)
depth=0 C = US, O = Circle Media Inc., CN = Circle002
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 C = US, O = Circle Media Inc., CN = Circle002
verify error:num=21:unable to verify the first certificate
verify return:1

Running the same command on a RPi3 I got this:
openssl s_client -CApath /etc/ssl/certs/ -connect oauth.ring.com:443
CONNECTED(00000003)
depth=2 C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert Global Root CA
verify return:1
depth=1 C = US, O = DigiCert Inc, CN = DigiCert SHA2 Secure Server CA
verify return:1
depth=0 C = US, ST = California, L = Santa Monica, O = Ring LLC, CN = *.ring.com
verify return:1

Both RPis are on the same network. Ring plugin works on the RPi3 but not on the RPi4.

It seems to be a certificate issue ("[Ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token. unable to verify the first certificate. Trying again in 5 seconds...")

I'm using the latest homebridge image:
OS: Raspbian GNU/Linux Buster (10)
Node.js: v14.16.1
NPM: v7.11.1
homebridge-ring: 9.18.0
homebridge: v1.3.4

@dgreif
Note: I downgraded to 9.12.2 and that didn't fix the certificate issue.

CAVACO-PT · 2021-11-09T21:15:44Z

Having this issue on homebridge

[11/9/2021, 9:08:51 PM] [Ring] Failed to reach Ring server at https://app.ring.com/api/v1/mode/location/ getaddrinfo EAI_AGAIN app.ring.com. Trying again in 5 seconds...
[11/9/2021, 9:08:55 PM] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/ring_devices. getaddrinfo EAI_AGAIN api.ring.com. Trying again in 5 seconds...

homebridge: v1.3.5

homebridge-ring v9.23.0

Node.js Version | v16.13.0

Npm Version v8.1.0

danhrainey · 2022-07-05T01:15:29Z

I started getting this similar error with the 11.0.2 Ring Plugin update. Does not occur every time or for very long. Only seems to be on the Ring Pro DoorBell Cam.
I don't ever see it on the Stickup and Outdoor Stickup cams. The Doorbell cam is the oldest of the bunch. If it keeps occurring I will replace it and see if the errors still occur.

Hoohs Version 4.2.5
Node Version 16.15.1
HameBridge Version 1.4.1
Unbuntu 20.04 (running in VM)
Ring Plug in 11.0.5

ERROR
8:29:43 PMRing BridgeRingErrorFailed to reach Ring server at https://app-snaps.ring.com/snapshots/next/110000040. Timeout awaiting 'request' for 20000ms. Trying again in 5 seconds... ( I modified the sequence numbers in the web addresses for posting to protect the innocent LOL :) )

Only occurs from a few minutes then it clears up.
8:29:31 PMRing BridgeRingStopped Live Stream for Front Door8:29:31 PMRing BridgeRingconnectionStateChange: closed8:29:31 PMRing BridgeRingiceConnectionStateChange: closed8:29:43 PMRing BridgeRingErrorFailed to reach Ring server at https://app-snaps.ring.com/snapshots/next/110000040. Timeout awaiting 'request' for 20000ms. Trying again in 5 seconds...8:29:48 PMRing BridgeRingErrorFailed to reach Ring server at https://app-snaps.ring.com/snapshots/next/860000034. Timeout awaiting 'request' for 20000ms. Trying again in 5 seconds...8:29:48 PMRing BridgeRingErrorFailed to reach Ring server at https://app-snaps.ring.com/snapshots/next/550000027. Timeout awaiting 'request' for 20000ms. Trying again in 5 seconds...8:29:48 PMRing BridgeRingErrorFailed to reach Ring server at https://app-snaps.ring.com/snapshots/next/450000053. Timeout awaiting 'request' for 20000ms. Trying again in 5 seconds...8:30:08 PMRing BridgeRingErrorFailed to reach Ring server at https://app-snaps.ring.com/snapshots/next/110000040. Timeout awaiting 'request' for 20000ms. Trying again in 5 seconds...8:30:09 PMRing BridgeRingErrorFailed to reach Ring server at https://app-snaps.ring.com/snapshots/next/550000027. Timeout awaiting 'request' for 20000ms. Trying again in 5 seconds...8:30:10 PMRing BridgeRingErrorFailed to reach Ring server at https://app-snaps.ring.com/snapshots/next/860000034. Timeout awaiting 'request' for 20000ms. Trying again in 5 seconds...8:30:13 PMRing BridgeRingErrorFailed to reach Ring server at https://app-snaps.ring.com/snapshots/next/860000034. Timeout awaiting 'request' for 20000ms. Trying again in 5 seconds...8:30:13 PMRing BridgeRingErrorFailed to reach Ring server at https://app-snaps.ring.com/snapshots/next/550000027. Timeout awaiting 'request' for 20000ms. Trying again in 5 seconds...8:30:13 PMRing BridgeRingErrorFailed to reach Ring server at https://app-snaps.ring.com/snapshots/next/450000053. Timeout awaiting 'request' for 20000ms. Trying again in 5 seconds...8:30:13 PMRing BridgeRingErrorFailed to reach Ring server at https://app-snaps.ring.com/snapshots/next/110000040. Timeout awaiting 'request' for 20000ms. Trying again in 5 seconds...

maga8637 · 2024-03-16T10:28:49Z

Hey, yesterday i installed the RING plugin, after finally getting my homebridge up to date. Ring was working fine in Homekit but after i changed the setting for movement detection in my Ring-App i lost connection in Hiomekit. Changeing the settings back was not helping either. I logged back into the ring plugin but that was also not helping. I also tried to downgrade to a previous version without any results. I sillt get the error message:
Failed to reach Ring server at https://app.ring.com/api/v1/mode/location/TOKEN. getaddrinfo EAI_AGAIN app.ring.com. Trying again in 5 seconds...
Any ideas?

dgreif added a commit that referenced this issue Jan 11, 2021

fix: remove keepalive and dns caching in favor of http2

fcfd2a6

#497

dgreif closed this as completed Jan 15, 2021

Failed to reach Ring server error #497

Failed to reach Ring server error #497

Comments

jmac0027 commented Nov 21, 2020

dgreif commented Nov 21, 2020

jmac0027 commented Nov 21, 2020

jmac0027 commented Nov 21, 2020

dgreif commented Nov 21, 2020

jmac0027 commented Nov 21, 2020

mac-n-cheese-uk commented Nov 21, 2020

dsrigby commented Nov 21, 2020 • edited

paqpaqpaq commented Nov 22, 2020

dgreif commented Nov 22, 2020

dsrigby commented Nov 22, 2020

mac-n-cheese-uk commented Nov 22, 2020 • edited

schpeen commented Nov 23, 2020 • edited

schpeen commented Nov 23, 2020

jmac0027 commented Nov 23, 2020

jmac0027 commented Nov 23, 2020

dgreif commented Nov 23, 2020

Sunoo commented Nov 23, 2020

apexad commented Nov 23, 2020 • edited

Sunoo commented Nov 23, 2020

dgreif commented Nov 23, 2020

paqpaqpaq commented Nov 23, 2020 • edited

schpeen commented Nov 23, 2020

dxdc commented Nov 23, 2020

schpeen commented Nov 23, 2020

dxdc commented Nov 23, 2020

dxdc commented Nov 23, 2020

schpeen commented Nov 24, 2020

apexad commented Nov 24, 2020

jmac0027 commented Nov 24, 2020

dxdc commented Nov 24, 2020 • edited

dgreif commented Dec 12, 2020

DMBlakeley commented Dec 12, 2020

mreassassin commented Dec 12, 2020

mreassassin commented Dec 12, 2020

LordZork commented Dec 12, 2020 • edited

[FIRST TRY]

9.12.9-beta.1

9.12.9-beta.2

9.12.9-beta.3

[SECOND TRY]

9.12.9-beta.2

[NOTES]

dgreif commented Dec 13, 2020 • edited

LordZork commented Dec 13, 2020

LordZork commented Dec 14, 2020 • edited

jmac0027 commented Dec 17, 2020

dgreif commented Dec 26, 2020

jmac0027 commented Jan 1, 2021

lishan89uc commented Jan 7, 2021

dgreif commented Jan 8, 2021

lishan89uc commented Jan 8, 2021

jmac0027 commented Jan 9, 2021

LordZork commented Jan 9, 2021

dgreif commented Jan 11, 2021

jmac0027 commented Jan 15, 2021

steveura commented Jan 15, 2021

dgreif commented Jan 15, 2021

steveura commented Jan 15, 2021

mreassassin commented Jan 15, 2021

dgreif commented Jan 16, 2021

fredsocial commented May 4, 2021

fredsocial commented May 4, 2021 • edited

CAVACO-PT commented Nov 9, 2021 • edited

danhrainey commented Jul 5, 2022

maga8637 commented Mar 16, 2024

dsrigby commented Nov 21, 2020 •

edited

mac-n-cheese-uk commented Nov 22, 2020 •

edited

schpeen commented Nov 23, 2020 •

edited

apexad commented Nov 23, 2020 •

edited

paqpaqpaq commented Nov 23, 2020 •

edited

dxdc commented Nov 24, 2020 •

edited

LordZork commented Dec 12, 2020 •

edited

dgreif commented Dec 13, 2020 •

edited

LordZork commented Dec 14, 2020 •

edited

fredsocial commented May 4, 2021 •

edited

CAVACO-PT commented Nov 9, 2021 •

edited