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

Application deployment error #12133

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

Originally created by @duzengjie on GitHub (Mar 25, 2025).

Originally assigned to: @crazywoola on GitHub.

Self Checks

  • 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 (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

Error occurred when clicking the publish button.
No obvious errors found in the logs for now.

This is the response message returned by the API after clicking the button.

{
  "code": "bad_request",
  "message": "The browser (or proxy) sent a request that this server could not understand.",
  "status": 400
}

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @duzengjie on GitHub (Mar 25, 2025). Originally assigned to: @crazywoola on GitHub. ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.1.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="1098" alt="Image" src="https://github.com/user-attachments/assets/1da264de-1592-4976-b4bd-2db77d731a23" /> Error occurred when clicking the publish button. No obvious errors found in the logs for now. This is the response message returned by the API after clicking the button. ```json { "code": "bad_request", "message": "The browser (or proxy) sent a request that this server could not understand.", "status": 400 } ``` ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 19:05:56 -05:00
yindo closed this issue 2026-02-21 19:05:56 -05:00
yindo commented 2026-02-21 19:05:57 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 25, 2025):

Hey @duzengjie, I'm here to help you with bug fixes, answer your questions, and guide you as a contributor. Let's squash those bugs together! 🤖

I found a similar open issue related to the error message "The browser (or proxy) sent a request that this server could not understand" when using Dify version 1.1.0 in a self-hosted Docker environment. The suggested solution is to ensure that the request to publish a workflow includes the correct "Content-Type" header set to "application/json" and that the JSON payload is properly formatted. Additionally, make sure the request includes the Authorization header with your API-Key:

Authorization: Bearer {API_KEY}
Content-Type: application/json

If the issue persists, you may need to investigate further into the request handling and any proxy configurations that might be affecting the request [1].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 25, 2025): <!-- Greeting --> Hey @duzengjie, I'm here to help you with bug fixes, answer your questions, and guide you as a contributor. Let's squash those bugs together! 🤖 <!-- Answer --> I found a similar open issue related to the error message "The browser (or proxy) sent a request that this server could not understand" when using Dify version 1.1.0 in a self-hosted Docker environment. The suggested solution is to ensure that the request to publish a workflow includes the correct "Content-Type" header set to "application/json" and that the JSON payload is properly formatted. Additionally, make sure the request includes the `Authorization` header with your `API-Key`: ```javascript Authorization: Bearer {API_KEY} Content-Type: application/json ``` If the issue persists, you may need to investigate further into the request handling and any proxy configurations that might be affecting the request <sup>[[1]](https://github.com/langgenius/dify/issues/16263)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/be743764-7cbd-4815-ae84-d987968aa4e2?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/be743764-7cbd-4815-ae84-d987968aa4e2?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/be743764-7cbd-4815-ae84-d987968aa4e2?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/be743764-7cbd-4815-ae84-d987968aa4e2?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/be743764-7cbd-4815-ae84-d987968aa4e2?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/be743764-7cbd-4815-ae84-d987968aa4e2?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/be743764-7cbd-4815-ae84-d987968aa4e2?feedback_type=other)</sup>
yindo commented 2026-02-21 19:05:57 -05:00
Author
Owner
Copy Link
Copy Source

@duzengjie commented on GitHub (Mar 25, 2025):

This is an error caused by a page operation, not an API call error.

@duzengjie commented on GitHub (Mar 25, 2025): This is an error caused by a page operation, not an API call error.
yindo commented 2026-02-21 19:05:57 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 25, 2025):

https://github.com/langgenius/dify/blob/6157f57872908238845f3ba65d3c17bfa6e25e41/docker/.env.example#L1-L42

Try to add http or https in these urls.

@crazywoola commented on GitHub (Mar 25, 2025): https://github.com/langgenius/dify/blob/6157f57872908238845f3ba65d3c17bfa6e25e41/docker/.env.example#L1-L42 Try to add http or https in these urls.
yindo commented 2026-02-21 19:05:57 -05:00
Author
Owner
Copy Link
Copy Source

@duzengjie commented on GitHub (Mar 25, 2025):

Image

I have already made the modifications, but it still doesn't work. This ubuntu is the host I configured locally, and Docker is running on another machine.

If this configuration is incorrect, other interfaces shouldn't be accessible either, right?

@duzengjie commented on GitHub (Mar 25, 2025): <img width="655" alt="Image" src="https://github.com/user-attachments/assets/814787a8-3650-45e1-b070-592ed0f0fc04" /> I have already made the modifications, but it still doesn't work. This ubuntu is the host I configured locally, and Docker is running on another machine. If this configuration is incorrect, other interfaces shouldn't be accessible either, right?
yindo commented 2026-02-21 19:05:57 -05:00
Author
Owner
Copy Link
Copy Source

@duzengjie commented on GitHub (Mar 26, 2025):

I used an API call locally, and it worked successfully after adding a body.

Image

It is already in the released state.
Image

@duzengjie commented on GitHub (Mar 26, 2025): I used an API call locally, and it worked successfully after adding a body. ![Image](https://github.com/user-attachments/assets/b1785f88-db19-4e30-9af6-5c39f4d45ac4) It is already in the released state. ![Image](https://github.com/user-attachments/assets/4f457060-09cd-4185-840e-a5fd6922079a)
yindo commented 2026-02-21 19:05:57 -05:00
Author
Owner
Copy Link
Copy Source

@duzengjie commented on GitHub (Mar 26, 2025):

docker dify

Image

cloud dify

Image

@duzengjie commented on GitHub (Mar 26, 2025): # docker dify ![Image](https://github.com/user-attachments/assets/eb3a8eeb-105b-4c35-bd6b-9f8dfd332ef2) # cloud dify ![Image](https://github.com/user-attachments/assets/7aad942d-05cb-4a2e-9cab-3ecf18241b49)
yindo commented 2026-02-21 19:05:57 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Apr 10, 2025):

I think this should be fixed in latest 1.2.0

@crazywoola commented on GitHub (Apr 10, 2025): I think this should be fixed in latest 1.2.0
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 🤔 cant-reproduce
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#12133
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?