Most Corral issues fall into four situations. In each one, remember that Corral is fail-open by design: if anything upstream fails, traffic passes rather than being cut, so the device is never left offline.
A site is wrongly blocked
If a legitimate domain does not resolve, add it to the Admin Whitelist in the managed configuration, as a domain or a suffix. System-critical domains for the MDM and Google Play are always allowed and cannot be blocked. The change applies once the device picks up the new configuration.
A page will not load at all
Check the status screen first:
If it shows Not protected (Private DNS), the user has set a strict Android Private DNS. Ask them to set Private DNS back to Automatic, or set
private_dnsto Allow if you accept their resolver.If it shows Protected, the block is expected. Confirm the domain in the diagnostic report.
The Private DNS warning
A strict Private DNS bypasses Corral, so Corral shows Not protected and steps aside rather than leaving the device without name resolution. Enforce Private DNS = Automatic by device policy if you need filtering to be guaranteed.
Sending a diagnostic report
On the app's About screen, enter the admin code and choose Send a diagnostic report. It bundles diagnostics, recent crashes, blocked domains and the persistent log, ready to attach to a support request. It never contains a secret or an API key.

