That is strange, what happens if you just call sudo netstat -tulnp?
When I run:
sudo netstat -tulnp
I get this:
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Jul 27 21:57:30 2017 from lucabuntu.station
osmc@osmc:~$ sudo netstat -tulnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:9091 0.0.0.0:* LISTEN 1484/transmission-d
tcp 0 0 0.0.0.0:8200 0.0.0.0:* LISTEN 1499/minidlnad
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 1754/smbd
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1416/rpcbind
tcp 0 0 0.0.0.0:8081 0.0.0.0:* LISTEN 1818/python
tcp 0 0 0.0.0.0:8085 0.0.0.0:* LISTEN 1584/python
tcp 0 0 0.0.0.0:51413 0.0.0.0:* LISTEN 1484/transmission-d
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1370/sshd
tcp 0 0 0.0.0.0:5050 0.0.0.0:* LISTEN 1544/python
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 1754/smbd
tcp6 0 0 :::139 :::* LISTEN 1754/smbd
tcp6 0 0 :::111 :::* LISTEN 1416/rpcbind
tcp6 0 0 :::51413 :::* LISTEN 1484/transmission-d
tcp6 0 0 :::22 :::* LISTEN 1370/sshd
tcp6 0 0 :::445 :::* LISTEN 1754/smbd
udp 0 0 0.0.0.0:38088 0.0.0.0:* 1243/avahi-daemon:
udp 0 0 0.0.0.0:51413 0.0.0.0:* 1484/transmission-d
udp 0 0 0.0.0.0:743 0.0.0.0:* 1416/rpcbind
udp 0 0 0.0.0.0:5353 0.0.0.0:* 1243/avahi-daemon:
udp 0 0 192.168.1.3:47686 0.0.0.0:* 1499/minidlnad
udp 0 0 0.0.0.0:43112 0.0.0.0:* 1484/transmission-d
udp 0 0 0.0.0.0:1900 0.0.0.0:* 1499/minidlnad
udp 0 0 0.0.0.0:111 0.0.0.0:* 1416/rpcbind
udp 0 0 192.168.1.3:123 0.0.0.0:* 1511/ntpd
udp 0 0 127.0.0.1:123 0.0.0.0:* 1511/ntpd
udp 0 0 0.0.0.0:123 0.0.0.0:* 1511/ntpd
udp 0 0 192.168.1.255:137 0.0.0.0:* 1610/nmbd
udp 0 0 192.168.1.3:137 0.0.0.0:* 1610/nmbd
udp 0 0 0.0.0.0:137 0.0.0.0:* 1610/nmbd
udp 0 0 192.168.1.255:138 0.0.0.0:* 1610/nmbd
udp 0 0 192.168.1.3:138 0.0.0.0:* 1610/nmbd
udp 0 0 0.0.0.0:138 0.0.0.0:* 1610/nmbd
udp6 0 0 :::743 :::* 1416/rpcbind
udp6 0 0 :::5353 :::* 1243/avahi-daemon:
udp6 0 0 :::111 :::* 1416/rpcbind
udp6 0 0 ::1:123 :::* 1511/ntpd
udp6 0 0 :::123 :::* 1511/ntpd
udp6 0 0 :::39091 :::* 1243/avahi-daemon:
And you are sure Kodi is running? GUI is on the screen?
What’s the output of ps -aus | grep kodi
Ok, If I connect the cable right away, I get weird screen.
Then I rebooted and I could see the GUI (osmc).
but If I do:
ps -aus | grep kodi
I get:
error: user name does not exist
Sorry miss typed ps -aux |grep kodi
But when you see the GUI then run the netstat
then I get this:
root 2084 0.0 0.0 5384 188 ? S 15:52 0:00 sudo -u osmc xinit /usr/lib/kodi/kodi.bin --standalone -fs --lircdev /var/run/lirc/lircd
osmc 2091 0.0 0.0 3492 228 ? S 15:52 0:00 xinit /usr/lib/kodi/kodi.bin --standalone -fs --lircdev /var/run/lirc/lircd
osmc 2102 8.2 43.1 442164 105740 ? SLl 15:52 1:28 /usr/lib/kodi/kodi.bin --standalone -fs --lircdev /var/run/lirc/lircd
So what is the output of netstat at that point?
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:9091 0.0.0.0:* LISTEN 1484/transmission-d
tcp 0 0 0.0.0.0:8200 0.0.0.0:* LISTEN 1507/minidlnad
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 1639/smbd
tcp 0 0 0.0.0.0:1038 0.0.0.0:* LISTEN 2102/kodi.bin
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1452/rpcbind
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 2102/kodi.bin
tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN 2092/X
tcp 0 0 0.0.0.0:8085 0.0.0.0:* LISTEN 1573/python
tcp 0 0 0.0.0.0:51413 0.0.0.0:* LISTEN 1484/transmission-d
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1389/sshd
tcp 0 0 0.0.0.0:36666 0.0.0.0:* LISTEN 2102/kodi.bin
tcp 0 0 0.0.0.0:5050 0.0.0.0:* LISTEN 1549/python
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 1639/smbd
tcp6 0 0 ::1:9090 :::* LISTEN 2102/kodi.bin
tcp6 0 0 :::139 :::* LISTEN 1639/smbd
tcp6 0 0 :::111 :::* LISTEN 1452/rpcbind
tcp6 0 0 :::8080 :::* LISTEN 2102/kodi.bin
tcp6 0 0 :::6000 :::* LISTEN 2092/X
tcp6 0 0 :::51413 :::* LISTEN 1484/transmission-d
tcp6 0 0 :::22 :::* LISTEN 1389/sshd
tcp6 0 0 :::36666 :::* LISTEN 2102/kodi.bin
tcp6 0 0 :::36667 :::* LISTEN 2102/kodi.bin
tcp6 0 0 :::445 :::* LISTEN 1639/smbd
udp 0 0 0.0.0.0:51413 0.0.0.0:* 1484/transmission-d
udp 0 0 0.0.0.0:5353 0.0.0.0:* 1243/avahi-daemon:
udp 0 0 0.0.0.0:760 0.0.0.0:* 1452/rpcbind
udp 0 0 0.0.0.0:42243 0.0.0.0:* 1393/atvclient
udp 0 0 127.0.0.1:9777 0.0.0.0:* 2102/kodi.bin
udp 0 0 192.168.1.3:45629 0.0.0.0:* 1507/minidlnad
udp 0 0 0.0.0.0:51291 0.0.0.0:* 1243/avahi-daemon:
udp 0 0 0.0.0.0:1900 0.0.0.0:* 2102/kodi.bin
udp 0 0 0.0.0.0:1900 0.0.0.0:* 1507/minidlnad
udp 0 0 0.0.0.0:10862 0.0.0.0:* 2102/kodi.bin
udp 0 0 0.0.0.0:111 0.0.0.0:* 1452/rpcbind
udp 0 0 192.168.1.3:123 0.0.0.0:* 1498/ntpd
udp 0 0 127.0.0.1:123 0.0.0.0:* 1498/ntpd
udp 0 0 0.0.0.0:123 0.0.0.0:* 1498/ntpd
udp 0 0 192.168.1.255:137 0.0.0.0:* 1604/nmbd
udp 0 0 192.168.1.3:137 0.0.0.0:* 1604/nmbd
udp 0 0 0.0.0.0:137 0.0.0.0:* 1604/nmbd
udp 0 0 192.168.1.255:138 0.0.0.0:* 1604/nmbd
udp 0 0 192.168.1.3:138 0.0.0.0:* 1604/nmbd
udp 0 0 0.0.0.0:138 0.0.0.0:* 1604/nmbd
udp 0 0 0.0.0.0:54937 0.0.0.0:* 1484/transmission-d
udp6 0 0 :::5353 :::* 1243/avahi-daemon:
udp6 0 0 :::760 :::* 1452/rpcbind
udp6 0 0 :::48139 :::* 1243/avahi-daemon:
udp6 0 0 :::111 :::* 1452/rpcbind
udp6 0 0 ::1:123 :::* 1498/ntpd
udp6 0 0 :::123 :::* 1498/ntpd
So netstat -tulnp | grep kodi should not give you an empty result any more?
While still kodi seems not to be listening on port 80 or 8080
I get this:
tcp 0 0 0.0.0.0:1038 0.0.0.0:* LISTEN 2102/kodi.bin
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 2102/kodi.bin
tcp 0 0 0.0.0.0:36666 0.0.0.0:* LISTEN 2102/kodi.bin
tcp6 0 0 ::1:9090 :::* LISTEN 2102/kodi.bin
tcp6 0 0 :::8080 :::* LISTEN 2102/kodi.bin
tcp6 0 0 :::36666 :::* LISTEN 2102/kodi.bin
tcp6 0 0 :::36667 :::* LISTEN 2102/kodi.bin
udp 0 0 127.0.0.1:9777 0.0.0.0:* 2102/kodi.bin
udp 0 0 0.0.0.0:1900 0.0.0.0:* 2102/kodi.bin
udp 0 0 0.0.0.0:10862 0.0.0.0:* 2102/kodi.bin
Everything seems to work if I type:
osmc:8080
So you still prefer to have it running on port 80?
No, really.
I’d like to know why I can’t use IP but as long as it works it’s ok with me.
Well you can as soon as you successfully change the port to 80.
So if you really want to figure it out then we have to continue to work this out together.
ok, how do we do?
sudo systemctl stop mediacenter
and then report output of
cat .kodi/userdata/guisettings.xml | grep web
Watch out this will reveal your web password so you might want to XXXXX that
Hi, thanks for your help.
here is the output:
webserver default=“true”>true
webserverpassword default=“true”>
webserverport default=“true”>8080
webserverusername default=“true”>
webskin default=“true”>webinterface.default
First a tip, when posting any code use the “pre-formatted text” button that looks like this </>
Second this indicates you have not change to port 80. So either with mediacenter running change it via the GUI. Or now with mediacenter stopped change it manually with nano .kodi/userdata/guisettings.xml and change 8080 to 80.
Then restart mediacenter
If you change it via nano when mediacenter is running it will be discarded
ok, thanks for your patience.
I did stop and change the value, then I do the “… grep web” and I get this:
<webserver default="true">true</webserver>
<webserverpassword default="true">XXXXXXXX</webserverpassword>
<webserverport default="true">80</webserverport>
<webserverusername default="true"></webserverusername>
<webskin default="true">webinterface.default</webskin>
and after sudo systemctl start mediacenter
I am no longer able to reach kodi from : IP:80, IP:8080, osmc:80, nor osmc:8080
In the meantime I can stiull reach couchpotato on osmc:5050
Actually you need to remove the default="true".
So first stop mediacenter and then remove that and set to 80. should look like that
<webserverport>80</webserverport>