9. FAQ

1. "coze-elasticsearch" container fails to start during deployment?

If the following error occurs during the deployment process:

Open docker/volumes/elasticsearch/setup_es.sh in a code editor (like VS Code). In the bottom-right corner of the editor, you will see a CRLF or LF indicator. Click it and select LF. Save the file and restart docker compose --profile '*' up -d. See also the related issue.

2. "Error response from daemon: Ports are not available: exposing port TCP http://0.0.0.0:2379 -＞ http://127.0.0.1:0" when deploying locally on Windows?

# Check port usage
netstat -ano | findstr :2379

net stop winnat
net start winnat

3. "Something error: Internal server error" during Agent conversation debugging?

You can query the specific error logs with the following command:

docker logs coze-server | grep -i 'node execute failed'

4. After uploading a document to the knowledge base, it shows "Processing 0%"?

After uploading a document to the knowledge base, it remains in the 'Processing' state for a long time, as shown in the image below: The knowledge base feature relies on the vector storage component and the Embedding model. Please check if the corresponding configurations are set up correctly. For the configuration process, refer to: Vectorized storage and Vectorization model.

5. Why does the model report an error after uploading an image/file during an Agent conversation or workflow debugging?

The image/file links accessed by the large model must be publicly accessible URLs. The upload component needs to be deployed on a public network. For details, please refer to: Upload Component Configuration

6. Is it normal for "setup" related containers to be in an exited state after the service starts?

Yes, this is normal. The setup-related containers perform script initialization tasks and will automatically exit once they are complete.