Have you already tried what Peter proposed in another thread?
[…] the unknown block type, most likely means that the keys are out of sync.
If you would navigate to the Displays page → Edit display → Advanced tab → Reconfigure XMR & Save
On the next collection interval (or after you restart the player) it should regenerate the keys which should solve the XMR issue.
I already tried reconfiguring XMR. Date & Time is also correct (inside xibo. The docker container itself has UTC, but the xibo settings use the correct regional setting).
Another client starting to have a (different?) issue:
I updated a single detail inside a layout and now the client does not come over the splash screen, saying Layout 360, [5000] no regions or widgets, ttl86400.
Guess what? Layout 360 does not even exist. And if it would: the chosen layout HAS regions - and a clock. The internal ID it should pick up is a bit higher.
Any ideas on this new one? Maybe worth opening a new thread?
Okay, the no regions or widgets sorted itself out by removing the layout-id-file from the lib. But the main issue with the other player still persists.
The Openweather widget had some issue and did not load. The layout designer showed and widget error. This led to DurationController to complain somehow. Removing this widget made all working again.
If a layout has a data widget inside it which has no data available on the player (because it has not been downloaded - i.e. the file is not there at all) we use xiboIC and call expire to move on.
Object reference not set to an instance of an object
I am not sure why this message would be logged in there - do you have the latest version of the CMS?
Usually this is because XTR isn’t running, or the WidgetSyncTask is in an error state and not processing.
The player cannot open the RSA signed message because the public key used to seal it (which the player sends to the CMS) is wrong or does not match.
I reinstalled the player and it seems to work now. However I still have these log entries when I change the layout. (in this example I added the flip clock). The datasets immediately started to show “no data available”.
Not sure if our issue is relatable, but it seems like that. After adding one certain picture to the layout, player can’t download it and here’s a log we’re getting. What could be an issue?
The IDs of the widgets will change if you checkout a layout and then publish it, which means new data will be requested. If you do this on a layout currently in the schedule loop, there will be a short period of time between publishing and the Widget Sync Task running to generate new data.
When the data is generated a push message is used to inform the player that it should be downloaded (if XMR doesn’t work then this won’t work either).
That’s weird then - I don’t seem to get that message. I’ll add a note for us to look at it.
SOrry for the 3rd post but more info: The “issue” for the mentioned widgetId also stops the other dataset from working even if its not mentioned with its Id (1877)
Also good to know: we have 2 other displays, with complete different Layouts and widgets and even other datasets which work fine. I can observer this issue on one display only but dont see whats wrong.
The log messages only mention widget cache errors. Are there any other (debug) logs which could point to the right spot to look at @dan ?
