Grok Academy Block Checker

If Grok is telling you that WebSockets are blocked, this usually happens because your school or device is blocking WebSockets. We've noticed, particularly on some Chromebooks, there is a device configuration setting that blocks WebSockets. The issue is within the proxy settings. Read more on how to fix this issue in our FAQs

This page will attempt to connect to each of our required services to make sure they haven't been blocked on your network. Please wait while the script executes, it could take some time.

The following domains patterns need to be accessible (unblocked) for all of Grok Academy to work as expected:

Note: This list includes both top-level (e.g. groklearning.com) and the wildcard (e.g. *.groklearning.com) versions of our domains.

Additionally, WebSockets need to be allowed on *.groklearning.com. Transparent proxies such as Netbox Blue and Palo Alto tend to block WebSockets by default.

If you fail the WebSocket test, you will need to ask your network administrator to whitelist *.groklearning.com to not be proxied since WebSocket connections by definition cannot be proxied. Note: The WebSocket protocols are ws:// and wss://.

If you fail any other test, you will need to ask your network administrator to unblock the domain being tested.

Below is a log of what happened during the Realtime WebSocket test. If you need technical assistance from Grok Support, please include a copy of the below log with your support enquiry so we can assist you as best as possible.

Below is a log of what happened during the Terminal WebSocket test. If you need technical assistance from Grok Support, please include a copy of the below log with your support enquiry so we can assist you as best as possible.

Below is a log of what happened during the Web Worker test. If you need technical assistance from Grok Support, please include a copy of the below log with your support enquiry so we can assist you as best as possible.