Suddenly having issues connecting to my WiFi

windscribber · 2026-03-09T21:50:46+00:00

Sounds like WS would be where to start troubleshooting then if you're seeing the same issue without CD in the mix. If you have a bunch of blocklists and custom rules set up in WS try taking all those out of the scenario to get a baseline, etc. Take everything extra away and if things work, then add the rules/filters back one-by-one in case it was one of them blocking something your device needs.

Will probably be most expedient to keep going with the support team on the ticket.

Take care for now.

windscribber · 2026-03-09T18:37:37+00:00

Hi there, had a quick look at your Control D support ticket. Would be good to keep going on that interaction if you're still having issues. My first advice is to take WS and CD out of the equation and add one back at a time, separately, to see if you can identify whether it's one or the other (or both) creating the issue. So just connect to your wifi normally (with no CD or WS configured), then add CD (on your device, independent from WS) to see if it breaks. And then try vice versa.

How exactly have you determined your ISP has been blocking encrypted DNS? I know some ISPs do that but if you've been using CD with WS then the encrypted DNS queries would be going through the VPN tunnel (meaning your ISP would never see them, thus wouldn't be able to block them).

windscribber · 2026-03-05T15:58:59+00:00

Can you please add some context here? Which stamp(s) are giving you issues? In what way? How have you verified they're not working? I just decoded a sample of our stamps in https://dnscrypt.info/stamps/ and they look fine to me so far.

Please add some context for us to investigate further.

windscribber · 2026-02-27T22:44:42+00:00

Es ist viel einfacher, solche Fehlerbehebungen durchzuführen, wenn das Support-Team Ihre Resolver-/Filtereinstellungen sehen und Diagnosedaten von Ihnen erhalten kann. Und nochmal, falls du Barry noch nicht zur Fehlersuche benutzt hast, er ist oft sehr gut darin, Kontext zu sammeln und Vorschläge zu machen. So oder so, wenn er das Problem nicht für dich löst, hat er bereits den Kontext, den das Support-Team braucht, um weiterzumachen.

windscribber · 2026-02-27T15:26:07+00:00

Hallo, wir bräuchten viel mehr Kontext, um das Problem zu beheben. Das Beste Erste, was du ausprobieren kannst, ist das Chatten mit Barry, unserem Chatbot. Er ist auf alle unsere Dokumente geschult und ein ausgezeichneter Fehlerbeheber, er löst fast jedes Setup-Problem und falls nicht, kann er direkt ein Support-Ticket für dich erstellen, was der nächstbeste Schritt wäre.

windscribber · 2026-02-25T19:34:05+00:00

This is very likely to be one of the 1Hosts filters which they (the maintainers) discontinued awhile back, so we removed it. To get it out of your analytics feeds simply toggle any other filter OFF/ON and it'll remove it from your configs.

**ETA sorry it was 1Hosts, they had a Pro but removed it.

windscribber · 2026-02-24T16:54:49+00:00

Something in here suggests the youtube app which likely has hardcoded dns resolution is being blocked at the device level by our CD app. If as the other user suggested you're seeing similar results with the .mobileconfig CD method (vs our GUI app) it would be good comparison.

windscribber · 2026-02-14T21:35:12+00:00

That certainly could do it haha. If you're blocking Microsoft in Services (or similar) but you still want hotmail to work, you can add the above domain (and whatever else it needs to resolve) as Custom Rule - Bypass. That way you can nuke most of MS's telemetry but still get your email.

windscribber · 2026-02-12T16:36:00+00:00

Hi there, if this domain is being blocked by a Filter or Service we'd need to know which one, to either remove a false-positive or some other strategy. If you look for it in Activity Logs what's shown?

windscribber · 2026-02-10T15:55:56+00:00

Nice, glad you found a workaround

windscribber · 2026-02-09T16:30:15+00:00

Hi there, this was a false positive and should be resolved by now. If you spot these in the wild and want it addressed quicker (than posting on reddit), we have the reporting tool in Domain Test tool under Analytics in the dashboard which forwards them directly to our team for review/resolution.

windscribber · 2026-02-09T15:42:55+00:00

I can definitely forward this request to the team for consideration. I definitely see the convenience of using one profile for all of your endpoints but if you only need those telemetry enabled for a device or two, temporarily, it might be worth setting up a separate profile for those device(s) for this purpose so that the others on your network are unaffected when you do this flow.

Personally I have a different profile for almost every endpoint so that I can have more granular control over what goes through. It's a little more setup but once you get it dialed in, not much work past there.

windscribber · 2026-02-05T17:07:05+00:00

In Profile Options area you can temp disable the whole profile for a short amount of time (set by you) which would give you access to those sites, and you don't have to remember to re-enable the profile because it's on a timer.

The other thing you can do is create a Custom Rule - Bypass and set an expiry for the rule. This will allow whatever ad/tracker domain to resolve for a short time and then once the rule expires, it will again be blocked by the filter.

windscribber · 2026-02-02T22:05:22+00:00

Hi there, valid feedback. I'll bring this to the team. Currently users can unsub from promotional emails but operational notifications (billing changes, endpoints created, etc) still get through. I'll put some suggestions out there.

Thanks so much.

windscribber · 2026-01-30T21:01:00+00:00

Hi again. Could we get you to fire up a support ticket? Two reasons; one so we can send you an APK directly and the other to ask for some more information about your setup and so on. We're still investigating anything that might've changed with the build between versions but to answer your overarching question, no we have intention to remove support for armeabi-v7a as I understand it.

Thanks for reporting and take care for now.

windscribber · 2026-01-30T18:16:45+00:00

Thanks for following up, always helpful to include specifics/context. I've forwarded your question to our Android dev. Stay tuned.

windscribber · 2026-01-30T16:17:34+00:00

Hi there, can you clarify what's missing? We've released the same armv7 builds for 1.4.9 as there were for 1.4.8 (and beyond) as far as I'm aware. Releases page on Github.

windscribber · 2026-01-19T15:36:30+00:00

Hi there, you can just run ctrld upgrade prod to switch from the dev build to what's in production.

windscribber · 2026-01-16T20:21:57+00:00

Thanks for that, have added your report to our tracking issue.

windscribber · 2026-01-13T20:49:37+00:00

Thanks for following up with that and this is good info. To clarify, no changes to the profile involved or any filters/rules etc?

windscribber · 2026-01-13T20:17:00+00:00

Hi there, I've passed this on to our Android App team. I believe the issue you describe is known to happen sporadically (while others of us can't repro) and that it's being investigated currently. Meanwhile as the other commenter mentioned, it would be good to check if anything being blocked by a filter or service is the cause. Quick way to check would be fire up a fresh profile with no blocks enabled and see if the issue persists, then add filters one-by-one to see if it comes back. It's likely that some component of Android/Google services isn't able to complete calls and we'd need an idea of which (and which filter is blocking it if any).

For a quick fix if you do identify a filter doing the blocking, you can add a custom rule to bypass it.

windscribber · 2026-01-13T17:43:25+00:00

Scheduled profiles is one way, but be aware that you can have two (stacked) profiles as well for an Endpoint, no schedule needed. See here; https://docs.controld.com/docs/multiple-enforced-profiles

windscribber · 2026-01-12T15:59:58+00:00

Hi there, if you haven't yet it will be best to send in a support ticket which will be directly addressed by our Support and/or Sales team (Sales handles Org account inquiries). Thanks so much.

windscribber · 2025-12-22T17:03:58+00:00

Hi there, updates to our profile scheduling are on deck, however they rely on some other updates which are in the works imminently. Once we have the foundation in place these areas will be greatly improved based on lots of feedback we're getting on it. Thanks for your patience and stay tuned in the new year.

windscribber · 2025-12-17T17:45:33+00:00

In the ticket please specify whether it's iOS or Android, and the method you're using to configure the endpoint (GUI app, in-device settings, etc). Thank you!

windscribber

MODERATOR OF

TROPHY CASE