View Full Version : How to access the Web interface in KooRaRoo

July 17th, 2013, 04:03 PM
To access the Web interface you need to know the IP address of your PC and the port used by KooRaRoo server.

To find the IP you need to run your command-line prompt by typing "cmd" into your Windows' search prompt. Then in the command-line prompt type "ipconfig" and hit Enter. You'll see the IP address there for one or more network cards.

To find the port used by the server go to Tools -> Options -> Server in the GUI and you'll see the port number there.

The last step is to go to the Devices pane, find the KooRaRoo server running on the IP of your PC, double-click on it and select one of the "KooRaRoo Web" device profiles for it, which should match the Internet browser you are using.

After that go to your browse and in the address bar type in the IP address (for example, followed by the port (for example 53180) and followed by "/html", like so:

You should now see your media library in HTML and be able to play videos, music and photos.

Robert Grant
July 18th, 2013, 05:30 AM
I just checked this out. All my files appear to populate on the web page with thumbnails and hyperlinks to each file. But selecting a hyperlink starts a download, not a play function. Is this the intended result?

July 18th, 2013, 08:26 AM
No, it should start playing. Can you please tell me which browser you are using and which device profile is selected for it in KRR?

Robert Grant
July 18th, 2013, 08:43 AM
Yes, the browser I'm using is Google Chrome and device profile KooRaRoo Google Chrome. Also tried Mozilla Firefox with KooRaRoo Firefox. In this case a dialogue opens asking to save or browse to something to open file with. Is this the intent here, to play files with a selected media player?

July 18th, 2013, 09:27 AM
Well, sort of. What happens here is files play within the browser window upon selecting them (or they should bring up your default media player if you have no built-in players in the browser, but that's not the ideal scenario). I think it'll be easier to handle through support, so that we don't go into deep diagnostics here, so can you please open a new support ticket and we'll do some investigating to get this going.