Containers not starting
If one or more containers fail to start, check the logs:-
Missing
.envfile — Copy the example and fill in your values: -
Port conflicts — Another service may already be using the required ports. Check with:
-
Missing emergency audio — Liquidsoap requires at least one fallback audio file in
emergency-audio/. Add an MP3, FLAC, or WAV file to this directory.
No audio playing
Verify the stream mount point
Confirm your mount point is configured correctly in the streams configuration.
Status panel not loading
-
Verify the status panel container is running:
- Check that the configured port is accessible and not blocked by your firewall.
-
Review the status panel logs for errors:
Analytics not recording
-
Confirm the analytics container is running:
- Check the analytics configuration for correct database connection settings.
-
Review the tracker logs:
High CPU or memory usage
-
Check which container is consuming resources:
- If Liquidsoap is using excessive CPU, reduce the number of concurrent streams or lower the encoding bitrate.
- Consider allocating more resources to the host machine for production workloads.
Docker Compose errors
| Error | Solution |
|---|---|
service "x" depends on undefined service | Verify all service names in docker-compose.yml match exactly |
port is already allocated | Stop the conflicting service or change the port in .env |
no matching manifest for linux/arm64 | Some images may not support ARM. Check for alternative images or build from source |
Still stuck?
If none of the above resolves your issue:- Search GitHub Issues for similar problems
- See the contact and help page for more support options

