This article helps you resolve the "Unable to fetch server information" error in LockDown Browser, which occurs when access to Respondus servers is blocked. It guides you through updating to the latest LockDown Browser version, enabling TLS 1.2, verifying your computer’s date and time settings, and troubleshooting network or firewall blocks. Additionally, it provides specific instructions for lab managers using the Managed Computers edition to ensure proper server profile detection.
Summary: The "unable to fetch server information" error occurs when access to Respondus servers is blocked by the computer or network, preventing LockDown Browser from loading the institution's learning management system. This issue can result from outdated software, disabled TLS 1.2, incorrect date/time settings, firewall or antivirus blocks, router restrictions, or missing institution ID properties in the Managed Computers edition.
This error typically occurs when either your computer or network is blocking access to our servers. As a result, LockDown Browser cannot access and then load your institution's learning management system.
Currently, our servers are:
Primary = server-profiles-respondus-com.s3-external-1.amazonaws.com
Mirror = www.respondus.com
1) The first thing you should do is ensure you are running the most current version of LockDown Browser. You'll need to download the full LockDown Browser installer using your institution's unique LockDown Browser download link. If you're unsure what this link is, please either contact your institution's help desk, or open a ticket with Respondus Support.
Note: using the "check for update" feature of LockDown Browser is not recommended for this step. It's best to only use the full LockDown Browser installer to perform the update.
2) You should ensure that TLS 1.2 is enabled on your computer. If not, it can cause the error. You can check this by going to: Control Panel > Network and Internet > Internet Options > Advanced tab.
Scroll down until you see "use TLS 1.2" and make sure it is checked.
3) Make sure the date/time settings on your computer are accurate, reflecting the physical location of the computer.
Once you've performed the above steps, should the error persist, this means that a block to our servers exists. To troubleshoot this problem, the best place to start is to temporarily relax any firewalls and/or anti-virus software to see if that makes the difference.
If the problem persists, it's possible that the block might also be set in the router. You may also want to try using a different network to see if that resolves the issue.
For lab managers who are encountering this error with the "Managed Computers" edition of LockDown Browser, you should also ensure that when pushing out this edition, you added the RSP_ID and RSP_KEY properties to your msiexec command.
If this is not done, then the institution ID will not be properly entered into the Windows registry, resulting in your institution's server profile not being detected. This can produce the "unable to fetch" error.
Further details are included in the "readme" file that comes packaged with the managed computers download.
Original source: Unable to fetch server information from both primary and secondary mirror servers | Respondus-Source-ID: 4409595535131 | Source-Updated: 2026-07-06T19:53:47Z
Comments
0 comments
Please sign in to leave a comment.