Technical Anshu
Tutorials Blog
🧰 Troubleshooting

Website Blocked by Mistake Use the Block Event Report and Pass Site

The filter blocked a site your team genuinely needs. Do not unblock the category and do not guess — the report already knows what happened.

✍️ Technical Anshu🛡️ Untangle / Arista NG Firewall⏱️ 6 minute read
🎥 Watch the full setup in the video — Web Filter categories, Pass Site and reports, step-by-step

Every category filter eventually blocks something legitimate. The video's troubleshooting flow is the professional way to handle it: Block Event report first, Site Lookup second, Pass Site last — an exception measured in one domain, not a category surrendered in a panic.

Web Filter — Block Event Report
Time User Site Category Policy ------------------------------------------------------------------ 09:41 hr-pc-04 careers-portal.in Job Search HR Passed 10:02 hr-pc-04 training-videos.com Streaming HR Blocked 10:03 hr-pc-04 training-videos.com Streaming HR Blocked (retry)
Illustration of the Block Event report — user, site, category and policy on one line. Values are examples.
1

Start from the Report, Not from the Complaint

The complaint arrives as 'your filter broke my work'. The Block Event report turns it into facts: the exact domain, the category that stopped it, the policy and the time. Half of all 'wrongly blocked' stories end right here — the site was blocked exactly as designed, and the conversation becomes about policy, not about a broken filter.

  1. Open the Web Filter's Block Events / reports view
  2. Find the user's attempts by time, user or device
  3. Note the domain and the category recorded for the block
2

Check the Label with Site Lookup

Run the domain through Site Lookup. Two different problems hide behind the same complaint: the category is correct and the policy is doing its job (a training site that really is filed under Streaming), or the category is wrong and the database mislabelled a work tool. The remedy is the same, but knowing which one you have tells you whether to expect more surprises from that category.

3

Pass the Site — One Domain, One Policy

The Pass Site list is the surgical fix the video demonstrates: the exact domain is allowed even though its category stays blocked. Keep the exception narrow — pass it only on the policy that needs it, and pass the domain, not the whole category.

  1. In the Web Filter for that policy, open the Pass Site list
  2. Add the exact domain from the report
  3. Save, then ask the user to try again while you watch the report
4

Write the Exception Down

Every pass entry is a small hole in a category you chose to block. Keep a simple note — site, reason, date, who asked. When the list is reviewed (and it should be, a few times a year), exceptions nobody can explain get removed. An unaudited pass list quietly becomes the real policy.

🎥 See It Done Live in the Video

The complete Web Filter setup on the HR policy — blocking categories, passing a site and reading the block report — is shown on screen in the full video.

▶️ Watch Full Video
❓ Common Questions (FAQ)

The block page is all the user sent me. Is that enough?

It is a good start — the block page names the site and usually the category. Confirm in the Block Event report anyway: it shows the exact domain (sites often load helper domains), the policy that fired, and every retry.

Should I pass the site for all policies or just one?

Just the policy that needs it. Passing a domain on every policy widens the exception far beyond the person who asked, and quietly changes rules for departments that never had the problem.

The site works now but its videos or login still fail. Why?

Many sites load content from other domains — video CDNs, login providers, payment pages. The report shows each blocked helper domain as its own event; pass the ones that are genuinely part of the same service.

This guide is based on the Technical Anshu video linked above • Stuck on a step? Ask in the video comments — that is where answers come from 🙏