langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

vllm provider fails with 404 error, but curl from inside the API container succeeds #18237

New Issue
Closed
opened 2026-02-21 19:45:16 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 19:45:16 -05:00
Owner
Copy Link
Copy Source

Originally created by @saraoncloud95 on GitHub (Sep 25, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.9.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Steps to reproduce*
Deploy Dify v1.9.0 using the standard Docker Compose method.

Set up a self-hosted OpenAI-compatible model endpoint (in our case, using vLLM to serve a DeepSeek model).

In the Dify UI, navigate to Settings -> Model Provider.

Click to add a new model under the vllm provider.

Enter the correct API endpoint URL and model name for API endpoint.

Click the "Add" button.

✔️ Expected Behavior

The model provider should be added successfully without any errors.

❌ Actual Behavior

The UI immediately displays an error notification: "Credentials validation failed with status code 404". The model provider cannot be saved.

Important Additional Context:
We have performed extensive troubleshooting and have confirmed this is not a user configuration or network issue.

A curl request to the model's /v1/models endpoint works perfectly when executed from inside the Dify API container.

Command: docker exec -it <dify_api_container> curl http://<model_server_ip>:/v1/models

This definitive test proves there are no firewall, DNS, or Docker networking problems.

The issue persisted even after a full, clean reset of the Dify application (docker-compose down --volumes) and a successful upgrade from version 0.6.0 to 1.9.0.

Originally created by @saraoncloud95 on GitHub (Sep 25, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.9.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Steps to reproduce* Deploy Dify v1.9.0 using the standard Docker Compose method. Set up a self-hosted OpenAI-compatible model endpoint (in our case, using vLLM to serve a DeepSeek model). In the Dify UI, navigate to Settings -> Model Provider. Click to add a new model under the vllm provider. Enter the correct API endpoint URL and model name for API endpoint. Click the "Add" button. ### ✔️ Expected Behavior The model provider should be added successfully without any errors. ### ❌ Actual Behavior The UI immediately displays an error notification: "Credentials validation failed with status code 404". The model provider cannot be saved. Important Additional Context: We have performed extensive troubleshooting and have confirmed this is not a user configuration or network issue. A curl request to the model's /v1/models endpoint works perfectly when executed from inside the Dify API container. Command: docker exec -it <dify_api_container> curl http://<model_server_ip>:<port>/v1/models This definitive test proves there are no firewall, DNS, or Docker networking problems. The issue persisted even after a full, clean reset of the Dify application (docker-compose down --volumes) and a successful upgrade from version 0.6.0 to 1.9.0.
yindo closed this issue 2026-02-21 19:45:16 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#18237
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?