Configure client xibo samsung QM65R QMR service

Hello,
I would like to test a client on Samsung QMR series QM65R I followed the procedure https://xibo.org.uk/docs/setup/tizen-installation-guide : Download and Install the Xibo for Tizen WGT
I also configure the date and time in the TV.
the problem for this connect to the CMS that does not work from the TV in the URL Louncher. I put my server address well https://cms.xxx.org
but nothing happens afterwards. Unable to connect error message …

Do you have any idea what and what is causing this problem?
Is there a configuration to do in CMS

Hello, I created a CMS trial on the cloud. everything works well with my Tizen.
My question what additional port should I open to be able to communicate my server with Tizen? Communication with Windows clients works well on my network. ports 80 and 443 are open. and the server is not accessible outside my network.

Thank you!!

There arent any additional ports needed - just the usual ones which you have already mentioned.

Is your local CMS up to date? Perhaps it is a CMS version issue

Hello, the CMS is at version 2.2.0.
what i did after i got the menu where i got the CMS information and the key. I put the information of my Onpremise server and not the one you trial cloud. so I managed to configure the screen and approve it on the CMS.
Is it possible that version 2.2.0 can cause connection blocking with the TV (connexion step)? on both CMS I add the trial version of Tizen or the fact that my CMS communicates only from inside my network to block the process of sending files to the screen.
I also noticed that the download speed of a video that was sent to the screen was very low (2 hours). however the same video was downloaded by a Windows client in 3 min. Also the video does not loop. once it makes the first turns it stops. on Windows Client it loops in content as expected. when I display a compain there is a time of 0.5 seconds between each layout that appears during which it is the default layout is displayed. it seems to me that the speed of the TV processor is not very efficient with the xibo client. Has anyone else had similar cases?
Thank you!!

We’ve tested the installation step quite extensively - the Player connects to the URL you put and downloads a config file, which it then uses to download the installation package and installs.

If you can install manually, and then use the connect to CMS screen and get a connection it seems that there isn’t any network issue.

Do you have Apache or nginx “send file” module configured - it might simply be that files are taking too long to download to the Player and therefore the install failed and you get a slow video.

With send file mode off, the Tizen player will be slower than Windows to download files - but we really recommend that you configure send file anyway, as your windows players will be using a lot of CPU cycles to download files.

Suggest that you solve the file download issue first - it might be spending a lot of CPU time downloading files.

We’ve not had any major issues with the processor power - although it is true that the processor is smaller than the typical windows PC, it is more than enough for the job, or so we’ve found.

Hello,
I use apache as a web server. in httpd:" EnablesendFile On" is there another module that I can configure for better performance?
CMS is up to date 2.2.2
PHP 7.3.11

thanks!

Have you configured the CMS settings to use it also? Send File Mode should be set to Apache.

When enabled players will download files via HTTP rather than via SOAP chunked downloads.

Hi!

image

i use PHP to send file in my httpd.conf : EnableSendFile OFF.

CMS is updated last week to version 2.2.2… i try with PHP to send file to Tizen with ENablesendFile is Off on the Httpd and i try to use Apache with Enablesendfile On.

With windows Player it’s fine with Apache or PHP. with the Tizen is fine but not quikly.

but if i Reset My TV and i unistall Xibo Apps and i try to configure it’s not possible de send file configuration from CMS. i use my trial xibo CMS with Nginx and every think Work Well. i don’t now wich problem with PHP and Apache.

Apache 2.4
PHP 7.3.11
cMS 2.2.2

thanks

You can see what we do in our Apache conf here: https://github.com/xibosignage/xibo-cms/blob/develop/docker/etc/apache2/conf.d/cms.conf

You would need to configure it with your library location too, so that it can access those files.

It is a good thing to get enabled as it will reduce load on the server and deliver files more quickly!

Hi, i have the same configuration in My Httpd.
i try to test with a DSCS9 i have this error :slight_smile:Method XmdsBase. Message: E class javax.net.ssl.SSLHandshakeExecption/java.security.cert.CertPathValidatorExecption : Trust anchor for certification path not found

if you have any idea. i have some DSC9 to configure
thanks

I think we might be jumping around topics a bit here :slight_smile:

That error means you have a problem with your SSL certificate and isn’t anything to do with send_file. If you’re using a self signed certification you can open the CMS in your Android browser first and trust that cert.

Hi Dan, i am able to connect to the CMS froms the android browser but when i try to connect CMS in Xibo apps i have error message :

.

Can you test the HTTPS version of your CMS URL at: https://whatsmychaincert.com/ and that should tell you what the problem is.

Basically the error message is saying that the HTTP Client can’t validate the SSL certificate - this can happen if its self-signed for example, or if you’re using a certificate that isn’t in the cert store on the device.

SSL isn’t really my area of expertise i’m afraid, so if the above doesn’t point you in the right direction you may need to contact the Help Desk (support is available for both Android and Tizen on there).

Hello, thanks for your Help.
finally there is missing an intermediate license file on the server which is not necessary to connect it via the Web Browser. android need to download this file to truster CMS. then reconfuguring the SSL again to make it work.
thanks

Fantastic - i’m pleased you figured it out!

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