Login at Kodi Home

dml3334 · 2015-07-27, 15:19

Hi.

I've just installed Kodi 15.0 on a Pipo Tablet:

IP Address (via DHCP): 192.168.0.155
Netmask: 255.255.255.0

I am trying to use Yatse as remote control from my Android mobile, with IP 192.168.0.154.

I have just followed this wiki:

http://yatse.tv/redmine/projects/yatse/wiki/XbmcConfig

webserver Port: 8080
webserver user: kodi
webserver password: kodi
Allow programs on this system to control XBMC
Allow programs on other systems to control XBMC
Share video and music libraries through UPnP
Allow control of Kodi via uPnP
Announce these services to other systems via Zeronconf

When I type

http://192.168.0.155:8080

in Chrome, in the tablet itself, user and password are requested, I enter them and I can see the web interface.

However, I cannot enter from the mobile. It says: ERR_CONNECTION_TIMED_OUT. If I use Yatse, the JSON-RPC test fails, as well.

I don't have any firewall in the tablet.

What could be happening?

Thanks.

dml3334 · 2015-07-27, 21:07

The exact error is

ERR_ADDRESS_UNREACHABLE

I have even opened the 8080 port in the WiFi router and changed it to 8082.

Any idea?

Thanks

dml3334 · 2015-07-27, 22:41

Hi.

I restarted the tablet and took a couple of debug logs.

Normal log

Debug Log

It says:

Code:
22:31:23 T:1734110032 NOTICE: Webserver: Starting... 22:31:23 T:1734110032 DEBUG: CWebServer [MHD]: Failed to bind to port 8082: Address already in use 22:31:23 T:1734110032 NOTICE: WebServer: Started the webserver

But I do not have anything else running on the 8082 port...
Now, a log where Kodi crashed while trying to enter into Kodi Log Uploader to upload the previous log:

Crash Log

It also says that the addresss was already in use.

Code:
22:30:23 T:1750945376 NOTICE: Webserver: Starting... 22:30:23 T:1750945376 DEBUG: CWebServer [MHD]: Failed to bind to port 8082: Address already in use 22:30:23 T:1750945376 NOTICE: WebServer: Started the webserver

I hope somebody knows what happens.

Thanks!

~~Ned Scott~~ · 2015-07-28, 07:10

It could be some other service running on the box. Try changing the port to something else just to rule it out.