Startup failed#
Self Hosted
When the web app cannot load what it needs, it shows a Startup failed dialog. The dialog lists the failed step, a short diagnosis, what to do next and the API address the page is using. This page explains each diagnosis.
Fix the cause, then use Check again or reload the page. Dismiss closes the dialog without fixing anything.
How the check works#
Check again looks at the failed request first, then asks the web server and the API:
GET /healthon the address of the page. It only answers that the service is running and does not contact the database.GET /api/system/health. It needs no key and returnsdatabaseOkandredisOk.
curl http://localhost:8000/api/system/health
Replace the address with the one your page uses. A response such as
{"status": "ok", "databaseOk": true, "redisOk": true} means the API can use
both. The commands below assume the Docker compose install; use your own
service names otherwise.
What each diagnosis means#
A failed request is shown with its method, path, status and request id. Include the request id when you search the logs or report a problem.
Diagnosis |
What to check |
|---|---|
Cannot reach the BrewGraph web server |
The host is not running, or the address, port or HTTPS certificate is
wrong. Run |
The request failed, but the web server answers now |
The failure was probably temporary. Reload. If it returns, read the logs
of |
The browser blocked or could not reach the API address |
The API address differs from the page address. Check
|
The web server is up but the API is not answering |
The answer was |
The API is running but cannot use the database |
|
The API hit an internal error |
The answer was |
The API rejected the API key |
The answer was |
The page has no API key |
|
Too many failed attempts |
The answer was |
The API refused the request |
Any other status. Read the message in the dialog and the API log for the request id. |
Startup failed for an unknown reason |
No failed request was recorded. Reload. If it persists, check the browser console and the API log. |
Redis#
redisOk: false means the API cannot reach Redis. Check that the Redis
service is running and that the API service is configured with its address.