[PROBLEM] Streaming moode to browser

[batman75]

Hello all

I've been using moode pretty successfully over the last 6-7 months. However, we recently moved house and wound up disconnecting everything quite brutally. I've since hooked everything back up again and all seems to be working ok...

APART FROM STREAMING!

My pi is connected via bluetooth to my amp in the front room, but I work at the back of the house and want to listen to music here. I used to be able to stream using http://moode:8000 but since moving, it's stopped working. Streaming is enabled in the audio options on port 8000 and I can play music on the amp, but on the browser (Chrome 94 on Win10, latest version of moode), I get an ERR_CONNECTION_REFUSED message.

Any thoughts on where I should look next please?

Thanks

[TheOldPresbyope]

@batman75

A little Internet searching turns up blog entries like "how to fix the ERR_CONNECTION_REFUSED..."

Could be as simple as clearing your browser cache...or not .

Regards,
Kent

[batman75]

@TheOldPresbyope

Thanks for the suggestions. Unfortunately, none that I tried (restarting router, clearing cache, flushing dns, disabling firewall/anti-virus) managed to work. I then thought I might have a problem because pi is attached to the router via a switch, but plugging in directly hasn't made a difference either. I've also tried restarting the http streaming, but still nothing.

[Tim Curtis]

I just ran a quick test and no issues in the configuration below. 

Code:

RP1 - HTTP Server ON
    - Play track
RP2 - Create radio station "New station" with URL = http://rp1:8000
   - Play "New station"
    - Track playing on host RP1 is playing on this host

Trying to access http://rp1:8000 via Browser though is not successful. In my case Safari just stays at a "loading" progress bar of about 10%.

What do you expect happen when accessing via Browser?

[vinnn]

Working fine for me, both with MP3 and FLAC streaming on the default port 8000.
@batman75 to rule out a name resolution issue on your home network try using the IP address instead of the "moode" hostname.

[Tim Curtis]

What player is being activated by Browser?

[batman75]

Working fine for me, both with MP3 and FLAC streaming on the default port 8000.
@batman75 to rule out a name resolution issue on your home network try using the IP address instead of the "moode" hostname.

Tried both mp3 and flac on both moode and ip address and the same result with both (i.e. nothing).

I just ran a quick test and no issues in the configuration below. 

Code:

RP1 - HTTP Server ON
   - Play track
RP2 - Create radio station "New station" with URL = http://rp1:8000
   - Play "New station"
   - Track playing on host RP1 is playing on this host

Trying to access http://rp1:8000 via Browser though is not successful. In my case Safari just stays at a "loading" progress bar of about 10%.

What do you expect happen when accessing via Browser?

Sorry, I'm not exactly sure what you mean here. I used to see a tab with a basic audio player (i.e. play/pause/duration), but I'm not getting close to that. With the RP1/RP2 comments, is that something I should try to test things? If so, where would I make the changes - sorry, Linux/pi novice here so I might need some spoon-feeding.

[Tim Curtis]

I'm turning on the http server on Pi #1 and then creating a radio station on Pi #2 to access the http stream from Pi #1. That confirms that the http server on Pi #1 is working properly.

I don't know why your Browser isn't launching the basic player as it had previously but in my case Safari Browser doesn't launch one either.

[batman75]

I'm turning on the http server on Pi #1 and then creating a radio station on Pi #2 to access the http stream from Pi #1. That confirms that the http server on Pi #1 is working properly.

I don't know why your Browser isn't launching the basic player as it had previously but in my case Safari Browser doesn't launch one either.

Ah, ok, thanks for clarifying. Makes sense now.

I'm not sure if the browser is even getting to the point where it needs to launch the player. It feels like I've ballsed something up on the pi, but I have no idea what. I tried switching the http streamer off and on, and the log shows the following.

20211014 074212 worker: Job mpd_httpd
20211014 074444 worker: Job mpd_httpd
20211014 074642 waitWorker(): Start (sys-config, w_active=0)
20211014 074642 waitWorker(): End   (sys-config, w_active=0)
20211014 074712 waitWorker(): Start (snd-config, w_active=0)
20211014 074712 waitWorker(): End   (snd-config, w_active=0)
20211014 074722 waitWorker(): Start (snd-config, w_active=1)
20211014 074723 waitWorker(): Wait  (1)
20211014 074724 worker: Job mpd_httpd
20211014 074724 waitWorker(): Wait  (2)
20211014 074724 waitWorker(): End   (snd-config, w_active=0)
20211014 074802 waitWorker(): Start (snd-config, w_active=1)
20211014 074803 waitWorker(): Wait  (1)
20211014 074804 waitWorker(): Wait  (2)
20211014 074804 worker: Job mpd_httpd
20211014 074805 waitWorker(): Wait  (3)
20211014 074805 waitWorker(): End   (snd-config, w_active=0)

Is there anywhere I can check on the pi itself to see if the streamer is actually running?

[Tim Curtis]

First I would turn off debug logging. Its not really necessary in this case.

Run the command below to confirm that HTTP server is enabled.

Code:

mpc outputs