Hi,
Some time in January/February our Tizen player stopped responding to the CMS. In mid February it disappeared from the CMS. After checking locally on the player it seemed to be unable to talk to the CMS. When i was in the menu where you put all the codes in and tried to press Connect to CMS, it just said it couldn’t connect to the CMS. After uninstalling the app it it now won’t let me reinstall and i get “Unable to connect to the server”. I’m very certain it isn’t a network problem as I have added a windows player today with no problem. The Windows player and Tizen player are on the same network.
The CMS is running in docker on version 4.2.2. I’ve tried two different versions of the tizen player v3_R309 and v3_R311. I’ve also updated the host and pulled all docker containers.
Any ideas?
Okay so i figured out what the problem was. I didn’t know but we had started using internal CA. So the samsung TV would just refuse to connect over https. After opening up for http it worked fine. The reason it worked on a windows machine was that i had reused an old computer that already had a certificate.
We had a similar issue with ours. It suddenly stopped updating new content in November, and it took us and Support until February to nail down what the issue was.
TL’DR = It was the SSL cert
We were using an Entrust SSL cert that was still good until the end of April 2025.
We had previously sent Support a copy of our SSL cert, but nothing seemed visibly wrong. As a last-ditch effort we issued a new SSL cert from (a different provider) SSL.COM and put that on to our development server. In testing, that seemed to do the trick. Our Tizen device connected and started to pull data\files. We then went on to repeat the process to our production server, and it appears to be working there as well.
It doesn’t make sense, but it appears that the Tizen devices are more sensitive to the SSL certificates? As both the currently running Windows and Android devices never had a problem. Once the new SSL was implemented the issue was resolved.