Can't access webui 6.5X - Printable Version

Can't access webui 6.5X - Printable Version

+- Moode Forum (http://moodeaudio.org/forum)
+-- Forum: moOde audio player (http://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (http://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: Can't access webui 6.5X (/showthread.php?tid=2519)

Can't access webui 6.5X - baek47 - 05-12-2020

Hi
I have used 6.4.X and a lot of prev. versions - and I like it :- )

After installing either 6.5.0/6.5.1/6.51 and powering rpi4, I can't connect to Moode through webinterface.....like i use to. It is wired network.
I have tried different computers, phones, browsers.
I can't see it with "Fling" (a phone ip-lister).
I can't see hotspot wifi- even wired cable is out.

I can see it in my "explorer" under network as MOODE and i can browse shared directories
I can ping it from Win10, but i get no ip-address, just a hardware address (looks like that)
I can sh from putty.

I need a little magic…..

-baek47

RE: Can't access webui 6.5X - Tim Curtis - 05-12-2020

Post the Moode startup log

Code:
moodeutl -l

RE: Can't access webui 6.5X - TheOldPresbyope - 05-12-2020

(05-12-2020, 12:25 PM)baek47 Wrote: ...
I can ping it from Win10, but i get no ip-address, just a hardware address (looks like that)
I can sh from putty.

I need a little magic…..

-baek47

Are you running dual-stack IPv4/IPv6 on your LAN? IPv6 addresses look a bit like a hardware address.

Regards,
Kent

RE: Can't access webui 6.5X - baek47 - 05-13-2020

(05-12-2020, 12:45 PM)Tim Curtis Wrote: Post the Moode startup log

Code:
moodeutl -l

Here is moodeutl -1

20200512 070930 worker: -- Start
20200512 070930 worker: Successfully daemonized
20200512 070930 worker: Integrity check (passed)
20200512 070930 worker: Session loaded
20200512 070930 worker: Debug logging (off)
20200512 070930 worker: Device raw: (0:ALSA|1:empty|i2s:none)
20200512 070930 worker: Device cfg: (On-board audio device|0|0|PCM|0)
20200512 070931 worker: ALSA volume set to (0%)
20200512 070931 worker: -- System
20200512 070933 worker: Host     (moode)
20200512 070934 worker: moOde    (6.5.2 2020-05-03)
20200512 070934 worker: Raspbian (10.3)
20200512 070934 worker: Kernel   (4.19.115-v7l+ #1305)
20200512 070934 worker: Platform (Pi-4B 4GB v1.1)
20200512 070934 worker: ARM arch (armv7l, 32-bit kernel)
20200512 070934 worker: MPD ver (0.21.22)
20200512 070934 worker: CPU gov (ondemand)
20200512 070934 worker: USB boot not available
20200512 070934 worker: File system not expanded yet

RE: Can't access webui 6.5X - baek47 - 05-13-2020

(05-12-2020, 12:54 PM)TheOldPresbyope Wrote:
(05-12-2020, 12:25 PM)baek47 Wrote: ...
I can ping it from Win10, but i get no ip-address, just a hardware address (looks like that)
I can sh from putty.

I need a little magic…..

-baek47

Are you running dual-stack IPv4/IPv6 on your LAN? IPv6 addresses look a bit like a hardware address.

Regards,
Kent

I think thats the problem, probably yes to dual stack.
Can I force ipv4 in Moode? Or connect to Moode via ipv6?

RE: Can't access webui 6.5X - baek47 - 05-13-2020

Her is:
[email=pi@moode:/etc]pi@moode:/etc[/email] $ sudo ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.1.40 netmask 255.255.255.0 broadcast 192.168.1.255
        inet6 xxxx::xxx:xxxx:d944:20f9 prefixlen 64 scopeid 0x20<link>
        ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)
        RX packets 1249 bytes 103663 (101.2 KiB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 448 bytes 84422 (82.4 KiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
        inet 127.0.0.1 netmask 255.0.0.0
        inet6 ::1 prefixlen 128 scopeid 0x10<host>
        loop txqueuelen 1000 (Local Loopback)
        RX packets 0 bytes 0 (0.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 0 bytes 0 (0.0 B)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
        ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)
        RX packets 0 bytes 0 (0.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 0 bytes 0 (0.0 B)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

RE: Can't access webui 6.5X - TheOldPresbyope - 05-13-2020

@baek47

Your moodeutl -l report was truncated before it got to the interesting bit. The next section should have read something like (where I obscured my AP SSID and my domain):

Code:
20200513 070907 worker: -- Network

20200513 070907 worker: eth0 exists

20200513 070907 worker: eth0 address not assigned

20200513 070907 worker: wlan0 exists

20200513 070907 worker: wifi country (US)

20200513 070907 worker: wlan0 trying SSID (xxxxxx)

20200513 070907 worker: IP addr (192.168.1.182)

20200513 070907 worker: Netmask (255.255.255.0)

20200513 070907 worker: Gateway (192.168.1.1)

20200513 070907 worker: Pri DNS (192.168.1.1)

20200513 070907 worker: Domain  (xxxxx.home)

Please post this section from the report for your player.

As for my question, sorry, I should have been more explicit.

The ifconfig information you posted shows normal information for a moOde player connected via ethernet. The ethernet interface eth0 is listening for both IPv4 and IPv6 packets. It has been assigned a routable IPv4 address, presumably from your network's DHCP server, but it has only a link-local IPv6 address (fe80:...) which tells me your network isn't dishing out global IPv6 addresses. This suggests that you're not running dual stack IPv4/IPv6 on your network.

What I should have asked for is the address returned when you tried to ping your moOde player from Windows. NOTE - it's safe to post link-local addresses, but it's not a good idea to post complete global IPv6 addresses (anything not starting fe80:...) because they are truly global. Anyone can touch a global IPv6 address from anywhere in the world. There's a fair amount of security built into the protocol by default but it's still good practice is to obscure everything after the first 6 or so characters.

Coincidentally, in just the last few days a few test team members have taken up the challenge of making moOde IPv6-clean. It's made a bit complicated by the fact that some us (like me) don't actually have IPv6 service from our ISP.

Regards,
Kent

RE: Can't access webui 6.5X - baek47 - 05-13-2020

(05-13-2020, 11:46 AM)TheOldPresbyope Wrote: @baek47

Your moodeutl -l report was truncated before it got to the interesting bit. The next section should have read something like (where I obscured my AP SSID and my domain):

Code:
20200513 070907 worker: -- Network 20200513 070907 worker: eth0 exists 20200513 070907 worker: eth0 address not assigned 20200513 070907 worker: wlan0 exists 20200513 070907 worker: wifi country (US) 20200513 070907 worker: wlan0 trying SSID (xxxxxx) 20200513 070907 worker: IP addr (192.168.1.182) 20200513 070907 worker: Netmask (255.255.255.0) 20200513 070907 worker: Gateway (192.168.1.1) 20200513 070907 worker: Pri DNS (192.168.1.1) 20200513 070907 worker: Domain (xxxxx.home)

Please post this section from the report for your player.

As for my question, sorry, I should have been more explicit.

The ifconfig information you posted shows normal information for a moOde player connected via ethernet. The ethernet interface eth0 is listening for both IPv4 and IPv6 packets. It has been assigned a routable IPv4 address, presumably from your network's DHCP server, but it has only a link-local IPv6 address (fe80:...) which tells me your network isn't dishing out global IPv6 addresses. This suggests that you're not running dual stack IPv4/IPv6 on your network.

What I should have asked for is the address returned when you tried to ping your moOde player from Windows. NOTE - it's safe to post link-local addresses, but it's not a good idea to post complete global IPv6 addresses (anything not starting fe80:...) because they are truly global. Anyone can touch a global IPv6 address from anywhere in the world. There's a fair amount of security built into the protocol by default but it's still good practice is to obscure everything after the first 6 or so characters.

Coincidentally, in just the last few days a few test team members have taken up the challenge of making moOde IPv6-clean. It's made a bit complicated by the fact that some us (like me) don't actually have IPv6 service from our ISP.

Regards,
Kent

Hi Kent
Thanks :-)) - and my moodeutl -l report wasn´t any longer, stops at "filesystem...." I tried several times. How do I get more report?
I have tried to add some ip-adresses in mpd.config, and changed a #presendece" in "host", nothing helped (i m really not an expert).
Get back to me if you want me to test any Ipv6-clean changes :-) on my network.
Im out of town 2 days, so i cant answer.
Regards baek47