# XMR errors despite everything setup correctly?

**URL:** <https://community.xibo.org.uk/t/xmr-errors-despite-everything-setup-correctly/14835>\
**Category:** Get Help\
**Created:** [June 26, 2018, 4:44am UTC](https://community.xibo.org.uk/t/xmr-errors-despite-everything-setup-correctly/14835 "2018-06-26T04:44:42Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![justink](https://community.xibo.org.uk/letter_avatar_proxy/v4/letter/j/e79b87/32.png) [@justink](https://community.xibo.org.uk/u/justink)\
**Post date:** [June 26, 2018, 4:44am UTC](https://community.xibo.org.uk/t/xmr-errors-despite-everything-setup-correctly/14835/1 "2018-06-26T04:44:42Z")

</div>

Hi, We have recently upgraded from 1.7.8 to 1.8.9 on a manual web server.

We run approximately 45 Android clients and updated all to the latest 1.8 R106 client.

Also recently purchased 2 Windows based players to test Windows player (1.8.8) on them.

From what I can tell XMR is setup correctly and all clients had XMR registered successfully via Edit Display → Advanced → Reconfigure XMR.

config.json:

> {  
> “listenOn”: “tcp://lo:50001”,  
> “pubOn”: [“tcp://10.251.33.207:9505”],  
> “debug”: false  
> }

Windows client can reach the XMR service on port 9505 successfully:

> PS C:\Users\infoscreen-svc\> TNC -ComputerName xibo -Port 9505
> 
> ComputerName : xibo  
> RemoteAddress : 10.251.33.207  
> RemotePort : 9505  
> InterfaceAlias : Ethernet  
> SourceAddress : 10.2.54.103  
> TcpTestSucceeded : True

Both the Android and Windows client come up with these same errors when trying a “Collect Now” command or other command.

> Unable to Process Queue of Player actions due to 1 of 1 player actions failed

> Player action connection failed. E = XMR connection failed. Error = Failed to connect the ZMQ: Protocol not supported

Troubleshooting files from the “Report Fault” page, as well as audit logs from the Windows client can be downloaded from the link below.

[https://filesender.oist.jp/filesender/download.php?vid=364ce4dc-b3e3-fd89-eb7a-00004980ed6f](https://filesender.oist.jp/filesender/download.php?vid=364ce4dc-b3e3-fd89-eb7a-00004980ed6f)

Any pointers are appreciated. Thank you

---

<div class="post-metadata">

**Author:** ![Peter](https://community.xibo.org.uk/user_avatar/community.xibo.org.uk/peter/32/8154_2.png) [@Peter](https://community.xibo.org.uk/u/Peter)\
**Post date:** [June 26, 2018, 10:05am UTC](https://community.xibo.org.uk/t/xmr-errors-despite-everything-setup-correctly/14835/2 "2018-06-26T10:05:58Z")

</div>

Assuming that the same private/public XMR addresses are configured in CMS Settings (which they seem to be, from your troubleshooting) and that XMR is running (you need to ruin it “manually” on non-docker installations) and that players can reach it, then we would expect that to work.

Your windows player did generate the private and public xmr address too.

Could you switch the XMR to debug (in config.json), restart it and see what’s logged when you run it please?

---

<div class="post-metadata">

**Author:** ![justink](https://community.xibo.org.uk/letter_avatar_proxy/v4/letter/j/e79b87/32.png) [@justink](https://community.xibo.org.uk/u/justink)\
**Post date:** [June 27, 2018, 12:08am UTC](https://community.xibo.org.uk/t/xmr-errors-despite-everything-setup-correctly/14835/3 "2018-06-27T00:08:06Z")

</div>

> [@Peter](#):
>
> Assuming that the same private/public XMR addresses are configured in CMS Settings (which they seem to be, from your troubleshooting) and that XMR is running (you need to ruin it “manually” on non-docker installations) and that players can reach it, then we would expect that to work.

Yes, XMR is running otherwise that port would not have been open. I also confirmed with “netstat -tun”:

> [root@xibo justin-kosinski]#netstat -tun  
> Active Internet connections (w/o servers)  
> Proto Recv-Q Send-Q Local Address Foreign Address State  
> tcp 0 0 10.251.33.207:9505 10.19.20.121:46462 ESTABLISHED  
> tcp 0 0 127.0.0.1:44504 127.0.0.1:50001 TIME\_WAIT  
> tcp 0 28 10.251.33.207:22 10.9.21.24:59854 ESTABLISHED  
> tcp 0 0 127.0.0.1:44480 127.0.0.1:50001 TIME\_WAIT  
> tcp 0 0 127.0.0.1:44526 127.0.0.1:50001 TIME\_WAIT  
> tcp 0 0 127.0.0.1:44532 127.0.0.1:50001 TIME\_WAIT  
> tcp 0 0 127.0.0.1:44540 127.0.0.1:50001 TIME\_WAIT  
> tcp 0 0 10.251.33.207:9505 10.15.24.104:37177 ESTABLISHED  
> tcp 0 0 10.251.33.207:9505 10.3.213.2:59719 ESTABLISHED  
> tcp 0 0 127.0.0.1:44522 127.0.0.1:50001 TIME\_WAIT  
> tcp 0 0 10.251.33.207:9505 10.19.20.117:46700 ESTABLISHED  
> tcp 0 0 10.251.33.207:9505 10.9.20.125:53364 ESTABLISHED  
> tcp 0 0 10.251.33.207:9505 10.15.24.111:34298 ESTABLISHED  
> tcp 0 0 10.251.33.207:9505 10.9.17.11:44825 ESTABLISHED  
> tcp 0 0 127.0.0.1:44524 127.0.0.1:50001 TIME\_WAIT  
> tcp 0 0 127.0.0.1:44550 127.0.0.1:50001 TIME\_WAIT  
> …

As per my last message I had

> “listenOn”: “tcp://lo:50001”,

in config.json as it would not even start with

> “listenOn”: “tcp://localhost:50001”,

In any case I thought I would try the “lo” version in the CMS but that just resulted in the error bellow when I tried a “Collect Now” command.

> Player action refused by XMR (connected but XMR returned false).

Now switching back to the “localhost” and I saw no errors when I initiate “Collect Now”.

Very odd…

---

<div class="post-metadata">

**Author:** ![Peter](https://community.xibo.org.uk/user_avatar/community.xibo.org.uk/peter/32/8154_2.png) [@Peter](https://community.xibo.org.uk/u/Peter)\
**Post date:** [June 27, 2018, 7:39am UTC](https://community.xibo.org.uk/t/xmr-errors-despite-everything-setup-correctly/14835/4 "2018-06-27T07:39:29Z")

</div>

> [@justink](#):
>
> Now switching back to the “localhost” and I saw no errors when I initiate “Collect Now”.

Does that work correctly now? ie no errors and XMR commands / actions are executed as expected?

---

<div class="post-metadata">

**Author:** ![justink](https://community.xibo.org.uk/letter_avatar_proxy/v4/letter/j/e79b87/32.png) [@justink](https://community.xibo.org.uk/u/justink)\
**Post date:** [June 28, 2018, 3:02am UTC](https://community.xibo.org.uk/t/xmr-errors-despite-everything-setup-correctly/14835/5 "2018-06-28T03:02:02Z")

</div>

Hi Peter,

Yes, XMR seems to be working correctly now.

Much thanks for your help with this.

---

<div class="post-metadata">

**Author:** ![system](https://community.xibo.org.uk/uploads/default/original/2X/a/a8759c2d8cc561474733895ac75beeb830f5d8ca.png) [@system](https://community.xibo.org.uk/u/system)\
**Post date:** [March 4, 2020, 5:11pm UTC](https://community.xibo.org.uk/t/xmr-errors-despite-everything-setup-correctly/14835/6 "2020-03-04T17:11:26Z")

</div>

Closed on March 4, 2020, 5:11pm UTC


