I’m pretty much a technical beginner here:
I’ve installed the most recent OSMC on a Raspberry Pi Model B with no problem and I now want to get a remote control onto everyone in the house’s phones (all Android)
I’ve downloaded both Yatse and Kore. Neither can find the device, and a bit of Googling tells me I need to turn on Settings > Services > Webserver “Allow control of XBMC via HTTP”
Unfortunately, on setting level expert, all that is showing in that menu is:
General
Control
UPnP/DLNA
Airplay
SMB Client
Weather
Can anyone tell me how to access “Allow control of XBMC via HTTP”?
Does OSMC have this option, or do I need to install a different application?
Thank you.
Oh yes, thanks. I did turn on the http option there as I was looking through all the menus, but it doesn’t seem to have worked. I’ve tried manually adding IP addresses and ports to the remote apps, but no luck. I’ll just have to keep trying stuff out I suppose.
Thanks.
Hi,
Whats happens if you go to http://pi.ip.address:8080 in your when browser?
Thanks Tom.
OK - I’m getting mixed results: The PC wired to the modem is showing Kodi, but the iMac doesn’t show it either wired or wireless. The phones are not showing it over wi-fi either (This site can’t be reached).
Another update - I decided to log in to the modem to open Port 8080. In the process I reset it, and it seems to have done the trick - my phone has now connected fine. Thanks for (in a roundabout way) getting me to the solution!
You should be very careful allowing kodi to be port forwarded to the outside web. It’s not designed for that and there are known vectors to be exploited in Kodi in such a web facing scenario.
Port forwarding should never be necessary in order to connect devices within your LAN.
1 Like
Thank you. I didn’t need to in the end, but thanks for the advice.
Thos, If you have other devices services that uses port 8080 there may be a conflict change your port number on OSMC to a random number and try and connect that way.
Other devices on 8080 should be no problem. Certainly none of them are on the same IP!
This would only be an issue of you had other services running on the same device that were also trying to use 8080.
1 Like
my mistake I said other devices, I meant services thanks for catching that.