LockDown Browser Error -7 on Mac (Network Error Fix 2026)
What error -7 means
Error -7 indicates LDB's pre-exam handshake with Respondus's configuration server (typically *.respondus.com on port 443) failed within the connection-timeout window. The error is unrelated to your LMS server (Canvas, Blackboard, etc.); it is purely Respondus's own infrastructure not being reachable from your Mac at the moment of launch.
Mac-specific causes
- Active VPN blocking Respondus endpoints (most common - corporate VPNs especially).
- Little Snitch / outbound firewall denying connections to
*.respondus.com. - Cellular hotspot with carrier filtering on TLS endpoints.
- Tor or a consumer VPN with an IP range Respondus has flagged for fraud detection.
- University network with a captive portal that has not been authenticated yet.
- macOS firewall blocking outbound connections (rare but possible if a profile is deployed by MDM).
Fix 1 - Disconnect from any active VPN
Open your VPN client (Cisco AnyConnect, NordVPN, ExpressVPN, GlobalProtect, etc.) and disconnect. Wait 10 seconds. Relaunch LDB from your LMS.
If you must be on the VPN to reach your LMS (some universities require it), contact your university IT and request that Respondus's egress IPs be added to the VPN's split-tunnel allow-list.
Fix 2 - Verify network reachability to Respondus
curl -I https://www.respondus.com
ping -c 4 www.respondus.comIf either fails or returns >500ms latency, your network is the problem. Try a different network (cellular hotspot to your phone, university wired Ethernet, friend's Wi-Fi) and retry the launch.
Fix 3 - Whitelist Respondus in Little Snitch / outbound firewall
If you have Little Snitch, Lulu, Radio Silence, or another outbound firewall, add an allow rule for *.respondus.com on TCP/443. Without it, LDB's silent connection attempts fail before any visible prompt.
See the conflicts cluster for the full firewall whitelist procedure.
Fix 4 - Test on a different network
If your home Wi-Fi consistently fails -7 but a friend's Wi-Fi works, your ISP or your router is the problem. Use cellular hotspot from your phone for the exam window and contact your ISP afterwards. Many ISPs (Comcast, AT&T residential) have intermittent TLS-MITM deployments that interfere with notarised macOS apps.
If none of these work
The remaining cases trace to your specific course's Respondus Dashboard configuration - your university IT or instructor needs to look at the server side. Contact them with: the exact error code, the LDB version (right-click LDB.app → Get Info), the macOS version (About This Mac), and the time of your launch attempt.
Frequently asked questions
Does error -7 mean I cheated?
No. -7 is a network connectivity failure between your Mac and Respondus's servers. It is logged for your instructor but is universally treated as a technical issue, not an integrity event.
Why does error -7 only sometimes appear?
Network conditions are variable - TLS handshake failures depend on momentary route conditions, ISP rate-limiting, and load on Respondus's servers. The same Mac on the same network can succeed at 9am and fail at 9:05am. If the error is intermittent, retry; if persistent across 30 minutes and multiple launches, network-level intervention is needed.
Can I take the exam offline if -7 keeps appearing?
No. LDB requires a live connection to Respondus's servers throughout the exam - answers are submitted to your LMS in real time. Offline exam-taking is not supported.
My university VPN is required to access the LMS but causes -7. What now?
Contact your university IT before exam day. Most have either a split-tunnel configuration that allows Respondus traffic, or a documented procedure for taking proctored exams without the VPN. The Respondus Dashboard administrator at your institution can also add VPN egress IPs to Respondus's allow-list.