JSON Invalid after Cert update

Get Help CMS Features and Functionality
1

CMS Version

Version 2.3.8 - Windows Docker

Issue

I’ve been using DataSets to get a very basic JSON file from our Papercut server
All running fine displaying the amount of pages printed in the last 4 hours.

Until we replaced our expiring wildcard cert on our print server at the beginning of the year,
Its a godaddy wildcard and Xibo was showing " curl: (60) SSL certificate problem: unable to get local issuer certificate" error when using the “Test Data URL” button
I fixed that by adding the cacert.pem file to shared\cms\ca-certs
and running the following as it still gave the curl error from just adding the pem file to the folder

docker exec -it xibo_cms-web_1 bash
update-ca-certificates
exit
docker restart xibo_cms-web_1

I can now get my JSON through the Test Data URL
But when running the scheduled task I receive
"The error is: Unable to get Data for PagesPrinted because the response was not valid JSON. "

I’ve run the JSON through some validators and they have returned positive

Through firefox and edge chome the JSON looks like this
{
“recentPagesCount” : 2746,
“comment” : “The number of pages printed in the last 240 minutes.”
}

the Test DATA URL button returns this:

{
“entries”: [
{
“recentPagesCount”: 2749,
“comment”: “The number of pages printed in the last 240 minutes.”
}
],
“number”: 1,
“processed”: [
[
{
“recentPagesCount”: 2749,
“comment”: “The number of pages printed in the last 240 minutes.”
}
]
],
“messages”: [
“Processing 1 results into 5 potential columns”,
"Processing Result with Data Root ",
“DataRoot is an object”,
“Processing as a Single Row”,
“Consolidating entries”,
“There are 1 entries in total”
]
}

Other than the certificate the server software is unchanged, Xibo is also unchanged from when it was working Dec last year

Any ideas of what I have missed?

Cheers

2

I am sorry, I can’t help - but I am experiencing a very similar behavior. I don’t use any certificates. In the userscripts folder, I created a php file outputting a json file which I copied here from the forum (so it should be a working example). Via test data url, I get the following result:

{
“entries”: [
{
“wifi”: “GuestAP”,
“rows”: [
{
“tglAwal”: “7 Mei 2018”,
“tglAkhir”: “13 Mei 2018”,
“password”: “WifiPass100”
},
{
“tglAwal”: “15 Mei 2018”,
“tglAkhir”: “23 Mei 2018”,
“password”: “WifiPass122”
}
]
}
],
“number”: 1,
“processed”: [
[
{
“awal”: “7 Mei 2018”,
“Pass”: “WifiPass100”
},
{
“awal”: “15 Mei 2018”,
“Pass”: “WifiPass122”
}
]
],
“messages”: [
“Processing 1 results into 2 potential columns”,
“Processing Result with Data Root rows”,
“DataRoot is an array”,
“Processing 0”,
“Processing 1”,
“Consolidating entries”,
“There are 2 entries in total”
]
}

However, also after starting the “Fetch Remote DataSets”-Task, I don’t obtain results in the data columns. Additionally, I get an error that " Remote DataSet Test failed to synchronise", because of JSON being not valid.

So perhaps, if the error on your side persists, it has nothing to do with your certificate? Did you update your XIBO after creating the DataSet task? Even you don’t updated after you changed the certificate, perhaps there is an error in the creation of the tasks in newer versions? Can somebody confirm Remote Datasets are working in 2.3.8?
Thank you and best,
Christian

3

I’m seeing a similar thing with a number of datasets, all of which were working before the 2.3.8 update.

Now they are coming up as invalid JSON even though manually testing them is pulling down the correct results.

It’s clearly able to process them when I press the test button.

“processed”: [
[
{
“Current Temperature”: “15.6”,
“Feels Like”: “14”,
“Humidity”: “76”,
“Pressure”: “1016.8”
}
]
],
“messages”: [
“Processing 1 results into 4 potential columns”,
“Processing Result with Data Root observational”,
“DataRoot is an object”,
“Processing as a Single Row”,
“Consolidating entries”,
“There are 1 entries in total”
]

4

Cheers for the replies,
So its starting to look like the 2.3.8 update which I did 3 days before our Cert got renewed,
I can’t say that I looked at my Dataset during the 2 days in the middle

5

Can confirm Version 2.3.6 DataSet can get my JSON file without issue

I duplicated my docker on a 2nd computer and loaded my instance with the Version 2.3.6 compose files
It booted which was nice and I was able to retrieve my JSON without issue

6

This issue was already reported and logged here:

A fix will be in 2.3.9

1 Like
7

There’s never database changes within patch releases, so you can safely upgrade and downgrade again on a patch release.

eg 2.3.7 to 2.3.8, roll back to to 2.3.7 and then later to 2.3.9.

With Docker that’s really simple since you’re just replacing one file and upping the containers to roll forward and back.

8

Yep I rolled back to 2.3.6 (because that’s the download i had sitting around)
and everything seems to work just fine

Cheers

9

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.