AzuraCast

You can start by checking the documentation for tips and pointers. Many common issues can be resolved by following the instructions in the guide pages. Additionally, checking the system logs can help identify the cause of your issue and provide more details for diagnosis.

You can flush all site-wide caches using a command-line script. Run the following command: ./docker.sh cli cache:clear.

This error typically occurs when Liquidsoap's internal audio buffer falls behind the broadcast. Common causes include an underprovisioned server, using CPU-heavy features, or having too many mount points/remotes/HLS streams. Try disabling CPU-heavy features or upgrading your server. If the issue persists, collect your station logs and submit an issue on the Liquidsoap GitHub.

This error occurs when your Docker version and Docker Compose version do not match. To fix it, run the following commands: cd /var/azuracast, ./docker.sh update-self, ./docker.sh install-docker, and ./docker.sh install-docker-compose. You may need to prefix these commands with sudo if running as non-root.

This error means another process is using the port(s) AzuraCast needs. You can either find and disable the conflicting process or change AzuraCast's port to an unused one, such as 8080.

AzuraCast automatically takes a database snapshot before migrations and attempts to restore from it if a failure occurs. If the automatic recovery fails, restoring from a routine backup is the simplest solution. Manual execution of incomplete SQL commands is possible but not officially supported.

Refer to the guide on how to report a bug for detailed instructions on submitting an issue.