DOH, Dns, Pi-hole, and Hubitat

[spartysh32]

Here's the error I'm getting trying to run Hubitat Package Manager after updating my DNS and PiHole to DOH. My ring works by itself fine. Besides backing it out, curious if anyone has gotten this to work?
Will DOH not work with Hubitat?

Here's what I tried to implement: cloudflared (DoH) - Pi-hole documentation

The hub is no longer connecting.

System Messages

Cloud connection is unavailable.

My main issue at the moment is the unofficial Ring Integration app. Error Logs:
[dev:762](http://
device ip/logs#pastdev762)2022-01-06 06:19:59.401 am [info](http://device ip/device/edit/762) Socket (v4.1.9.9) | close() called

[dev:762](http://device ip/logs#pastdev762)2022-01-06 06:19:58.385 am [info](http://device ip/device/edit/762) Socket (v4.1.9.9) | initialize() called

[dev:762](http://device ip/logs#pastdev762)2022-01-06 06:19:56.369 am [info](http://device ip/device/edit/762) Socket (v4.1.9.9) | reconnectWebSocket() called delay: 2

[dev:762](http://device ip/logs#pastdev762)2022-01-06 06:19:56.318 am [warn](http://device ip/device/edit/762) Socket (v4.1.9.9) | Websocket Failure Message: failure: dp-gw-na-js.amazon.com

[dev:762](http://device ip/logs#pastdev762)2022-01-06 06:19:54.265 am [info](http://device ip/device/edit/762) Socket (v4.1.9.9) | close() called

[dev:762](http://device ip/logs#pastdev762)2022-01-06 06:19:53.249 am [info](http://device ip/device/edit/762) Socket (v4.1.9.9) | initialize() called

[dev:762](http://device ip/logs#pastdev762)2022-01-06 06:19:51.233 am [info](http://device ip/device/edit/762) Socket (v4.1.9.9) | reconnectWebSocket() called delay: 2

[dev:762](http://device ip/logs#pastdev762)2022-01-06 06:19:51.181 am [warn](http://device ip/device/edit/762) Socket (v4.1.9.9) | Websocket Failure Message: failure: dp-gw-na-js.amazon.com: Temporary failure in name resolution

[marktheknife]

Can you repost your log as a screenshot?

It’s hard to read when posted as plain text.

[spartysh32]

[sburke781]

Have you tried using that local DNS with another PC / laptop and testing how it performs?

[spartysh32]

Yea, everything else on my network going through that DNS was working fine.

I've disabled the service on the pi-hole, and my hubitat is the only thing still not reconnecting. Trying to retrace what else I've done. I tried restoring from a backup, still no good. Also removing all extra adlists from pihole, to see if that did something.

[nh.schottfam]

Also note that echo speaks is having web socket issues due to Alexa changing apis.

@tonesto7 has looked at correcting but has been waiting for the Alexa api changes to settle down.

[RELEASE] Echo Speaks V4

UPDATE: I apologize for not providing any updates on the WebSocket issues. I started working on changes over a month ago when Amazon killed the web-based WebSocket. I've found someone who has decoded the WebSocket that the amazon devices use. The issue is that in order for this to work I would have to port it over from Javascript to Java which in most cases is simple :|. But it's not simple when working with crypto and binary functions. The other issue is the libraries that are allowed on Hu…

[thebearmay]

Don't recall anyone saying they were using DNS over HTTP (DoH) directly with HE before. A simple way to check if that is the issue would be to set the DNS server back to 8.8.8.8 and see if that resolves the issue (may want to reboot after setting it). If it does resolve then you have conclusive proof that the DoH is the issue, if it doesn't resolve the issue then it's on to the next potential cause.

[spartysh32]

Was able to get the hub back online. I'll look more at this, as well as the 8.8.8.8 mentioned by @thebearmay.

Seeing my ring devices no longer connecting.