Troubleshooting¶
Common problems with AnythingLLM, what causes them and how to fix them.
The UI does not load¶
Cause: the port-forwarding session is not running, or AnythingLLM is still starting.
Fix: start the session again with portNumber and localPortNumber set
to 3001, then check on the instance:
The password is refused¶
Cause: the password does not match AUTH_TOKEN in
/etc/anythingllm/server.env, for example after only one of the two files
was changed.
Fix: set both files again, see Change the admin password.
The workspace does not do plain document Q&A¶
Cause: new workspaces start in automatic (agent) mode.
Fix: in the workspace settings, set the chat mode to Chat.
Bedrock does not work with the instance role¶
Cause: the built-in AWS Bedrock provider uses access keys, not the instance's IAM role.
Fix: use Generic OpenAI with the Bedrock OpenAI-compatible endpoint and a Bedrock API key, see Connect a model.
The model or embedding provider returns errors¶
Cause: the key or model name is wrong, or the instance cannot reach the provider over outbound HTTPS.
Fix: check the provider settings, the security group's outbound rules and the log:
The service does not start¶
Cause: server.env or admin.password is missing, empty, or no longer
owned by root:root with mode 0600. The service checks both before it starts
the container.
Fix: read the reason, restore the files and their permissions, then restart:
sudo journalctl -u anythingllm -n 50 --no-pager
sudo chown root:root /etc/anythingllm/server.env /etc/anythingllm/admin.password
sudo chmod 0600 /etc/anythingllm/server.env /etc/anythingllm/admin.password
sudo systemctl restart anythingllm
The disk fills up¶
Cause: documents and vectors grow with use.
Fix: remove documents you no longer need in the UI, or grow the EBS volume and the file system.
If it still fails, contact info@softwaresushi.com.
Last updated October 13, 2026 · Suggest an improvement