Skip to main content

SDLA Quick Fix · Nearpod

A Nearpod Interactive Activity Will Not Load

Isolate the affected activity, refresh one test device, and use Nearpod's connection test before asking IT to review WebSockets or filtering.

Teacher

Students can enter the Nearpod lesson, but Whiteboard, Time to Climb, Interactive Video, VR, or another activity stays blank or never starts.

Quick Fix

First, keep the lesson moving. Tell students whether to wait, skip the activity, or use your backup response method while you test one device. Avoid having the entire class repeatedly reload at once.

Follow these steps in order.

  1. Identify the exact failure

    Note the lesson title, activity type, slide number, and whether the problem affects the teacher, one student, or the whole class. If only imported media fails, record the media provider too.

  2. Refresh one test device

    On one affected device, refresh the page or leave and rejoin the same active session. Close duplicate lesson tabs and pause browser extensions only if your district allows that troubleshooting step.

  3. Run Nearpod's connection test

    On the affected school network, open the Nearpod WebSocket test (opens in a new tab). Record the result rather than changing network or security settings yourself.

  4. Compare a second approved network

    If local policy permits, test the same activity on a staff device using a different approved connection. If it works there but not on school Wi-Fi, the evidence points to local filtering, proxy, or network configuration.

  5. Check service status and escalate

    Review the Nearpod status page (opens in a new tab). If Nearpod is operational and multiple devices fail, ask IT to review WebSocket access, Nearpod's current required domains, and any third-party media domain used by the activity.

Copy-and-paste message for local IT

A Nearpod [activity type] in [lesson title/slide] will not load on [number] devices using [school/network]. The lesson itself loads, but the activity shows [exact behavior]. Nearpod's WebSocket test returned [result] at [time], and the status page showed [status]. The same activity [did/did not] work on [approved comparison connection]. Please review WebSocket access, Nearpod's current network requirements, and filtering for the activity's media provider.

Stop and escalate when

The connection test fails, the same activity fails across multiple devices, or success changes by network. Firewall, content-filter, proxy, certificate, and WebSocket changes belong to authorized IT staff.

Nearpod resources