mariolukas/HydraPlay

No client connected

Medel opened this issue · 6 comments

Medel commented

I tried to create Hydraplay with Podman, Podman-compose but there are no clients. It only shows "Hydraplay" and "no clients connected". Sometimes a window with "MOPIDY-0/1 not connected".

There are no "stream_{0/1}.fifo" in "/tmp" in the container
Log.txt

Medel commented

I have changed the config from tcp to fifo. Now the "stream_{0/1}.fifo" exist.
Snapcast works - tested with cat /dev/urandom > /tmp/stream_0.fifo

But Hydraplay no success

I am not familiar with podman, but can you double check your port configuration. Most issues like yours are related to the port configuration.

Medel commented

Port configuration should be right:
1704/tcp -> 0.0.0.0:1704
1705/tcp -> 0.0.0.0:1705
1780/tcp -> 0.0.0.0:1780
6680/tcp -> 0.0.0.0:6680
6681/tcp -> 0.0.0.0:6681
6682/tcp -> 0.0.0.0:6682
6683/tcp -> 0.0.0.0:6683
6684/tcp -> 0.0.0.0:6684
6685/tcp -> 0.0.0.0:6685
6686/tcp -> 0.0.0.0:6686
6687/tcp -> 0.0.0.0:6687
6688/tcp -> 0.0.0.0:6688
6689/tcp -> 0.0.0.0:6689
6690/tcp -> 0.0.0.0:6690
8080/tcp -> 0.0.0.0:8080

I noticed when i was testing yesterday that the websocket port just using the docker compose seemed to be the issue. I discovered it was trying to hit the websocket port in the dev tools in my browser watching the console. I then added port 80 to 8080 in the docker-compose file and it stopped the issue.

Medel commented

That works also with podman

Medel commented

After some tests:
Test with Opensuse 15.4 Firefox V112.0(64Bit) and Chromium V112.0.5615.121
Up to version 0.8.0 from docker hub it works with the Chrome browser
It does not work with Firefox
Firefox tries to read: http://192.168.0.1:8080/api/settings -> 404 Not Found
Chrome reads: http://192.168.0.1:8080/api/mopidy/settings