Home Admin & Settings Network and Proxy Settings

Network and Proxy Settings

Last updated on Apr 17, 2026

Network and Proxy Settings

KyberGate uses a cloud-based proxy architecture to filter web traffic. Understanding the network configuration helps ensure reliable filtering across all devices in your school.

Before You Begin

  • You need Admin role or higher
  • Access to your school's network equipment (firewall, router) or your IT team
  • Know your MDM platform for deploying proxy settings to devices

How KyberGate Proxy Works

KyberGate routes web traffic through its cloud proxy network using a PAC (Proxy Auto-Configuration) file. This approach:

  • Enables SSL/HTTPS inspection for full content filtering
  • Works across all platforms (iPad, Chromebook, Windows, macOS)
  • Uses smart geo-routing across 8 regional proxy servers for optimal speed
  • Requires no on-premise hardware

Proxy Regions

KyberGate automatically routes traffic to the nearest proxy:

  • East Coast (NYC) — Primary
  • Southeast (Atlanta)
  • Midwest (Chicago)
  • Central (Dallas)
  • Northwest (San Francisco)
  • West Coast (Los Angeles)
  • Canada (Toronto)
  • Europe (London)

Deploying Proxy Settings via MDM

For iPads (Jamf, Mosyle, Kandji)

  1. In your MDM, create a Global HTTP Proxy configuration profile
  2. Set the proxy type to Auto (PAC)
  3. Enter your organization's PAC file URL (found in Settings → Network in your dashboard)
  4. Deploy the profile to your device groups

For Chromebooks (Google Admin)

  1. In Google Admin Console, go to Devices → Chrome → Settings
  2. Under Network → Proxy, select Use proxy auto-config
  3. Paste your PAC file URL
  4. Apply to the appropriate OUs

For Windows/macOS

  1. The KyberGate agent automatically configures proxy settings during installation
  2. No manual proxy configuration needed
  3. Verify in Settings → Network that the agent is reporting proxy status as active

Firewall Recommendations

Ensure these are allowed through your school firewall:

  • Outbound ports: 443 (HTTPS), 80 (HTTP), 8080 (proxy)
  • Domains: *.kybergate.com, proxy.kybergate.com
  • Optionally block direct internet access (bypass proxy) by restricting outbound 443/80 to only KyberGate proxy IPs

Tips

  • Use the Network Health Score on your dashboard to monitor proxy connectivity across devices
  • The PAC file URL is unique per organization — do not share it publicly
  • If your school uses a firewall with SSL inspection, add KyberGate proxy domains to the bypass list to avoid certificate conflicts

Troubleshooting

  • Devices not routing through proxy: Verify the PAC file URL is correctly deployed via MDM. Check Devices → [device name] → Network for proxy status
  • Slow browsing: Check the Network Health Score. If a specific region shows high latency, contact support
  • Certificate errors: Ensure the KyberGate root certificate is installed on all devices (see Certificate Installation guide)

Related Articles