LockDown Browser Error -118 on Mac (Configuration / Network Fix)

Error -118 is the highest code in Respondus's general configuration error band. Most -118 reports trace to a stale LDB cache combined with a transient network issue. Cache-clear + retry fixes ~75% of cases on the LDBypass test fleet.

What error -118 means

Error -118 fires at the boundary of the configuration error range - often when LDB and the Dashboard agree on the configuration but a transient network failure during the handshake left the state half-applied. The next launch surfaces -118 because the half-applied state is invalid.

Mac-specific causes

Fix 1 - Cache-clear + retry

rm -rf ~/Library/Application\ Support/LockDown\ Browser/
rm -rf ~/Library/Caches/com.respondus.lockdownbrowser/

Relaunch from LMS. -118 typically resolves on the next launch.

Fix 2 - Verify network is stable

Test reachability with curl -I https://www.respondus.com. If latency is >500ms or the request times out, switch networks before retrying.

Fix 3 - Reinstall if cache-clear does not help

Run the complete uninstall + fresh install from your LMS link. See uninstall cluster.

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

Is -118 the most severe of the configuration errors?

No - Respondus does not rank these by severity. -118 is just the last code in the band. Diagnostically, -118 is similar to -21 (cache stale).

Should I clear cache before every exam to prevent -118?

Unnecessary. Cache-clear is a fix when -118 appears, not a preventive measure. Routine cache-clear forces re-downloading the Dashboard config and slows your exam launch by 5-10 seconds.