has anyone been able to configure the websocket in 4.2?
I changed the config.json to reflect the needed ports (see below). The problem is xmr service will not bind to port 8080/8081 as intended. is there a different way for config.json to be setup?
has anyone been able to configure the websocket in 4.2?
I changed the config.json to reflect the needed ports (see below). The problem is xmr service will not bind to port 8080/8081 as intended. is there a different way for config.json to be setup?
here’s my config.json:
{
“listenOn”: “tcp://127.0.0.1:50001”,
“pubOn”: [“tcp://:9505"],
“debug”: true,
“sockets”: {
“ws”: “0.0.0.0:8080”,
“api”: “0.0.0.0:8081”,
“zmq”: ["tcp://:9505”]
}
}
Same issue here, i guess the docs are not correct
Your configuration looks wrong to me.
From the docs:
{
"sockets": {
"ws": "0.0.0.0:8080",
"api": "0.0.0.0:8081",
"zmq": ["tcp://*:9505"]
},
"debug": true
}
You seem to have other settings in there.
Indeed it’s different as placing the above mentioned code solely yields a parsing error for xmr.phar when trying to execute
Then it sounds like you still have the old XMR server there not the latest release.
i’ve confirmed I’m using latest CMS release 4.2.0. Noting that I have 2 xmr.phar within the archive as listed below. the xmr service is running from the first location (which has newer files) yet it looks for the config.json from the 2nd location.
Which file should we use and where should the service run from?
I also stopped the service and manually executed both .phar files using the new config.json file and yields the same error:
location-1: ./vendor/bin/xmr.phar → 3357 bytes → dated: 1/23/2025
location-2: ./vendor/xibosignage/xibo-xmr/bin/xmr.phar → 707129 bytes dated: 8/2/2023
Add me to the list, doesn’t work for me either.
I think an old XMR.phar is shipped by default, see:
xibo-cms-4.2.0\vendor\xibosignage\xibo-xmr\bin
The xmr.phar there is from 2023, since the one in xibo-cms-4.2.0\vendor\bin seems to be newer.
But just replacing the xmr.phar in xibo-cms-4.2.0\vendor\xibosignage\xibo-xmr\bin resulted in following php-error:
[04-Feb-2025 16:12:17 Europe/Zurich] PHP Warning: include(E:\CMS\vendor\xibosignage\xibo-xmr\bin/../xibosignage/xibo-xmr/bin/xmr.phar): Failed to open stream: No such file or directory in E:\CMS\vendor\xibosignage\xibo-xmr\bin\xmr.phar on line 119
[04-Feb-2025 16:12:17 Europe/Zurich] PHP Warning: include(): Failed opening 'E:\CMS\vendor\xibosignage\xibo-xmr\bin/../xibosignage/xibo-xmr/bin/xmr.phar' for inclusion (include_path='.;C:\php\pear') in E:\CMS\vendor\xibosignage\xibo-xmr\bin\xmr.phar on line 119
[04-Feb-2025 16:14:47 Europe/Zurich] PHP Warning: include(E:\CMS\vendor\xibosignage\xibo-xmr\bin/../xibosignage/xibo-xmr/bin/xmr.phar): Failed to open stream: No such file or directory in E:\CMS\vendor\xibosignage\xibo-xmr\bin\xmr.phar on line 119
[04-Feb-2025 16:14:47 Europe/Zurich] PHP Warning: include(): Failed opening 'E:\CMS\vendor\xibosignage\xibo-xmr\bin/../xibosignage/xibo-xmr/bin/xmr.phar' for inclusion (include_path='.;C:\php\pear') in E:\CMS\vendor\xibosignage\xibo-xmr\bin\xmr.phar on line 119
[04-Feb-2025 16:15:20 Europe/Zurich] PHP Warning: include(E:\CMS\vendor\xibosignage\xibo-xmr\bin/../xibosignage/xibo-xmr/bin/xmr.phar): Failed to open stream: No such file or directory in E:\CMS\vendor\xibosignage\xibo-xmr\bin\xmr.phar on line 119
[04-Feb-2025 16:15:20 Europe/Zurich] PHP Warning: include(): Failed opening 'E:\CMS\vendor\xibosignage\xibo-xmr\bin/../xibosignage/xibo-xmr/bin/xmr.phar' for inclusion (include_path='.;C:\php\pear') in E:\CMS\vendor\xibosignage\xibo-xmr\bin\xmr.phar on line 119
We publish a container with XMR in it and that’s how we’d generally expect it to be run.
I’ll ask the question internally about whether xmr.phar in the release should be there still or not.
There shouldn’t be an xmr.phar inside the CMS release anymore. It’s a mistake that it is there.
If you need to run XMR outside of the container, then it needs to be downloaded separately from the XMR releases page. Inside the release archive you’ll find a bin folder with the phar archive in it.
You need version 1.0 for CMS version 4.2.
We will update the docs in due course to make this clear. Thanks for pointing it out.
I replaced the xmr.phar with the one mentioned in new repository bin folder. this file now looks for config.json in same folder however passing the above mentioned config settings and then trying to execute xmr.phar still yields an error:
PHP Fatal error: Uncaught ErrorException: Undefined property: stdClass::$listenOn in phar:///var/www/xyz.com/public_html/vendor/bin/xmr.phar/index.php:66
Stack trace:
#0 phar:///var/www/xyz.com/public_html/vendor/bin/xmr.phar/index.php(66): exception_error_handler()
#1 /var/www/xyz.com/public_html/vendor/bin/xmr.phar(14): require(‘…’)
#2 {main}
thrown in phar:///var/www/xyz.com/public_html/vendor/bin/xmr.phar/index.php on line 66
That looks like it’s still the old version then inside the 1.0 release tarball. I’ve raised it internally and will let you know when that’s resolved.