> ## Documentation Index > Fetch the complete documentation index at: https://docs.goguardian.com/llms.txt > Use this file to discover all available pages before exploring further. # Troubleshoot Why a Website Is Blocked in GoGuardian Admin > Identify what blocked a student — a policy rule, custom group, global config, Scene, or iFrame filtering — and how to allow the site. This article provides a workflow for troubleshooting and resolving students who are unexpectedly blocked by GoGuardian. ## Identify the Block Page Before troubleshooting, identify which block page the user sees. Different block pages indicate whether the site was blocked by GoGuardian Admin policies, Smart Alerts, GoGuardian DNS, GoGuardian Teacher Scenes, Google Admin Console, or something outside GoGuardian. See [Types of GoGuardian Block Pages](/products/admin/block-pages) for examples. Identify the Block Page ## Use the "Why Was This Blocked?" Feature Administrators can see which policy rule, custom group, global config setting, or GoGuardian Teacher Scene caused a block using the **Why was this blocked?** feature. The "Why was this blocked?" feature does not support GoGuardian DNS filtering blocks, YouTube video filtering, or embedded content blocked through iFrames. 1. Search for the student who saw the block page using the global search bar at [admin.goguardian.com](https://admin.goguardian.com/). 2. Under **Detailed Browsing History**, click the filter icon in the **Result** column to show only blocked history. 3. Click the kebab (three-dot) menu on the far right of the row containing the blocked URL. 4. Click **Why was this blocked?** to view the rule that caused the block. Student browsing activity dashboard filtered to only display Blocked results The popup shows the blocked URL, the name of the responsible policy, and the specific rule. For a policy block, click the policy link in the popup to adjust it and allow websites as needed. For more detail, see [Block and Allow Websites](/products/admin/block-and-allow-websites). Why was this blocked screen showing: Blocked URL, Policy, and rule causing the block ## Troubleshoot iFrame Filtering **Filter iFrame Content** is an optional setting in the Advanced Config section of GoGuardian Admin. When enabled, every user filtered by GoGuardian has their policy rules applied to iFrames embedded on a webpage. A student may then see a partial block page when the page is allowed but an embedded iFrame is blocked. Detailed Browsing History logs blocked and allowed websites, but does not list content blocked through iFrame filtering. Use one of the options below to identify the blocked iFrame URL. ### Option 1: Use the Inspect Tool 1. Right-click the page and select **Inspect**. 2. On the **Elements** tab, search (Ctrl+F on Windows and ChromeOS, Command+F on Mac) for `iframe`. 3. Look for a result that reads `iframe src=` followed by an HTTPS web address. 4. Hover over the matching `iframe src=` link to highlight the block page. Add the blocked iFrame URL as an allow rule in the user's policy to grant access. ### Option 2: Use the Bypass Password The Bypass Password temporarily unblocks blocked content. You can use it to surface a blocked iFrame URL in the logs. 1. Have the student go to the site with the blocked iFrame. 2. Have the student click **Bypass**, enter any password, and click **Submit**. Have the student click Bypass, enter any password, and click Submit. 3. In GoGuardian Admin, go to **Advanced Config** → **Bypass Password Attempts**. 4. Find the student's attempt and its corresponding URL, then add that URL as an allow rule in the student's policy. See [Configure Bypass Passwords](/products/admin/configure-bypass-passwords) for recommended best practices. Troubleshoot iFrame Filtering ## Contact Support If you are still troubleshooting, contact the GoGuardian support team by live chat or email. Include the blocked website or iFrame and the name or email address of the student.