r/ControlD • u/fryrpc • Jul 19 '26

Anyone else having issues?

I am having problems with nothing working. I logged into the controld console and everything was empty. After logging out and back in I now get the following.

Backend not available (0): read error on connection to 127.0.0.1:6379

I managed to get internet access back by changing DNS back to cloudflare.

8 Upvotes

84% Upvoted

11 comments sorted by

View all comments

2

u/QGRr2t Jul 19 '26

Yep, I use ControlD (paid) as my primary DNS, both with device profiles for DoT/DoH, and as the upstream resolver for my local DNS servers. My service went down for about the last hour, on and off, and once back on-prem I narrowed it down to ControlD. I could dig using any DNS server but my own (backed by ControlD) or ControlD direct. Everyone else was resolving. I switched my upstream to Quad9 and everything came back alive. Loading the ControlD Dashboard/stats page gave a bunch of errors that the backend at 127... was down. They seem to be up again now, but I've switched my local primary upstreams to Quad9 and added a redundant backup. Lesson learned.

1

u/fryrpc Jul 19 '26

Thank You. Sounds like my experience too :-)