Troubleshooting¶
The client cannot connect¶
health()returnshealthy: false, status: "unreachable": the URL is wrong or the service is down. CheckGROW_GRAYLOG_URL(defaulthttp://127.0.0.1:9000) and that the port is reachable from where your code runs (inside Docker,127.0.0.1is the container itself).
- Calls fail with
UNAVAILABLEafter several seconds: the client retried with backoff. LowermaxRetriesortotalTimeoutto fail faster. - Behind a corporate proxy:
HTTP_PROXY/HTTPS_PROXYare ignored on purpose. Setproxy(orGROW_GRAYLOG_PROXY).
CONFIG errors¶
The message names the setting or environment variable, never its value. Typical causes: a URL
without http:// or https://, a duration such as 10 sec (use 10s or 10000), a client
certificate without its key, MAX_RETRIES below 0.
AUTHENTICATION or PERMISSION_DENIED¶
ping()is the quickest credential check: it makes one authenticated call.
- Make sure the credential variables are the ones this SDK reads:
GROW_GRAYLOG_API_TOKEN(orGRAYLOG_API_TOKEN), orGROW_GRAYLOG_USER+GROW_GRAYLOG_PASSWORD(orGRAYLOG_USER+GRAYLOG_PASSWORD); see Graylog settings. An API token wins over user/password, and explicit config values win over the environment. - An API token is sent as HTTP Basic
<token>:token; a token created for another Graylog user only has that user's permissions.
- The SDK never prints credentials, so
toString()of the config shows[REDACTED]even when a credential is set.
TLS errors¶
- Self-signed or private CA: set
tls.caCertPath(GROW_GRAYLOG_CA_CERT). - Mutual TLS: set both
tls.clientCertPathandtls.clientKeyPath. tls.insecureSkipVerifyonly for local tests.
RATE_LIMITED¶
The service asked the client to slow down. The client waits for Retry-After up to
maxRetryAfter (60 s); longer waits fail at once with retryAfter set on the error so your code
can schedule a later attempt.
TIMEOUT¶
requestTimeout (30 s) bounds one attempt and totalTimeout (120 s) the whole call including
retries. Raise them for slow operations, or pass a per-call deadline (signal, ctx, cancel token,
future timeout).
See what the client does¶
Turn on the logger or add hooks: both see every attempt with redacted headers and URLs.
Docker integration tests fail¶
- Run one language:
make test-docker LANGS=go. - In CI, download the
compose-logs-<lang>artifact of the failed job. - Locally, the stack is removed after each run; rerun with Docker logs open
(
docker compose -f docker/compose.yml logs -f) in a second terminal.
Still stuck?¶
Open an issue with the language, package version, Graylog Open version and a minimal reproduction (with secrets removed): https://github.com/grow-codes-packages/graylog/issues.