If that matches what you’ve configured for XMR - then yes
If yes, and it still doesn’t work - lets see the output of XMR in debug mode. Adjust the debug property in config.json and restart XMR. You should get some extra output
After updating the Private and public address… It didn’t work. when I try to request a screenshot, it will just load and not closing the dialog box… Also I already added a debug property on my config.json, but I didn’t get any errors on the log…
By the way, can I pm you the access to our CMS so that you can have a look and feel free to test it…
The only thing I can think of at this point is to run XMR from source code, and enable more logging in it to find out what is causing the segmentation fault.
The source code is here: https://github.com/xibosignage/xibo-xmr, you can get a zip or git clone of that and drop it in a folder (i.d suggest /home/nvdigi5/xibo-xmr). Copy your existing config file into the new folder and you can try to run xmr by:
cd /home/nvdigi5/xibo-xmr
php index.php
We can then add some more logging to index.php below line 15.
I have follow your instruction and run it on my server… Also I have also updated my document root to point now in web instead of public_html…
By the way, when I try to run xmr on my server… It will now have information that it is starting and listening to my cms… also, when I try to request screenshot, it has xmr info with and json object on it. Please the screenshot…
However, I can’t see any screenshot being uploaded on the display on my cms… also, I try commands like restarting the player with this command taskkill /f /im XiboClient.exe and rebooting the pc using this command shutdown /r /t 0 , it will just add to the xmr info that there are a request, but it doesn’t do anything… Also turn off the firewall already on my player computer to make sure there wasn’t no blocking on accessing my cms… but it doesn’t work either…
I know, I am getting close on this… I can feel it… Thank you in advance for your response for this issue.
Sorry for the delay, it has been a busy few days with 1.8.2. It is interested that you have a working XMR from the repository - I can’t immediately explain that.
Now that XMR is working (logging requests from the CMS) and also sending heartbeats, you can use the player information screen to show whether or not it has been able to connect to your XMR service on the IP shown for publish.
You can also use the column selector on the CMS Display page to see if “XMR Registered” has been ticked, which will happen when the player registers its XMR channel (identifier).