#FAQ

#Startup and connectivity

The container is running but I cannot reach it. Confirm the port is mapped to 8801 and that curl http://localhost:8801/api/status returns JSON on the host. JSON back means the service itself is fine and the problem is the firewall or the reverse proxy.

The log reports a database connection failure. Check the username, password, database name, and network reachability in SQL_DSN. Inside a container, localhost is the container itself; reaching a database on the host needs the host address or the service name on the container network.

Rate limiting and caching behave inconsistently across replicas. Replicas must share one Redis instance and one database. Only the master applies schema changes and runs scheduled jobs; start the others with NODE_TYPE=slave.

#Requests and responses

Streamed responses get cut off. The ingress layer is buffering SSE. Disable response buffering and raise read timeouts to minutes.

The upstream reports an authentication failure. A channel holds the provider's real key while clients use a Geekit token; the two are not interchangeable. Check the key and base URL in the channel configuration.

A model name with a -high or -thinking suffix reports "model not found". Those suffixes are parsed by the gateway. The corresponding base model name must be present in the channel's model list.

#Billing

The quota deduction does not match what I expected. The log carries the billing detail for each request, separating input, output, cache-hit, and reasoning tokens before applying channel ratios. Read that log entry first, then check the channel ratio configuration.

If a request fails after pre-consumption, is the quota returned? Yes. When a request fails or actual usage is below the pre-consumed amount, the difference is refunded at settlement.

#Data

Can I edit values in the database directly? No. Persisted data that needs fixing is corrected with a new versioned revision under migration/. A hand edit does not propagate to other environments and cannot be reviewed.

Can I migrate from One API? Yes, the database is fully compatible. Back up first; unapplied revisions replay automatically at startup.

#Still stuck

See Community and include the version, deployment method, database type, and the relevant log excerpt.