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

Credentials validation failed: JSON decode error, response body #16702

New Issue
Closed
opened 2026-02-21 19:27:14 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 19:27:14 -05:00
Owner
Copy Link
Copy Source

Originally created by @hongwei366 on GitHub (Sep 3, 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.8.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

when add new model, interace error, raise "Credentials validation failed: JSON decode error, response body"
Image

Image

✔️ Expected Behavior

how to work out this problem

❌ Actual Behavior

No response

Originally created by @hongwei366 on GitHub (Sep 3, 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.8.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce when add new model, interace error, raise "Credentials validation failed: JSON decode error, response body" <img width="635" height="673" alt="Image" src="https://github.com/user-attachments/assets/8197f539-b72e-4d4f-b6c3-6f38faf11927" /> <img width="362" height="641" alt="Image" src="https://github.com/user-attachments/assets/9002876e-9910-4f25-ba04-5575326109a3" /> ### ✔️ Expected Behavior how to work out this problem ### ❌ Actual Behavior _No response_
yindo added the 🌚 invalid label 2026-02-21 19:27:14 -05:00
yindo closed this issue 2026-02-21 19:27:14 -05:00
yindo commented 2026-02-21 19:27:14 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 3, 2025):

Hi @hongwei366! I'm Dosu and I’m helping the dify team.

This error happens because Dify expects the model provider's API endpoint to return a valid JSON response, but it's getting something else—usually an HTML error page or plain text. This often means the endpoint URL is incorrect, the API key is invalid, or the provider isn't fully OpenAI-compatible.

Here’s how you can troubleshoot:

  • Double-check that the endpoint (https://vip.dmxapi.com) is correct and reachable from inside your Docker container.
  • Make sure your API key is valid and has the right permissions.
  • Confirm the model name (gpt-4o-mini) matches exactly what your provider expects—some providers require a prefix or specific naming format (e.g., qwen/Qwen2.5-32B instead of just Qwen2.5-32B) example.
  • The provider must return a JSON response that matches the OpenAI API spec. If it returns HTML or a non-JSON error, Dify will throw a JSON decode error details.
  • Check your Dify backend logs for more details about the failed request.
  • Try calling the endpoint manually (e.g., with curl) from inside the Docker container to see the raw response.
  • If possible, test with a known working OpenAI-compatible endpoint to isolate whether the issue is with Dify or the external provider.

If the endpoint is not truly OpenAI-compatible or always returns HTML, you’ll need to contact the provider or use a supported integration.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Sep 3, 2025): <!-- Greeting --> Hi @hongwei366! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This error happens because Dify expects the model provider's API endpoint to return a valid JSON response, but it's getting something else—usually an HTML error page or plain text. This often means the endpoint URL is incorrect, the API key is invalid, or the provider isn't fully OpenAI-compatible. Here’s how you can troubleshoot: - Double-check that the endpoint (`https://vip.dmxapi.com`) is correct and reachable from inside your Docker container. - Make sure your API key is valid and has the right permissions. - Confirm the model name (`gpt-4o-mini`) matches exactly what your provider expects—some providers require a prefix or specific naming format (e.g., `qwen/Qwen2.5-32B` instead of just `Qwen2.5-32B`) [example](https://github.com/langgenius/dify-official-plugins/issues/706). - The provider must return a JSON response that matches the OpenAI API spec. If it returns HTML or a non-JSON error, Dify will throw a JSON decode error [details](https://github.com/langgenius/dify/pull/23456). - Check your Dify backend logs for more details about the failed request. - Try calling the endpoint manually (e.g., with `curl`) from inside the Docker container to see the raw response. - If possible, test with a known working OpenAI-compatible endpoint to isolate whether the issue is with Dify or the external provider. If the endpoint is not truly OpenAI-compatible or always returns HTML, you’ll need to contact the provider or use a supported integration. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/02b03be7-771b-4873-821d-f7c607014cee?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/02b03be7-771b-4873-821d-f7c607014cee?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/02b03be7-771b-4873-821d-f7c607014cee?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/02b03be7-771b-4873-821d-f7c607014cee?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/02b03be7-771b-4873-821d-f7c607014cee?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/02b03be7-771b-4873-821d-f7c607014cee?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/02b03be7-771b-4873-821d-f7c607014cee?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/25088)
yindo commented 2026-02-21 19:27:14 -05:00
Author
Owner
Copy Link
Copy Source

@hjlarry commented on GitHub (Sep 3, 2025):

please update to v1.8.1 and try again

@hjlarry commented on GitHub (Sep 3, 2025): please update to v1.8.1 and try again
yindo commented 2026-02-21 19:27:14 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Sep 3, 2025):

We will not return error messages like this.

@crazywoola commented on GitHub (Sep 3, 2025): We will not return error messages like this.
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 🌚 invalid
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#16702
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?