Xibo

unable to register display

Asked by Kosturnix

Xibo is driving me really mad.

Have a display (fully licensed) and can contact to my CMS. Version 1.6. The CMS is installed at home, as POC. But it works (with some problems).

Installed the 1.7 RC server in the webspace from my ISP. Works fine, and I can do all I need to do.

Only one minor detail is NOT working: the display will NOT register itself to the new CMS.
Can it be because my display is version 1.6 and the CMS 1.7?
The license is brand new, pity if I have to pay again after a week because there arrives a new version....

Settings of the CMS are in my opinion OK. Tried several possibilities, in the browser they all work. Can use both http://kampongvoetbal.n/xibo/ as also http://xibo.kampongvoetbal.nl/ and it shows me the xml-stuff.

The ServerKey is correct (copy and paste the same in the CMS 1.6 as 1.7 version) so that can't be a problem. But the only thing I get is an html 500-error.

Even removed the license from the in the CMS 1.6 version before attempting to connect it to the CMS 1.7. No difference

Please help, in this way my Proof Of Concept is becoming a great disaster.

Frank

Question information

Language:
English Edit question
Status:
Answered
For:
Xibo Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Donny Yeo (donnyyeo) said : 		#1

Xibo for Android.
You should have POC with the 14 days trial license.

https://springsignage.com/xibo-for-android/

"No hidden costs, download the APK, try it and if you like it pay £15 GBP per display. Use your licence forever.

Optionally purchase upgrades as they become available. Licences are validated automatically every 30 days."

Revision history for this message
Alex Harrington (alexharrington) said : 		#2

1.7 CMS requires a 1.7 client of the same version. Old 1.6 clients already
using the CMS will continue to get limited updates but you can't register
new 1.6 clients with a 1.7 CMS

Revision history for this message
Kosturnix (frank-schots) said : 		#3

The POC with 1.6 is not working as expected; since it took me some time I did pay for the 1.6 client. Just last week.

Having done that it looks like I really have to move on to the 1.7 CMS. And also a 1.7 client. D

That's a pity: have fully licensed an 1.6 client for a POC that failed.

Revision history for this message
Alex Harrington (alexharrington) said : 		#4

If you're talking about the Spring Signage Android client that doesn't form
part of the Open Source project.

You can contact their support team directly for support on the Android
Client - and assuming you purchased the client licence reasonably recently
should be entitled to a free upgrade to 1.7 once it's released.

Can you help with this problem?

Provide an answer of your own, or ask Kosturnix for more information if necessary.

To post a message you must log in.