Buster Neece

@manugut That's a different problem unrelated to the SSL certificate; it's likely that you have some other service running or listening on port 443 (i.e. an nginx or apache server...

@manugut Try restarting the server, and if that doesn't work create another issue here on GitHub. I want to avoid too many side issues on this pinned thread.

@drno88 This is what should be in the AzuraCast user's cron tasks as of the latest stable version: https://github.com/AzuraCast/AzuraCast/blob/main/util/ansible/roles/azuracast-cron/templates/azuracast_cron.j2

@davidkamp AzuraCast is following the appropriate documented API from Liquidsoap with regard to crossfade duration, fade-in and fade-out times, and it should be working as expected. If it isn't, this...

@NicoxDJ I can see how that would stress you out, for sure. Definitely the safest way to avoid that is to spin down the AzuraCast service while making changes to...

@paulcjkp I've updated our code to always send an annotation value for every track as a temporary workaround for this, but this won't affect things like live streams or remote...

@AaronUnmuted You may need to update again...we've been in the process of issuing several fixes over the last week or so.

@AaronUnmuted If you're on the latest Rolling Release, you may need to manually "Restart Broadcasting" on those stations...because Liquidsoap shouldn't be referring to the `web` container in those API calls,...

@AaronUnmuted @bilalbox I'm currently deploying an update to the Rolling Release branch that will add a new debug option. Under the system administration page, then System Debugger, at the bottom...

@AaronUnmuted Sadly nothing in the logs there helps with explaining why the web service would be going down repeatedly. It looks like one of the station backends is failing to...