Moode Forum
[SOLVED] HTTP Streaming not working - Printable Version

+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: [SOLVED] HTTP Streaming not working (/showthread.php?tid=5973)

Pages: 1 2


HTTP Streaming not working - hurcheon - 12-01-2023

Hi

This is a fresh build, using the imager. WiFi working, though only by IP address via wifi, I can get it resolve the name if I attached an Ethernet cable

However I would like to stream the music to browser, to be able to play from any device in a simple matter

So under the AUDI0, I have set up the HTTP Streamer, and left it to default

But it is not working, Any thoughts about what I am doing wrong

Thanks

Code:
This site can’t be reached
[color=#5f6368][size=small][b]192.168.1.236[/b] refused to connect.[/size][/color]
[color=#5f6368][size=small]Try:[/size][/color]
Checking the connectionChecking the proxy and the firewall
ERR_CONNECTION_REFUSED



Startup log
Code:
20231201 123449 worker: --
20231201 123449 worker: -- Start moOde 8 series
20231201 123449 worker: --
20231201 123449 worker: Successfully daemonized
20231201 123449 worker: Waiting for Linux startup...
20231201 123501 worker: Linux startup complete
20231201 123501 worker: Boot config backed up
20231201 123503 worker: File check (OK)
20231201 123504 worker: Session vacuumed
20231201 123504 worker: Session loaded
20231201 123504 worker: Debug logging (OFF)
20231201 123504 worker: Reduced system logging (OFF)
20231201 123504 worker: --
20231201 123504 worker: -- Audio debug
20231201 123504 worker: --
20231201 123504 worker: ALSA cards: (0:Headphones | 1:IQaudIODAC | 2:empty | 3:empty
20231201 123504 worker: MPD config: (1:IQaudIODAC | mixer:(Analogue) | card:1)
20231201 123505 worker: ALSA mixer actual (Analogue)
20231201 123505 worker: ALSA Analogue volume set to (0%)
20231201 123505 worker: --
20231201 123505 worker: -- System
20231201 123505 worker: --
20231201 123506 worker: Host      (moode)
20231201 123506 worker: Hardware  (Pi-4B 1.5 4GB)
20231201 123506 worker: moOde     (8.3.6 2023-09-05)
20231201 123506 worker: RaspiOS   (11.7)
20231201 123506 worker: Kernel    (6.1.21-v8+ #1642)
20231201 123506 worker: Procarch  (aarch64, 64-bit)
20231201 123506 worker: MPD ver   (0.23.12)
20231201 123506 worker: CPU gov   (ondemand)
20231201 123506 worker: Userid    (moodeuser)
20231201 123506 worker: Homedir   (/home/moodeuser)
20231201 123506 worker: Timezone  (Europe/London)
20231201 123506 worker: Keyboard  (gb)
20231201 123506 worker: USB boot  (enabled)
20231201 123506 worker: File sys  (expanded)
20231201 123507 worker: HDMI port (On)
20231201 123507 worker: Sys LED0  (On)
20231201 123507 worker: Sys LED1  (On)
20231201 123507 worker: --
20231201 123507 worker: -- Network
20231201 123507 worker: --
20231201 123507 worker: eth0 adapter exists
20231201 123507 worker: eth0 address check (Off)
20231201 123507 worker: eth0 address not assigned
20231201 123507 worker: wlan0 adapter exists
20231201 123507 worker: wlan0 country (GB)
20231201 123507 worker: wlan0 configured SSID (MyNetSSID)
20231201 123507 worker: wlan0 SSID alternates (None)
20231201 123507 worker: wlan0 router mode (Off)
20231201 123507 worker: wlan0 address check (up to 90 secs)
20231201 123507 worker: wlan0 connected to SSID (MyNetSSID)
20231201 123507 worker: wlan0 power save (Disabled)
20231201 123507 worker: IP addr (192.168.1.236)
20231201 123507 worker: Netmask (255.255.255.0)
20231201 123507 worker: Gateway (192.168.1.254)
20231201 123507 worker: Pri DNS (192.168.1.254)
20231201 123507 worker: Domain  (home)
20231201 123507 worker: --
20231201 123507 worker: -- Software update
20231201 123507 worker: --
20231201 123507 worker: Automatic check (On)
20231201 123507 worker: Checking for available update...
20231201 123507 worker: Software is up to date
20231201 123507 worker: --
20231201 123507 worker: -- File sharing
20231201 123507 worker: --
20231201 123507 worker: SMB file sharing (Off)
20231201 123507 worker: NFS file sharing (Off)
20231201 123507 worker: --
20231201 123507 worker: -- Audio config
20231201 123507 worker: --
20231201 123507 worker: MPD conf update skipped (USB device)
20231201 123507 worker: ALSA card number (1)
20231201 123507 worker: MPD audio output (IQaudIODAC)
20231201 123507 worker: Audio formats (S16_LE, S24_LE, S32_LE)
20231201 123507 worker: ALSA mixer name (Analogue)
20231201 123507 worker: MPD mixer type (software)
20231201 123508 worker: Hdwr volume controller exists
20231201 123508 worker: Max ALSA volume (100%)
20231201 123508 worker: ALSA output mode (Default)
20231201 123508 worker: ALSA loopback (Off)
20231201 123508 worker: Renderer active flags (reset)
20231201 123508 worker: CamillaDSP configuration (off)
20231201 123508 worker: --
20231201 123508 worker: -- MPD startup
20231201 123508 worker: --
20231201 123508 worker: MPD started
20231201 123508 worker: MPD accepting connections
20231201 123508 worker: MPD output 1 ALSA Default (On)
20231201 123508 worker: MPD output 2 ALSA Bluetooth (Off)
20231201 123508 worker: MPD output 3 HTTP Server (On)
20231201 123508 worker: MPD crossfade (off)
20231201 123508 worker: MPD ignore CUE files (yes)
20231201 123508 worker: MPD camilladsp volume sync (Off)
20231201 123508 worker: MPD camilladsp volume range (60 dB)
20231201 123508 worker: --
20231201 123508 worker: -- Music sources
20231201 123508 worker: --
20231201 123508 worker: USB sources
20231201 123508 worker: Samsung USB
20231201 123508 worker: NAS sources
20231201 123508 worker: None configured
20231201 123508 worker: --
20231201 123508 worker: -- Feature availability
20231201 123508 worker: --
20231201 123508 worker: Input select (available)
20231201 123508 worker: Input (MPD)
20231201 123508 worker: Output (IQaudIODAC)
20231201 123508 worker: Bluetooth (available)
20231201 123508 worker: AirPlay renderer (available)
20231201 123508 worker: Spotify renderer (available)
20231201 123508 worker: Squeezelite (available)
20231201 123508 worker: RoonBridge renderer (not installed)
20231201 123508 worker: Multiroom sender (available)
20231201 123508 worker: Multiroom receiver (available)
20231201 123508 worker: UPnP renderer (available)
20231201 123508 worker: DLNA server (available)
20231201 123508 worker: GPIO button handler (available)
20231201 123508 worker: Stream recorder (n/a)
20231201 123508 worker: HTTPS-Only mode (n/a)
20231201 123508 worker: --
20231201 123508 worker: -- Other
20231201 123508 worker: --
20231201 123508 worker: USB volume knob (Off)
20231201 123508 worker: USB auto-mounter (udisks-glue)
20231201 123508 worker: Saved MPD vol level (0)
20231201 123508 worker: Preamp volume level (0)
20231201 123508 worker: MPD volume level (9) restored
20231201 123508 worker: ALSA Analogue volume (100%)
20231201 123508 worker: Auto-play (Off)
20231201 123509 worker: LocalUI (On)
20231201 123509 worker: Automatic CoverView (Off)
20231201 123509 worker: On-screen keyboard (Off)
20231201 123509 worker: Library scope (all)
20231201 123509 worker: Library active search (None)
20231201 123509 worker: View reset to (Playback)
20231201 123509 worker: Maintenance interval (360 minutes)
20231201 123509 worker: Screen saver activation (Never)
20231201 123509 worker: Session permissions (OK)
20231201 123509 worker: --
20231201 123509 worker: -- Startup complete 
20231201 123509 worker: --
20231201 123509 worker: Mount monitor (off)
20231201 123509 worker: Watchdog monitor (started)
20231201 123509 worker: Responsiveness (Default)
20231201 123509 worker: Ready



RE: HTTP Streaming not working - TheOldPresbyope - 12-01-2023

Huh.

It's not a feature I use, but enabling HTTP streaming with default settings on a moOde 8.3.6 player (hostname moode) just now, I can stream to my Google Pixel 6a and to my Linux Mint laptop. I used a Chromium browser on the phone and a Firefox browser on the laptop. In both cases I entered the URL


Code:
moode.local:8000


Any more details on your test? How did you try to access the HTTP server?

Regards,
Kent


RE: HTTP Streaming not working - Tim Curtis - 12-01-2023

Looks like breakage in the audio config

Code:
20231201 123504 worker: ALSA cards: (0:Headphones | 1:IQaudIODAC | 2:empty | 3:empty
20231201 123504 worker: MPD config: (1:IQaudIODAC | mixer:(Analogue) | card:1)

I2S HAT DAC's like the IQaudIO devices are always assigned ALSA card 0 but in your case it shows up on card 1.


RE: HTTP Streaming not working - TheOldPresbyope - 12-01-2023

PS

From a Linux command line, at least, it's easy to get details about the connectivity to the moOde streaming server using curl.

Example from my Linux Mint laptop


Code:
kreed@T520:~$ curl -v -o /dev/null http://moode.local:8000
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 10.0.0.6:8000...
* Connected to moode.local (10.0.0.6) port 8000 (#0)
> GET / HTTP/1.1
> Host: moode.local:8000
> User-Agent: curl/7.81.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Type: audio/mpeg
< Connection: close
< Pragma: no-cache
< Cache-Control: no-cache, no-store
< Access-Control-Allow-Origin: *
<
{ [1045 bytes data]
100  707k    0  707k    0     0  38136      0 --:--:--  0:00:18 --:--:-- 39996^C

and it continued running without error until I exited the process with a Ctrl-C.


Regards.
Kent


RE: HTTP Streaming not working - hurcheon - 12-03-2023

(12-01-2023, 02:20 PM)TheOldPresbyope Wrote: Huh.

It's not a feature I use, but enabling HTTP streaming with default settings on a moOde 8.3.6 player (hostname moode) just now, I can stream to my Google Pixel 6a and to my Linux Mint laptop. I used a Chromium browser on the phone and a Firefox browser on the laptop. In both cases I entered the URL


Code:
moode.local:8000


Any more details on your test? How did you try to access the HTTP server?

Regards,
Kent

Thanks Kent


I tried Chrome on a Windows 10 machine 

Chrome and Firefox on a Google Pixel 6 Pro

Chromium and Firefox on a Linux Mint 20 Ulyana


I tried the .local name:8000 and the IP address with the port at the end too

Neither worked


RE: HTTP Streaming not working - hurcheon - 12-03-2023

(12-01-2023, 02:52 PM)TheOldPresbyope Wrote: PS

From a Linux command line, at least, it's easy to get details about the connectivity to the moOde streaming server using curl.

Hi

Thanks for this

Tried from both Windows and Linux, this is the Windows output because this where I was looking at the forum

Code:
C:\Users\winuser> curl -v -o NUL http://192.168.1.236
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 192.168.1.236:80...
* Connected to 192.168.1.236 (192.168.1.236) port 80
> GET / HTTP/1.1
> Host: 192.168.1.236
> User-Agent: curl/8.4.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx/1.18.0
< Date: Sun, 03 Dec 2023 00:39:08 GMT
< Content-Type: text/html; charset=UTF-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Set-Cookie: PHPSESSID=ho7vk67sqrjua8sme0pqhsjgdq; path=/
< Expires: Thu, 19 Nov 1981 08:52:00 GMT
< Cache-Control: no-store, no-cache, must-revalidate
< Pragma: no-cache
<
{ [1122 bytes data]
100  158k    0  158k    0     0  2261k      0 --:--:-- --:--:-- --:--:-- 2263k
* Connection #0 to host 192.168.1.236 left intact

C:\Users\winuser> curl -v -o NUL http://192.168.1.236:8000
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 192.168.1.236:8000...
  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0* connect to 192.168.1.236 port 8000 failed: Connection refused
* Failed to connect to 192.168.1.236 port 8000 after 2075 ms: Couldn't connect to server
  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0
* Closing connection
curl: (7) Failed to connect to 192.168.1.236 port 8000 after 2075 ms: Couldn't connect to server

Interestingly, this time, Windows still refuses to resolve the domain, but Linux gets it by alias, the phone won't take either

All on the same network, weird


RE: HTTP Streaming not working - TheOldPresbyope - 12-03-2023

(12-03-2023, 12:44 AM)hurcheon Wrote:
(12-01-2023, 02:52 PM)TheOldPresbyope Wrote: PS

From a Linux command line, at least, it's easy to get details about the connectivity to the moOde streaming server using curl.

Hi

Thanks for this

Tried from both Windows and Linux, this is the Windows output because this where I was looking at the forum

Code:
C:\Users\winuser> curl -v -o NUL http://192.168.1.236
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 192.168.1.236:80...
* Connected to 192.168.1.236 (192.168.1.236) port 80
> GET / HTTP/1.1
> Host: 192.168.1.236
> User-Agent: curl/8.4.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx/1.18.0
< Date: Sun, 03 Dec 2023 00:39:08 GMT
< Content-Type: text/html; charset=UTF-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Set-Cookie: PHPSESSID=ho7vk67sqrjua8sme0pqhsjgdq; path=/
< Expires: Thu, 19 Nov 1981 08:52:00 GMT
< Cache-Control: no-store, no-cache, must-revalidate
< Pragma: no-cache
<
{ [1122 bytes data]
100  158k    0  158k    0     0  2261k      0 --:--:-- --:--:-- --:--:-- 2263k
* Connection #0 to host 192.168.1.236 left intact

C:\Users\winuser> curl -v -o NUL http://192.168.1.236:8000
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 192.168.1.236:8000...
  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0* connect to 192.168.1.236 port 8000 failed: Connection refused
* Failed to connect to 192.168.1.236 port 8000 after 2075 ms: Couldn't connect to server
  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0
* Closing connection
curl: (7) Failed to connect to 192.168.1.236 port 8000 after 2075 ms: Couldn't connect to server

Interestingly, this time, Windows still refuses to resolve the domain, but Linux gets it by alias, the phone won't take either

All on the same network, weird

Well, actually this was a check of connectivity to the default port 80 (which is the WebUI interface) rather than port 8000.

What about Tim's observation about breakage in the audio config?

Regards,
Kent


RE: HTTP Streaming not working - hurcheon - 12-03-2023

(12-03-2023, 12:54 AM)TheOldPresbyope Wrote: Well, actually this was a check of connectivity to the default port 80 (which is the WebUI interface) rather than port 8000.



What about Tim's observation about breakage in the audio config?

Regards,
Kent

Ah, so the 8000 wouldn't have worked anyway? Ah well, all part of the learning process

As to the ALSA, that is the next thing, I have four devices around me, all checking connectivity


RE: HTTP Streaming not working - hurcheon - 12-03-2023

(12-03-2023, 12:54 AM)TheOldPresbyope Wrote: Regards,
Kent


Well, it is late, and I haven't figured out where the ALSA config lives to change it, something to look into tomorrow

I am guessing that the card not being as expected is why the utility isn't helping

Thank you Tim and Kent for your help so far. It is very much appreciated

Code:
moodeuser@moode:~ $ moodeutl --hwparams

closed


Tomorrow after some sleep, even if I have to rebuild the OS Big Grin


RE: HTTP Streaming not working - TheOldPresbyope - 12-03-2023

Oops, I didn't scroll down in your codebox. Sorry.

For the test of port 8000 you got as a response "connect to 192.168.1.236 port 8000 failed: Connection refused" This suggests the service isn't running since you could reach the WebUI service (port 80) on the same host.

Regards,
Kent