Loading...
Loading...
Found 3 Skills
Use when the user reports connectivity issues, access failures, DNS resolution problems, or any error with Twingate. Activate for: "can't connect", "not working", "resource not found", "access denied", DEAD connector, DNS not resolving, device trust blocking access, security policy issues, P2P failure, or any Twingate troubleshooting or diagnostic request. Also activate for symptom-shaped and error-string queries: exact client error text ("unknown network name", "too many open files", "setup wizard ended prematurely", "unable to join network"), OS-specific client bugs on Windows, macOS, Linux (Fedora, Ubuntu, NixOS), ChromeOS, or Android Auto; client crashes, freezes, or unresponsiveness; version-specific regressions (e.g. a specific client build number misbehaving); TAP adapter or virtual network adapter issues; device posture / screen lock / disk encryption check failures; third-party AV, EDR, VPN, or DNS-filtering software conflicts (CrowdStrike, Zscaler, Elastic AV, Avast, consumer VPNs); packet capture, system report, or client/connector log collection; and engaging or escalating to Twingate technical support.
Readiness checklist for homelab VLAN segmentation, local DNS filtering, and WireGuard-style remote access before changing router, firewall, DHCP, or VPN configuration.
Twingate Internet Security — DNS filtering, exit networks, browser security, and DNS-over-HTTPS. Load when the user mentions DNS filtering, content filtering, internet security, exit networks, egress routing, browser security, NextDNS, DoH, DNS categories, or profile priority. Also trigger on 'Internet Security', 'DNS Security Profile', 'fixed egress IP', or 'SaaS allowlisting' in a Twingate context. Also activate for DNS conflicts and symptom-shaped DNS queries: a third-party DNS filter or AV product conflicting with Twingate (Cisco Umbrella, DNSFilter, AdGuard, Avast Real Site Protection), CGNAT range conflicts (`100.96/12`), multiple-network-interface DNS resolution problems, "all nameservers have failed", DNS request delays on Linux, a Docker container's second DNS query returning the wrong IP, or a personal/DIY exit-network VPN built on Twingate.