· Other
roon display.
For a short time roon display web works only on the roon server machine (win 10), or other PCs but only when roon is also enabled on those PCs.
On a raspberry I have linux with roon display kiosk and roon bridge and I can't display. this happened a few days ago.
I will add that sound goes through the bridge.
Does anyone know the cause / solution?
Router dlink, switch zyx, connecting LAN
What is your display solution? Roon do not supply a display component for linux (on ARM or x64) although you can obviously use a web browser linked to http://<RoonServerIpAddress>:9330/display/
As a consequence, this question would be better asked (with more details of your Raspberry Pi configuration) in one of Raspberry Pi , RoPieee or DietPi
I have a raspberry on it roon bridge and a browser with the roon display address entered.
Until last week everything worked fine, now it doesn’t display.
The roon display address also displays strangely instead of 192.168…, it is 127.0.0…
It looks to me like a bug in roon…
The Roon display url is of the form http://<RoonServerIpAddress>:9330/display/
On the Roon Server itself, you can use an ip address of 127.0.0.1 because that is a special ip address that means ‘this machine’. On all other devices running a web browser for the display, you must to use the Roon Server’s local network ip address - which will be the one shown as 192.168.???.???.
The browser on your Raspberry Pi is looking at the wrong ip address and needs to be set to use the 192.168.???.??? address of your Roon Server.
This is not a problem created by Roon or a Roon Bridge update. The web server configuration is not part of the Roon Bridge installation and is thus not something that Roon Support are likely to comment on in detail. You need to re-visit the procedure that was used to setup the display. You still have not given details of the operating system and browser used so I can’t give more detail.
Incidentally, there is no security risk associated with publishing these addresses in full because they relate to your local network which is not directly accessible from the outside world - addresses in the range 192.168.0.0 to 192.168.255.255 are one of the special non-routable ip address groups which is what allows them to be used on millions of home networks (even though there are only 65536 (65534 usable) addresses in this range.
OK, so from the beginning because I don’t really know much about it.
I currently have a roon server on Nuc.
A raspberry with raspbian has roon bridge installed and a www browser in full screen option. In this browser remotely using putty, I usually entered the address that the roon server gave for roon display.
They were usually addresses from a group similar to my IPs within the network, for example: 192.168.8.180:9330/display/
Currently, the IP that roon gives looks different than usual 127.0.0.1:9330/display/.
A raspberry and server are connected by one Zyx switch to a dlink router.
If I can suggest anything else, please ask because I may have missed something.
thank you
I presume this NUC is running Windows (not RoonOS [as installed by ROCK] or any other linux variant) since your comments below suggest that you are running a Roon Client on the same computer (and there is no Roon client for Linux).
Edit: Changed server ip address to match that shared in the images in the OP’s post below.
If you mean that the Roon → Settings → Displays page is suggesting the http://127.0.0.1:9330/display/ url instead of http://192.168.8.130:9330/display/ then that may be an issue. I assume that this is because you are running the Roon client on the same computer as the Roon Server. Hence my assumption that you are running Windows on your NUC above.
Ideally, it would not use the 127.0.0.1 (‘localhost’) ip address in the displayed URL because that URL is only valid for browsers on the Roon Server machine itself. Unfortunately, I can’t reproduce this at present because my Roon server is hosted on linux (for which no client is available) and is currently being used by other members of the household so I can’t de-authorise it in order to setup a temporary Windows hosted Roon server.
If you use a Roon client on any other computer (or phone/tablet), it will give the url for the host display as http://192.168.8.130:9330/display/ (assuming the ip address of your Roon server has not changed).
If, on any Roon client, you go to Roon → Settings → Roon ARC, you will see the ip address of your Roon server. If you use this instead of the 127.0.0.1 ipaddress in the web browser, it should show the Roon display.
Hey @Pawel_Majcherek,
Thank you for writing in! And a huge thank you to @Wade_Oram for the clear breakdown of information so far.
Wade is correct in the statement below:
Could you share a screenshot of this page?
Thank you gentlemen for your advice.
Yes, I have Windows and Roon on it.
I am sending photos of how it looks in practice
It is true that when I enter the address 192.168.8.130:9330/display/ on another PC, the display works.
The question is what happened in the raspberry that even when I give it this address 192.168.8.130 it does not display?
The issue of the wrong ip address being used in the presented display url when the client is run on the same machine as the server (at least for Windows) is an issue that Roon can and, probably, should address.
The Raspberry Pi issue is not something that Roon support staff are bound to address.
For my part, I use DietPi rather than RaspberryOS (which is what it looks like you are using) so I’m not sure what the issue with the Chromium config is. You should ask the question regarding the Raspberry Pi on the Raspberry Pi sub forum where you are more likely to find people using the same operating system. Make sure you post the operating system details including the version number.
Wade_Oram, thank you very much.
I posted in the raspberry zone.
I wanted to ask about two more things, maybe you can tell me.
Is it worth changing windows to roon rock (until recently my dac on xmos only played DSD files natively for windows with asio, now I changed the dac so there shouldn’t be this problem)
In your opinion, should I change to dietpi (the things I care about are roon bridge, NAA for hqplayer, and a www browser for the screen, does dietpi have that)?
thank you
ROCK on the NUC could replace Windows to provide a Roon Server but then you would not have a display and you would not have the ability to run any other applications. ROCK installs can be used as a Roon Server (or possibly a Roon Bridge) but nothing else. No Roon Client, No Web Browser - nothing. RoonOS, as installed by ROCK, is designed to run headless (no keyboard and no display).
On the Raspberry Pi you could run everything you want under DietPi but there is no real advantage over RaspberryPi OS. They are both based on Debian.
Anyway, this conversation in the support forum is not the correct place for any converation - and you are just making the thread contents more confusing for any Roon support staff that want to pick up the incorrect display URL issue. Please do not ask any more questions unrelated to that issue in this thread.
Just for information:
I have now been able to re-produce this issue with build 1470 of Roon Server and the Roon Client on Windows 11 23H2 build 22631.4460 (all updates and patches availble have been applied):
Running a Roon Client on the same computer as the one running the Roon Server and then going to Roon → Settings → Displays shows a display URL that employs the localhost ip address (127.0.0.1) instead of the ip address of the Roon Server on the local network:
Thank you both @Pawel_Majcherek and @Wade_Oram for the reproduction of the incorrect IP within Display settings when using both Roon and Roon Server on a windows machine. We’ve submitted a ticket to development for further investigation!
We’ll share any updates on progress here! Thanks again 
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
