I see "Unexpected response from the server" when I try to login, download books, or sync my data.

Tech Support

Last Update 4 years ago

There are two situations where you can see this message. The first is very easy to solve, but the second is a mystery.


The first thing to try is to log into your Laridian account again. This will refresh the Customer ID and password that PocketBible uses to access your account and may resolve this problem. Go to Settings in PocketBible, then Program Settings, then Laridian Account. Log into your account again on that screen (re-enter your customer ID/email address and your password).


If you get an error message while trying to log in, the most likely reason is that you're entering the wrong password. If you can't remember your password, there's a password-reset or Forgot Password button on that screen you can use to request a password reset email from our server.


If this doesn't fix the problem, then we suspect it is a problem with your WiFi router, access point, proxy server, or antivirus solution that is introducing unexpected text into the response you receive from our server. In the past, when we have examined our server logs on this end to see what is happening, we notice that we are never getting the request from the user's device to access the account. So something is preventing the request from getting through to us. That  means that we can't do anything to fix it from our side.


It is usually the case that the problem resolves itself just as mysteriously as it began. There are a couple things you can try to speed it along:


  1. Try powering down your device and restarting it. Don't just exit and relaunch PocketBible – turn the power off to the device then turn it back on and try again. How you do that depends on the device. You will have to search for the applicable method on the Web if you don't know how to do it.
  2. Try logging in through a different WiFi network, or try logging in with the cellular network instead of WiFi.
  3. Try just waiting until tomorrow and trying again. Sometimes that works.

Was this article helpful?

1 out of 3 liked this article