Beem fails to authenticate using Android 5.0 Lollipop devices
Tested on Nexus 4 and Nexus 10 devices.
Error says "Warning: Your settings are set to use a server proxy or a specific server hostname. Unable to authenticate your account. Please verify your credentials"
Is there any further development going on with BEEM as I see it's been more than a year since a new client has been released.
#1 Updated by Frédéric Barthéléry almost 5 years ago
- Subject changed from BeemFails to authenticate using Android 5.0 Lollipop devices to Beem fails to authenticate using Android 5.0 Lollipop devices
- Priority changed from High to Normal
This seems to be a configuration issue. Check that your settings are correct specifically for the proxy and specific server configuration.
I have no problem to connect on Lollipop devices.
Regarding the development of Beem, unfortunattely we have less and less time to work on it so the development is stalled for now.
#4 Updated by Neil Carter almost 4 years ago
This is behaving in the exact same manner on my Motorola Droid Turbo. Since upgrading the OS to Lollipop 5.1, Beem will not authenticate (worked fine with KitKat). It provides the exact same error message with every attempt: "Warning: Your settings are set to use a server proxy or a specific server hostname. Unable to authenticate your account. Please verify your credentials"
There are no proxy servers involved. I've checked the specific server configuration loads of times, everything is very straightfoward, simple, and correct. And my credentials are being entered correctly. Is there a network sniffer for Android that would allow us to monitor the connection to observe the error?
It appears there's an encryption and/or certificate incompatibility involved between the Lollipop OS, Beem, and the Beehive server. It would appear the Lollipop OS has eliminated the ability to use either a certain type of encryption or class of certificate, no longer acceptable from a security standpoint.
Also, if I enable "Enable XMPP debug", where does the debug output go?
Please update and advise.
#7 Updated by Frédéric Barthéléry almost 4 years ago
You can use a software like wireshark to sniff the communication between your device and the server. But as the communication is probably encrypted you will have to provide the encryption keys of the server. That's why I recommand running adb logcat to get the log on the device instead.