[v3.8.0] /readyz URL not working anymore

[Ostantia]

LocalAI version: 3.8.0

Environment, CPU architecture, OS, and Version: Docker on Linux, multiple AMD CPUs, different servers all on Ubuntu

Describe the bug

Since updating vrom v3.7.0 to 3.8.0, the /readyz URL is not working (not as the healthcheck on this page of the docs mentions it inside the docker compose config : https://localai.io/basics/container/ (which makes the container unhealthy all the time) or from my external uptime supervision using Uptime Kuma) On previous versions the result is "OK" even without authenticating because it's for the supervision of the container. On v3.8.0 the code is 401 unauthorized.

To Reproduce

Upgrade to version 3.8.0 and try to get without auth to /readyz on your localai instance.

Expected behavior

The access without auth should be granted and the result "OK" should appear for the supervision to tell that the container is up and running.

Logs

Localai container logs : (First line is me on a web browser while authenticated trying to see the "OK" page, but got nothing, second is uptime kuma, unauthenticated, getting 401)

private-localai-container  | 4:31PM INF HTTP request method=GET path=/readyz status=200
private-localai-container  | 4:32PM INF HTTP request method=GET path=/readyz status=401

Additional context

If it was intended to be this way then it's okay, I'll change my supervision, but the most problematic thing is that it also affects the container healthcheck that is still mentionned in the latest docs, but doesn't work with the latest version and keeps marking the container as unhealthy (https://localai.io/basics/container/) :

healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8080/readyz"]
      interval: 1m
      timeout: 20m
      retries: 5

[brknkfr]

We experience the same with the /healthz endpoint.