Cannot log into the Dashboard, URL opens a random Album Art about azuracast

[BusterNeece]

@renatopinto89 That's a very unusual error to be having. It implies that something upstream of AzuraCast (maybe a reverse proxy or something similar) is aggressively misconfigured.

Is there anything between the AzuraCast installation and the web in this case?

[renatopinto89]

UPDATE!
It got even worse, now NGINX completely crashes to the point even UptimeRobot triggers a Server Down alert, nothing responds to the web ports until I restart the AzuraCast Containers.

Is there any way to restart NGINX through the command line in a way that the streams themselves don't restart? I ask because the streams keep functioning through the IP:Port addresses

This could be overloaded Server but CPU never goes over 20% neither does RAM.

Hi @BusterNeece

Thank you so much for your reply.

Nothing else is running in that Server, only the AzuraCast docker container.

DNS is managed through Cloudflare, but as DNS Only, not cached

Kind Regards

[BusterNeece]

@renatopinto89 Can you try switching to the Rolling Release channel and updating to the latest version? We have a working theory of what might be causing this and want to see if our changes resolve anything.

[renatopinto89]

@BusterNeece Hi Buster, thank you so much for the reply.

I did switch to rolling release and now monitoring status.

Something I might add, last night, the Front-End completely crashed again and saw this in the logs (this was before the switch to Rolling Release)

azuracast | {"level":"error","ts":1715396738069158575,"logger":"server","msg":"no free workers in the pool, wait timeout exceed","reason":"no free workers","internal_event_name":"EventNoFreeWorkers","error":"worker_watcher_get_free_worker: NoFreeWorkers:\n\tcontext deadline exceeded"}
azuracast | {"level":"error","ts":1715396738069212025,"logger":"http","msg":"execute","start":1715396678068023353,"elapsed":60.001187932,"error":"static_pool_exec: NoFreeWorkers:\n\tstatic_pool_exec:\n\tworker_watcher_get_free_worker:\n\tcontext deadline exceeded"}

[BusterNeece]

@renatopinto89 I'm assuming that this issue is fixed now as of the latest stable (0.20.0) or the latest Rolling Release?

[renatopinto89]

Hi Buster
Everything seems to be running normally without those crashes since the latest stable (0.20.0).
Thank you so much for the follow up and for your help.

Kind Regards