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

Public access URL request error（400） #12629

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

Originally created by @hybIsVeryCool on GitHub (Apr 7, 2025).

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I modified the port of nginx and encountered an error when accessing the URL
Image

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @hybIsVeryCool on GitHub (Apr 7, 2025). ### 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.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I modified the port of nginx and encountered an error when accessing the URL ![Image](https://github.com/user-attachments/assets/84b419c7-3e78-4702-b205-0491b4cfd8be) ![Image](https://github.com/user-attachments/assets/1a210b73-c1e2-43d5-976d-cc856da68cf2) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 19:08:17 -05:00
yindo commented 2026-02-21 19:08:17 -05:00
Author
Owner
Copy Link
Copy Source

@hybIsVeryCool commented on GitHub (Apr 7, 2025):

Image

@hybIsVeryCool commented on GitHub (Apr 7, 2025): ![Image](https://github.com/user-attachments/assets/40d2cb8c-efe3-4d20-a3c6-a147d9a19206)
yindo commented 2026-02-21 19:08:17 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 7, 2025):

I found a similar open issue titled "Public access URL 404 application unavailable" that might be relevant to your situation. The suggested solution includes several steps:

  1. Confirm that the app is published and the app ID is correct. Check the admin panel to ensure the app is set to public and the access URL is correct.
  2. Verify that the web container or frontend service is running using commands like kubectl get pods and kubectl logs to check the status and logs of the web/frontend pod. Ensure the service is exposing the /chat route.
  3. If using an Ingress controller, make sure the rules for /chat/* are correctly forwarding to the frontend service. Check the YAML configuration to verify the path and backend service settings.
  4. Use kubectl port-forward to forward the service port and test accessing the application directly. If this works, the issue likely lies in the ingress or reverse proxy configuration.
  5. Ensure that the URL is not set to "udify.app" as this is the production cloud domain name. Configure the URL to point to your local or self-hosted environment instead [1].

Additionally, common causes of a 400 status code in the Dify platform when accessing the '/api/parameters' endpoint include:

  • AppUnavailableError: The app is unavailable, and you need to check your app configurations.
  • ProviderNotInitializeError: No valid model provider credentials are found, requiring completion of provider credentials in settings.
  • ProviderQuotaExceededError: The quota for Dify Hosted OpenAI has been exhausted, requiring completion of provider credentials in settings.
  • ProviderModelCurrentlyNotSupportError: The Dify Hosted OpenAI trial does not support the GPT-4 model [2].

Review these potential causes and solutions to address the 400 status code error you're encountering.

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 (Apr 7, 2025): <!-- Answer --> I found a similar open issue titled "Public access URL 404 application unavailable" that might be relevant to your situation. The suggested solution includes several steps: 1. Confirm that the app is published and the app ID is correct. Check the admin panel to ensure the app is set to public and the access URL is correct. 2. Verify that the web container or frontend service is running using commands like `kubectl get pods` and `kubectl logs` to check the status and logs of the web/frontend pod. Ensure the service is exposing the `/chat` route. 3. If using an Ingress controller, make sure the rules for `/chat/*` are correctly forwarding to the frontend service. Check the YAML configuration to verify the path and backend service settings. 4. Use `kubectl port-forward` to forward the service port and test accessing the application directly. If this works, the issue likely lies in the ingress or reverse proxy configuration. 5. Ensure that the URL is not set to "udify.app" as this is the production cloud domain name. Configure the URL to point to your local or self-hosted environment instead <sup>[[1]](https://github.com/langgenius/dify/issues/17569)</sup>. Additionally, common causes of a 400 status code in the Dify platform when accessing the '/api/parameters' endpoint include: - **AppUnavailableError**: The app is unavailable, and you need to check your app configurations. - **ProviderNotInitializeError**: No valid model provider credentials are found, requiring completion of provider credentials in settings. - **ProviderQuotaExceededError**: The quota for Dify Hosted OpenAI has been exhausted, requiring completion of provider credentials in settings. - **ProviderModelCurrentlyNotSupportError**: The Dify Hosted OpenAI trial does not support the GPT-4 model <sup>[[2]](https://github.com/langgenius/dify/blob/main/api/controllers/service_api/app/error.py)</sup>. Review these potential causes and solutions to address the 400 status code error you're encountering. <!-- 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/8b5214c7-1edd-40f5-9114-a845d9bead7b?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/8b5214c7-1edd-40f5-9114-a845d9bead7b?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/8b5214c7-1edd-40f5-9114-a845d9bead7b?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/8b5214c7-1edd-40f5-9114-a845d9bead7b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/8b5214c7-1edd-40f5-9114-a845d9bead7b?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/8b5214c7-1edd-40f5-9114-a845d9bead7b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/8b5214c7-1edd-40f5-9114-a845d9bead7b?feedback_type=other)</sup>
yindo commented 2026-02-21 19:08:17 -05:00
Author
Owner
Copy Link
Copy Source

@hybIsVeryCool commented on GitHub (Apr 7, 2025):

I don't know why I accessed 400, but all other applications I created were accessed normally, except for my own application

@hybIsVeryCool commented on GitHub (Apr 7, 2025): I don't know why I accessed 400, but all other applications I created were accessed normally, except for my own application
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#12629
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?