Home Troubleshooting Block Page Not Displaying Correctly

Block Page Not Displaying Correctly

Last updated on Apr 17, 2026

Block Page Not Displaying Correctly

When KyberGate blocks a website, it shows a branded block page with the reason for blocking and a "Request Access" button. If this page isn't appearing correctly, this guide helps diagnose and fix the issue.

Before You Begin

  • Note what you're seeing instead of the block page (blank page, browser error, timeout, generic error)
  • Check if the issue affects all blocked sites or specific ones
  • Test on multiple devices to determine if it's device-specific or fleet-wide

Understanding the Block Page

KyberGate's block page features:

  • Cream/coral branded design with your school's name
  • Block reason (category, keyword match, or policy rule)
  • Request Access button for students to submit unblock requests
  • Displayed during the CONNECT phase — before the TLS handshake, so no certificate is needed for the block page itself

Common Issues and Solutions

1. Blank White Page Instead of Block Page

Cause: The browser is failing to load the block page resources.

Solution:

  1. Verify the device can reach *.kybergate.com — this domain must be accessible for the block page to load
  2. Check your school firewall isn't blocking KyberGate's own domains
  3. Clear the browser cache and try again

2. Browser Certificate Error Instead of Block Page

Cause: The browser is attempting to establish TLS directly with the blocked domain before the proxy can serve the block page.

Solution:

  1. Ensure the KyberGate root certificate is installed and trusted on the device
  2. Deploy the certificate via MDM for automatic trust
  3. For HSTS-pinned domains (some banking, Google services), this is expected behavior — the browser's security prevents any interception

3. Connection Timeout Instead of Block Page

Cause: The proxy is dropping the connection instead of serving a block page.

Solution:

  1. Check your proxy configuration — verify the PAC file URL is correct
  2. Test connectivity to the proxy: visit https://proxy.kybergate.com/health from the device
  3. If the health check fails, check your network/firewall settings

4. Generic Browser Error (ERR_PROXY_CONNECTION_FAILED)

Cause: The device cannot reach the KyberGate proxy servers.

Solution:

  1. Verify the device has internet connectivity
  2. Check that outbound ports 443, 80, and 8080 are open in your firewall
  3. Ensure proxy.kybergate.com and regional proxy domains are not blocked
  4. Try switching the device to a different network to isolate the issue

5. Block Page Shows but Request Access Doesn't Work

Cause: The Request Access button requires connectivity to KyberGate's API.

Solution:

  1. Ensure api.kybergate.com is accessible from the device
  2. Check that the student is logged in / identified — anonymous devices may not have the Request Access option
  3. Verify Request Access is enabled in Settings → Block Page → Request Access

Customizing the Block Page

You can customize the block page appearance in Settings → Block Page:

  • Upload your school logo
  • Edit the block message text
  • Enable/disable the Request Access button
  • Add custom instructions or contact information

Tips

  • Test block page appearance after any network or certificate changes
  • The block page works without full SSL inspection — it's served during the initial connection phase
  • If students report they "can't access anything," it may be a proxy connectivity issue rather than over-blocking — check the Network Health Score first

Related Articles