Environment
moOde version: 10.1.2
Device: Raspberry Pi 3
Access via browser on desktop Linux
Network: tested via IP address and moode.local
Problem
After installing moOde 10.1.2, the Web UI sometimes became partially broken after boot when Autoplay was enabled.
The page loaded, but the GUI was incomplete and unusable.
Only a minimal layout was shown, mainly the playback knob circles and a few small UI elements. The normal player interface did not appear.
What I observed
nginx was running normally
php8.4-fpm was running normally
CSS and JavaScript assets loaded with HTTP 200
the problem occurred in different browsers
the problem also occurred in private browsing mode
clearing browser cache/site data did not help
the issue was reproducible even when accessing moOde directly by IP address
Important finding
The request to engine-mpd.php appeared to hang.
When testing locally on the Pi:
curl -s "http://127.0.0.1/engine-mpd.php?state=undefined"
the command did not return and had to be aborted manually.
The log contained this line:
Engine-mpd: socket timeout (600000 secs)
Relevant log excerpt
worker: Current view: reset to Playback
worker: Active flags: all false
worker: Reset flags: skipped
worker: Engine-mpd: socket timeout (600000 secs)
worker: Session check: ok
worker: -- Startup complete
worker: Auto-play: on
worker: Auto-play: using songid 27
Workaround / Fix
Disabling Autoplay and rebooting the system fixed the issue immediately.
After disabling Autoplay:
the Web UI loaded normally again
the player became fully usable
the problem did not reappear
Additional notes
I have used moOde for many years and did not experience this behavior with older versions.
This looks like a regression in moOde 10.1.2 related to Autoplay and/or the playback state during startup.
Possible trigger
Autoplay may be trying to resume a problematic playback item, queue state, or stream during boot, which then causes engine-mpd.php to hang and prevents the Web UI from initializing correctly.
Steps to reproduce
Install moOde 10.1.2
Enable Autoplay
Reboot the system
Open the Web UI
In my case, the UI sometimes loads only partially and becomes unusable
Expected behavior
The full Web UI should load normally after boot, even when Autoplay is enabled.
Actual behavior
The UI loads only partially, appears broken, and engine-mpd.php hangs until Autoplay is disabled and the system is rebooted.
Environment
moOde version: 10.1.2
Device: Raspberry Pi 3
Access via browser on desktop Linux
Network: tested via IP address and moode.local
Problem
After installing moOde 10.1.2, the Web UI sometimes became partially broken after boot when Autoplay was enabled.
The page loaded, but the GUI was incomplete and unusable.
Only a minimal layout was shown, mainly the playback knob circles and a few small UI elements. The normal player interface did not appear.
What I observed
nginx was running normally
php8.4-fpm was running normally
CSS and JavaScript assets loaded with HTTP 200
the problem occurred in different browsers
the problem also occurred in private browsing mode
clearing browser cache/site data did not help
the issue was reproducible even when accessing moOde directly by IP address
Important finding
The request to engine-mpd.php appeared to hang.
When testing locally on the Pi:
curl -s "http://127.0.0.1/engine-mpd.php?state=undefined"
the command did not return and had to be aborted manually.
The log contained this line:
Engine-mpd: socket timeout (600000 secs)
Relevant log excerpt
worker: Current view: reset to Playback
worker: Active flags: all false
worker: Reset flags: skipped
worker: Engine-mpd: socket timeout (600000 secs)
worker: Session check: ok
worker: -- Startup complete
worker: Auto-play: on
worker: Auto-play: using songid 27
Workaround / Fix
Disabling Autoplay and rebooting the system fixed the issue immediately.
After disabling Autoplay:
the Web UI loaded normally again
the player became fully usable
the problem did not reappear
Additional notes
I have used moOde for many years and did not experience this behavior with older versions.
This looks like a regression in moOde 10.1.2 related to Autoplay and/or the playback state during startup.
Possible trigger
Autoplay may be trying to resume a problematic playback item, queue state, or stream during boot, which then causes engine-mpd.php to hang and prevents the Web UI from initializing correctly.
Steps to reproduce
Install moOde 10.1.2
Enable Autoplay
Reboot the system
Open the Web UI
In my case, the UI sometimes loads only partially and becomes unusable
Expected behavior
The full Web UI should load normally after boot, even when Autoplay is enabled.
Actual behavior
The UI loads only partially, appears broken, and engine-mpd.php hangs until Autoplay is disabled and the system is rebooted.