Troubleshooting
Common problems, and what to check first.
The browser doesn't enrol
- On the extension's settings page, the admin console section says what went wrong, such as a key that isn't valid.
- Open
chrome://policy(oredge://policy), select Reload policies, and checkenrolmentKeyshows with status OK under Browser Rules. - Check the extension ID in your policy matches the one on the extension's settings page.
- Check the computer can reach
console.browser-rules.com. Until it can, the browser keeps the default policies (or, once enrolled, the last policies it received).
A policy doesn't take effect
Browsers pick up changes within a few minutes. To check one straight away, select Sync now on its settings page, which lists the policies in force and any that were skipped, with why.
A website stops working
Add it to excluded websites in the admin console to confirm the extension is the cause. If it is, keep it excluded or tell us at [email protected]. Before a browser is enrolled, you can switch off the default policy that blocks it: see The default policies.
A large download is blocked
ZIPs over the size limit (128 MB unless changed in the admin console's General settings) can't be checked, so the matching policy's fallback decides, and the default policies block them. Raise the limit in the admin console, or add an Allow policy for the website the files come from.
Downloads take a moment longer
The extension fetches ZIPs (and, if the admin console checks every download's content, every download) to look inside them before saving. That's expected; checks stop after the time limit in General settings.