[Ring] Failed to reach Ring server at https://api.ring.com/clients_api/ring_devices. getaddrinfo ENOTFOUND api.ring.com.

[arakylien]

Is there an existing issue for this?

• I have searched the existing issues

Describe The Bug

In homebridge logs:
[3/17/2024, 10:26:17 AM] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/ring_devices. getaddrinfo ENOTFOUND api.ring.com. Trying again in 5 seconds...
[3/17/2024, 11:05:24 AM] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/ring_devices. getaddrinfo ENOTFOUND api.ring.com. Trying again in 5 seconds...
[3/17/2024, 11:07:31 AM] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/ring_devices. getaddrinfo ENOTFOUND api.ring.com. Trying again in 5 seconds...
[3/17/2024, 11:08:17 AM] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/ring_devices. getaddrinfo ENOTFOUND api.ring.com. Trying again in 5 seconds...

After a Homebridge restart:
3/17/2024, 11:11:14 AM] Please add [Porte d'entrée 51D5] manually in Home app. Setup Code: ###. <== Last log from starting
[3/17/2024, 11:20:05 AM] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/ring_devices. getaddrinfo ENOTFOUND api.ring.com. Trying again in 5 seconds...

To Reproduce

Random.
Unsure since when as I restarted setting up a home bridge device from scratch 1 week ago.

Expected behavior

Unsure if this is from Ring servers or from your package.
All Ring related features from your Homebridge plugin are running fine meanwhile.
In HomeKit, all seem to run fine.

Relevant log output

No response

Screenshots

No response

Additional context

No response

OS

Linux

Node.js Version

v20.11.1

NPM Version

v10.2.4

ring-client-api

v12.1.0

Operating System

Debian 12

[tsightler]

getaddrinfo ENOTFOUND api.ring.com

This is quite simple, the plugin is unable to resolve the hostname. This is not directly a plugin issue, it can be caused by network issues, DNS issues, conflicts with older, non-updated plugins that do things which break the internal NodeJS network functions, etc. but there's nothing than can be done to resolve this from a plugin perspective.