Fix a site that stopped working
Blocking a request a page depends on can stop the page working. A login that never completes, a video that will not start, and a checkout that hangs are the usual shapes.
Confirm the cause
- Open Blue Guard.
- Go to Settings.
- Under Protection, turn off Safari blocking.
- Reload the page.
If the page works, blocking was the cause. If it does not, turn Safari blocking back on. The problem lies elsewhere, and leaving it off achieves nothing.
Test one mechanism at a time. Turning both off tells you a blocker was involved but not which one, and they are fixed differently.
Allow the site
For a site you use regularly, add it to your allowed sites and turn blocking back on.
- Go to Settings > Exceptions > Allowed sites.
- Add the site's domain.
- Reload the page.
An allowed site is exempt from every category and from custom rules. It is an exception, not a weakening of anything else.
When allowing does not fix it
If the site still misbehaves with blocking off entirely, Blue Guard is not the cause. Content blockers are a common first suspect because they are a recent change, and often they are not responsible.
If it works with Safari blocking off but not with the site allowed, the broken request is coming from a domain other than the one in the address bar. Allow that domain too. A page that loads its payment form from a separate provider needs the provider allowed, not the page.
Reduce blocking instead of ending it
If several sites break in the same way, a whole category may be at fault rather than a single site.
Turn categories off one at a time under Settings > Filters, and retest after each one. Annoyances is the usual candidate, because hiding page elements can remove something the page turns out to need. Choose what to block describes what each category covers.
What is stored
Allowed sites are stored on your device and applied to both blocking mechanisms. Nothing about which sites you allowed is sent anywhere, and Privacy and data covers the rest of what the app keeps.