I'm also a Jerboa user, but other than not displaying the error for very long the result should be the same if you use the 'native' website. That would be my recommended next course of action to see if you can get the error to persist a bit longer so you can read it. Odds are it's something set up server side.