Common issues when deploying the KyberGate MDM profile.
Profile Installed But No Traffic Appearing
- Check the org ID — Make sure the PAC URL contains your actual org ID, not the placeholder "ORG_ID"
- Check proxy reachability — On the device, open Safari and go to https://proxy.kybergate.com/health — it should return "OK"
- Wait 60 seconds — The device needs to fetch the PAC file and route traffic. First requests may take a moment.
"Cannot Verify Server Identity" Errors
- The CA certificate isn't trusted. Check Settings > General > About > Certificate Trust Settings on iPad.
- Re-push the MDM profile — the trust settings may not have applied.
Profile Was Removed by Student
- Ensure the iPad is supervised. Only supervised devices prevent profile removal.
- Add a Restrictions payload that prevents configuration profile removal.
"Proxy Server Not Responding"
- Check if the proxy is running: curl https://proxy.kybergate.com/health
- KyberGate is designed to fail-open — if the proxy is unreachable, traffic goes direct. This is by design.
$UDID or $EMAIL Variables Not Replaced
- These are MDM variable substitution tokens. Jamf uses $UDID, Mosyle uses %DeviceUDID%. Check your MDM's documentation for the correct variables.
- If your MDM doesn't support variable substitution, the device will still register using its IP address.
Still Stuck?
Contact support@kybergate.com with your org ID, device model, and MDM platform.