-
-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to reach Ring server 9.x+ #397
Comments
Can you give v |
Still receiving an error on 9.5.0: Failed to reach Ring server at https://app.ring.com/rhq/v1/devices/v1/locations. queryA EREFUSED app.ring.com. Trying again in 5 seconds... Thanks for your work, it is very appreciated |
Do you have anything unique on your network setup? Like a pihole or something that does dns caching? |
Nothing that I know of. Mac mini goes straight to Linksys EA9500 router. Firewall on the Mac is off. I flushed the Mac dns before my original post. Before running on the Mac I was running homebridge on a FreeBSD platform with no problem. Just checked my FreeBSD platform with 9.5.0 and runs without issue. |
Can you set ‘“debug”: true’ in your ring config? Should log some additional info about the dns failure. Could also try node 14.5.0 but I’m not sure that will make a difference |
[7/11/2020, 12:59:24 PM] [Ring] DNS Cache for app.ring.com: {"errno":"EREFUSED","code":"EREFUSED","syscall":"queryAaaa","hostname":"app.ring.com"} |
There is definitely something in your server or network blocking the dns request. @dxdc any ideas? |
I agree. @doomstare please post the results of: scutil --dns
cat /etc/hosts
dig a app.ring.com
dig aaaa app.ring.com I'm wondering if it's an IPv6 issue, given that the aaaa query failed. |
Also, you may want to check the Security & Privacy system pref pane under System Preferences and confirm there is no issue with your Firewall (at least, you can disable it to test). And flushing your cache is an option too: dscacheutil -flushcache
sudo killall -HUP mDNSResponder |
@server ~ % scutil --dns resolver #1 resolver #2 resolver #3 resolver #4 resolver #5 resolver #6 resolver #7 DNS configuration (for scoped queries) resolver #1 @server ~ % cat /etc/hosts Host Databaselocalhost is used to configure the loopback interfacewhen the system is booting. Do not change this entry.127.0.0.1 localhost @server ~ % dig a app.ring.com ; <<>> DiG 9.10.6 <<>> a app.ring.com ;; OPT PSEUDOSECTION: ;; Query time: 14 msec @server ~ % dig aaaa app.ring.com ; <<>> DiG 9.10.6 <<>> aaaa app.ring.com ;; OPT PSEUDOSECTION: ;; Query time: 13 msec |
I don’t have firewall on and my ISP doesn’t provide ipv6 |
It's your DNS server (Comcast). You can see it here:
Also, it's very odd to me that you have 3 DNS entries, especially 2 local ones. Do you have some kind of double NAT issue with your router?
What are the settings in your System Preferences -> Network -> (default network) -> DNS? At a minimum, you should add Cloudflare or Google DNS. Comcast is not reliable: (just one example) |
@dgreif a few other thoughts:
btw, @doomstare I wonder if there is a maximum amount of dns hits on ring.com which is why (maybe) you'd be getting throttled by Comcast. |
Went into network settings and there was old Comcast dns info saved. I don’t use Comcast anymore. Cleared the dns info so it would pull from the router and it appears everything is working now. Thank you for you’re help! |
Glad it's fixed. You should still figure out why you're getting 2 different IP's for a local DNS (unless you had 2 entries loaded there). You don't need to have any DNS entries loaded in your Mac network settings, it will pull those automatically. |
Ya I cleared them all out. For some reason there were 3 ipv4 entries and almost a dozen ipv6 entries. I have my network default dns set to 1.1.1.1 and 1.0.0.1 |
Just experienced something similar on my HomeBridge setup:
...clearing the DNS cache/getting a new DHCP lease/restarting the networking service didn't resolve the problem, only restarting HomeBridge itself did. |
@washcroft whats your version of node, npm, ring plugin, and hb? Your dns config looks fine. Try adding |
node v12.18.2 |
Update your ring plugin. That should fix it! |
Bug Report
Describe the Bug
I am getting the following error when updating to any version 9.0 and up.
Failed to reach Ring server at https://app.ring.com/rhq/v1/devices/v1/locations. queryAaaa EREFUSED app.ring.com. Trying again in 5 seconds...
Rolled back every version until I hit 8.2.0 and everything was working again. Been searching for 2 days for similar issue but couldn't find anything
Environment
The text was updated successfully, but these errors were encountered: