This happens way too often. On different screen every time.
?
What’s your private and public XMR addresses in Settings / display profile assigned to this device?
Also what Xibo for Android version is this? Should be preferably 1.8 R101 since you’re using 1.8 CMS.
The adress is correct, IT work for 3-4 days, then this happen.
Ver is .101
I may have found the cause of my problem.
All of my boxes are on timers, so they reboot once a day.
Every time I reboot, I get "can not get public key"
Something I can fix?
Some screens goes on/off with the lighting in the rooms, so they reboot, whether I want or not.
/Nicklas
You can try to navigate to the Displays page -> Edit display -> Advanced tab -> check ‘Reconfigure XMR’ and click Save.
It could be also good to restart Xibo player after making this change.
It shouldn’t be needed to do that after each reboot though.
i get the same issue…
even if i have done :
Displays page -> Edit display -> Advanced tab -> check 'Reconfigure XMR
223 2017-04-26 19:25 Can’t get Public Key.
220 2017-04-26 19:25 Key Pair generation failure.
217 2017-04-26 19:25 Key Pair generation failure.
215 2017-04-26 19:12 Can’t get Public Key.
212 2017-04-26 19:12 Key Pair generation failure.
209 2017-04-26 19:12 Key Pair generation failure.
206 2017-04-26 19:00 Key Pair generation failure.
203 2017-04-26 19:00 Can’t get Public Key.
200 2017-04-26 18:59 Key Pair generation failure.
197 2017-04-26 18:47 Key Pair generation failure.
194 2017-04-26 18:47 Can’t get Public Key.
191 2017-04-26 18:47 Key Pair generation failure.
190 2017-04-26 18:34 Can’t get Public Key.
187 2017-04-26 18:34 Key Pair generation failure.
184 2017-04-26 18:34 Key Pair generation failure.
182 2017-04-26 18:21 Can’t get Public Key.
179 2017-04-26 18:21 Key Pair generation failure.
176 2017-04-26 18:21 Key Pair generation failure.
173 2017-04-26 18:08 Can’t get Public Key.
170 2017-04-26 18:08 Key Pair generation failure.
167 2017-04-26 18:08 Key Pair generation failure.
164 2017-04-26 17:55 Key Pair generation failure.
161 2017-04-26 17:55 Can’t get Public Key.
158 2017-04-26 17:55 Key Pair generation failure.
156 2017-04-26 17:42 Can’t get Public Key.
153 2017-04-26 17:42 Key Pair generation failure.
150 2017-04-26 17:42 Key Pair generation failure.
149 2017-04-26 17:29 Key Pair generation failure.
147 2017-04-26 17:17 Can’t get Public Key.
144 2017-04-26 17:17 Key Pair generation failure.
141 2017-04-26 17:17 Key Pair generation failure.
This basically means that the player is unable to create or recall the RSA key it generated to communicate with XMR (push messaging from the CMS).
Rekey only clears the key from the CMS side, allowing the Player to send a new key. As this doesn’t work it is possible you have a corrupted key in stored in the player that isn’t being cleared.
Can you try deleting all data for the application (which will require you to reconfigure it when you start it back up), so see if that clears the error.
I will record a 
for the next release to try and detect a corrupt key and self-clear it.
As a side note this probably isn’t great for the device
Will try that.
The displays are in stores, so they turn on with the lighting in the morning, and turn off at night. The reason I chose to do that is that the minix boxes hang out sometimes, now they get an automatic reboot every night.
use Minix x7 mini with autostart then the power goes on.
Here we go again. Followed your step on one of my screens ysterday. Cleared all data and rekeyed.
Everything works well until…
Uploading…
The strange thing is that it did work for several hours, so the configuration must be correct.
I’m about to losing my mind
OK - its still a useful test - its a repeatable problem, not a one off corruption of some sort. That makes me think the key isn’t being stored correctly.
I’ll look into this asap - the error message itself is actually harmless if you don’t use push messaging for anything. You can lower your collection interval to compensate and ignore the message.
Once I have something to try, I will PM you and @urbanit a link to a new APK to try
Thank u.
I do the same thing on a 24/7 screen and se if its the reboot that make the problem.
1 Like
Try to reboot my device with the new APK.
Here´s the log:
ID Datum Meddelande
58420 2017-04-28 17:52 Can’t get Public Key - NPE
58419 2017-04-28 17:52 Key Pair generation failure. java.io.NotSerializableException
58418 2017-04-28 17:52 Key Pair generation failure. java.io.NotSerializableException
58417
I may be closer to understanding this - i’ve build another beta APK and made it available at the same URL as before. Would it be possible for you to try again please?
Same name on the file?
Run it now, let u now tomorrow =)
61507 2017-04-30 00:03
Key Pair generation failure. java.io.NotSerializableException
61647 2017-04-30 02:00
Unable to open message: javax.crypto.BadPaddingException/error:0407106B:rsa routines:RSA_padding_check_PKCS1_type_2:block type is not 02
Hmm - would it be possible to put auditing on in your display settings profile and also on the display itself? I am hoping to get another message logged telling me where it failed.
What version of android do you have running on your Minix?
Using the extra logging I have found some information on the issue which states it was a bug in Android 4.1.1 (for reference : https://issuetracker.google.com/issues/36955953)
For 1.8 we do require android 4.4 or higher