trying to prevent this kind of debugging...
Would you have time to do the following Debugging steps?
Click the options menu (it is in the top right and looks like either "3 lines" or a "wrench".
You should see a panel appear at the bottom of the screen with options like "elements', "resources", "network", .. "console". Make sure "Console" is selected.
Right click in the console, and make sure "Preserve Log upon Navigation" is checked.
In the console, please type the following and press enter
it should say "undefined"in response
Keeping the console open, now, navigate to (or refresh) the login page for Raxa.
Try logging in with your username and password.
Does it still fail?
If so, please Copy-Paste (highlight all of the logs by clicking and dragging. Then press Ctrl+C to copy. Then open another file and press Ctrl+V to paste) all of the console logs. The attached screenshot shows the kind of logs I'm looking for. You can directly copy them into an email and send to john and myself.
P.S. If we cannot resolve this update remotely before Sathyan arrives, I can revert to the prior version tomorrow afternoon, before Friday's registration session.
P.P.S. In the future, we'll can try capture these logs automatically, so you needn't manually follow these debugging steps.
there are some scripts that allow us to connect in remotely - perhaps these aren't reliable enough and we can improve; so they dont have to reset the computer
we ideally need to be able to see the web browser just as JSS does, so can try logging in, etc, and see errors they're hitting. VNC