Skip to content

Troubleshooting

HTTP 401

Cause: the credential does not match this instance, or the client is not trusting this instance's certificate.

Fix: use sushi-mem0-api so it reads access.json and server.crt. If you added another user, pass that user's file with --profile. Do not print the file.

HTTP 400 or 404

Cause: the JSON is invalid, the text length is outside 1 to 8,000 characters, or the memory id or route does not exist.

Fix: correct the body file and retry. GET /memories lists what this user has stored.

HTTP 429

Cause: another operation is still running. The service handles one operation at a time.

Fix: wait for it to finish, then send the next call.

HTTP 503

Cause: no provider is configured. Health shows provider_configured: false.

Fix: run the provider setup in Getting started. The output file for provider-setup.py must not already exist.

HTTP 502

Cause: the provider or local storage call failed. A failed add can leave partial upstream work.

Fix: check the provider URL, credential, model, dimensions, quota, and free disk. List memories before you retry an add, so you do not store a duplicate. Remote providers must be HTTPS. A change of embedding model is refused once vectors exist. The adapter does not migrate them.

Last updated November 11, 2026 · Suggest an improvement