api.ring.com resolving to 127.0.0.1
<!--
Please DO NOT DELETE THIS TEMPLATE or your issue may be closed immediately.
Before opening an issue, search for open and closed GitHub issues that match your situation.

If this is a Live Stream issue please go back and use the Live Streaming issue template.
-->

# Bug Report

### Describe the Bug
<!-- ✍️edit: --> After restarting homebridge-ring works briefly. I am able to change the system status from home to away and vice versa using HomeKit. However, after a few times it stops working. Instead I get errors every five seconds in the homebridge log that homebridge is unable to reach the Ring server. From the error it seems that it is resolving api.ring.com to 127.0.0.1.

### To Reproduce
Steps to reproduce the behavior:
 - Start Homebridge
 - Attempt to change state of system several times.
 - See error: [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/dings/active.  connect ECONNREFUSED 127.0.0.1:443.  Trying again in 5 seconds...

### Expected behavior
<!-- ✍️edit: --> Expect state to change.


### Screenshots/Logs
<!-- ✍️edit: -->[Ring] Failed to reach Ring server at https://api.ring.com/clients_api/dings/active.  connect ECONNREFUSED 127.0.0.1:443.  Trying again in 5 seconds....

### Additional context
<!-- ✍️edit: --> 

### Homebridge Ring Config
Post homebridge-ring platform config  _without sensitive information_
```

{
            "refreshToken": "xxx",
            "sendDoorbellMotionNotificationsToTv": true,
            "platform": "Ring"
        }

```

### Environment
<!-- ✍️edit: -->
 - OS: Mac OS
 - Node.js: v14.17.1
 - NPM: 8.3.0
 - homebridge-ring: v.9.23.0
 - homebridge: v.1.3.8
