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

400 BAD_REQUEST #21918

New Issue
Closed
opened 2026-02-21 20:14:51 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 20:14:51 -05:00
Owner
Copy Link
Copy Source

Originally created by @XiaoYueTan on GitHub (Jan 26, 2026).

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.11.4

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When dify's version was updated from 1.10.1 to 1.11.4, an error occurred when the original api interface was called Dify API Error [400 BAD_REQUEST] {"code":"invalid_param","message":"1 validation error for ChatRequestPayload\nauto_generate_name\n Input should be a valid boolean [type=bool_type, input_value=None, input_type=NoneType]\n For further information visit https://errors.pydantic.dev/2.11/v/bool_type","status":400}
I've checked the interface content of the api and it seems there's nothing wrong. What's going on

And there's the problem in this picture. Why can't this container be started

Image

✔️ Expected Behavior

It is hoped that the incorrect container can be started and the api interface can be accessed normally

❌ Actual Behavior

No response

Originally created by @XiaoYueTan on GitHub (Jan 26, 2026). ### 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.11.4 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When dify's version was updated from 1.10.1 to 1.11.4, an error occurred when the original api interface was called Dify API Error [400 BAD_REQUEST] {"code":"invalid_param","message":"1 validation error for ChatRequestPayload\nauto_generate_name\n Input should be a valid boolean [type=bool_type, input_value=None, input_type=NoneType]\n For further information visit https://errors.pydantic.dev/2.11/v/bool_type","status":400} I've checked the interface content of the api and it seems there's nothing wrong. What's going on And there's the problem in this picture. Why can't this container be started <img width="1748" height="136" alt="Image" src="https://github.com/user-attachments/assets/0e9cd8a0-2426-4a9b-b13e-02fae1a729c4" /> ### ✔️ Expected Behavior It is hoped that the incorrect container can be started and the api interface can be accessed normally ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 20:14:51 -05:00
yindo closed this issue 2026-02-21 20:14:51 -05:00
yindo commented 2026-02-21 20:14:51 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 26, 2026):

The 400 BAD_REQUEST error is caused by the API receiving auto_generate_name as null/None, which is not valid in Dify 1.11.4. The new version enforces strict boolean validation: auto_generate_name must be true or false, or omitted (it defaults to true if not provided). To fix this, make sure your API payload either omits auto_generate_name or sets it explicitly to true or false—never null or None. For example:

{
  "query": "your message",
  "inputs": {},
  "auto_generate_name": false
}

or simply omit the field if you want the default behavior. See API schema update and validation logic for details.

For the container startup issue, common causes after an upgrade include misconfigured environment variables, Docker network problems, or missing dependencies. Check your Docker Compose and .env files for correct settings, especially network-related variables like CLUSTER_HOSTNAME or WEAVIATE_CLUSTER_HOSTNAME. Review the container logs for errors such as "No private IP address found, and explicit IP not provided"—this often points to a Docker network misconfiguration. You may need to set explicit IP addresses, adjust Docker network mode, or ensure your pod subnet is within a valid range (e.g., 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16). More troubleshooting steps are described here.

If the container still won't start, please provide the exact error logs from the failing container for more targeted help.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 26, 2026): <!-- Answer --> The 400 BAD_REQUEST error is caused by the API receiving auto_generate_name as null/None, which is not valid in Dify 1.11.4. The new version enforces strict boolean validation: auto_generate_name must be true or false, or omitted (it defaults to true if not provided). To fix this, make sure your API payload either omits auto_generate_name or sets it explicitly to true or false—never null or None. For example: ```json { "query": "your message", "inputs": {}, "auto_generate_name": false } ``` or simply omit the field if you want the default behavior. See [API schema update](https://github.com/langgenius/dify/pull/24715) and [validation logic](https://github.com/langgenius/dify/pull/29855) for details. For the container startup issue, common causes after an upgrade include misconfigured environment variables, Docker network problems, or missing dependencies. Check your Docker Compose and .env files for correct settings, especially network-related variables like CLUSTER_HOSTNAME or WEAVIATE_CLUSTER_HOSTNAME. Review the container logs for errors such as "No private IP address found, and explicit IP not provided"—this often points to a Docker network misconfiguration. You may need to set explicit IP addresses, adjust Docker network mode, or ensure your pod subnet is within a valid range (e.g., 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16). More troubleshooting steps are described [here](https://github.com/langgenius/dify/issues/14313). If the container still won't start, please provide the exact error logs from the failing container for more targeted help. <!-- 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/3eed807e-7bfd-4ab8-ab95-50e4d0853f59?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/3eed807e-7bfd-4ab8-ab95-50e4d0853f59?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/3eed807e-7bfd-4ab8-ab95-50e4d0853f59?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/3eed807e-7bfd-4ab8-ab95-50e4d0853f59?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/3eed807e-7bfd-4ab8-ab95-50e4d0853f59?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/3eed807e-7bfd-4ab8-ab95-50e4d0853f59?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/3eed807e-7bfd-4ab8-ab95-50e4d0853f59?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20400%20BAD_REQUEST%20error%20is%20caused%20by%20the%20API%20receiving%20auto_generate_name%20as%20null/None%2C%20which%20is%20not%20valid%20in%20Dify%201.11.4.%20The%20new%20version%20enforces%20strict%20boolean%20validation%3A%20auto_generate_name%20must%20be%20true%20or%20false%2C%20or%20omitted%20%28it%20defaults%20to%20true%20if%20not%20provided%29.%20To%20fix%20this%2C%20make%20sure%20your%20API%20payload%20either%20omits%20auto_generate_name%20or%20sets%20it%20explicitly%20to%20true%20or%20false%E2%80%94never%20null%20or%20None.%20For%20example%3A%0A%0A%60%60%60json%0A%7B%0A%20%20%22query%22%3A%20%22your%20message%22%2C%0A%20%20%22inputs%22%3A%20%7B%7D%2C%0A%20%20%22auto_generate_name%22%3A%20false%0A%7D%0A%60%60%60%0Aor%20simply%20omit%20the%20field%20if%20you%20want%20the%20default%20behavior.%20See%20%5BAPI%20schema%20update%5D%28https%3A//github.com/langgenius/dify/pull/24715%29%20and%20%5Bvalidation%20logic%5D%28https%3A//github.com/langgenius/dify/pull/29855%29%20for%20details.%0A%0AFor%20the%20container%20startup%20issue%2C%20common%20causes%20after%20an%20upgrade%20include%20misconfigured%20environment%20variables%2C%20Docker%20network%20problems%2C%20or%20missing%20dependencies.%20Check%20your%20Docker%20Compose%20and%20.env%20files%20for%20correct%20settings%2C%20especially%20network-related%20variables%20like%20CLUSTER_HOSTNAME%20or%20WEAVIATE_CLUSTER_HOSTNAME.%20Review%20the%20container%20logs%20for%20errors%20such%20as%20%22No%20private%20IP%20address%20found%2C%20and%20explicit%20IP%20not%20provided%22%E2%80%94this%20often%20points%20to%20a%20Docker%20network%20misconfiguration.%20You%20may%20need%20to%20set%20explicit%20IP%20addresses%2C%20adjust%20Docker%20network%20mode%2C%20or%20ensure%20your%20pod%20subnet%20is%20within%20a%20valid%20range%20%28e.g.%2C%2010.0.0.0/8%2C%20172.16.0.0/12%2C%20192.168.0.0/16%29.%20More%20troubleshooting%20steps%20are%20described%20%5Bhere%5D%28https%3A//github.com/langgenius/dify/issues/14313%29.%0A%0AIf%20the%20container%20still%20won%27t%20start%2C%20please%20provide%20the%20exact%20error%20logs%20from%20the%20failing%20container%20for%20more%20targeted%20help.)&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/31581)
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 🐞 bug
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#21918
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?