We jumped on a call and figured it out - we had to change his Region to English (United States), from English (Europe).   The login server was not liking the locale=en-150 that was being sent to it. We'll work on addressing that from our end for a permanent fix.