‌‌‌‌‌OpenRouter, o1-mini and o1-preview error

langgenius / dify

Dify is an open-source LLM app development platform. Dify's intuitive interface combines AI workflow, RAG pipeline, agent capabilities, model management, observability features and more, letting you quickly go from prototype to production.

Other

50.82k stars 7.31k forks source link

Self Checks

[X] This is only for bug report, if you would like to ask a question, please head to Discussions.
[X] I have searched for existing issues search for existing issues, including closed ones.
[X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
[X] Please do not modify this template :) and fill in all the required fields.

Dify version

0.10.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Add openrouter API
Choose o1-mini on agent chat
Chat

Errors only happen with o1-mini and o1-preview

✔️ Expected Behavior

‌‌‌‌No error, Agent can run normally

❌ Actual Behavior

[openrouter] Error: 'choices'

Hey there, @KienVu2368! I'm here to help you with any bugs, questions, or contributions you may have regarding Dify. I'll do my best to assist you while we wait for a human maintainer to jump in. Let's tackle this together!

I couldn't find specific information about the 'choices' error in the Dify codebase when using the o1-mini and o1-preview models. However, there are some related discussions and issues that might be helpful:

A similar issue was discussed regarding a 404 error when using the o1-preview model in a self-hosted Docker setup. The solution involved ensuring that the Ollama service is accessible from the Docker container by using host.docker.internal instead of localhost in the service URL ^[1].
There is also a related unsolved discussion about a connection error with status code 503, which might provide some insights into network-related issues ^[2].

For the 'choices' error, it might be beneficial to check the network configurations and ensure that all services are correctly exposed and accessible within your Docker setup. Additionally, reviewing the logs for any specific error messages related to the 'choices' error could provide more clues.

To continue talking to Dosu, mention @dosu.

langgenius / dify