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

Dify deployment on an intranet (no external network access), encountering an error when creating an agent. #8869

New Issue
Closed
opened 2026-02-21 18:28:16 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:28:16 -05:00
Owner
Copy Link
Copy Source

Originally created by @OneChainTech on GitHub (Mar 2, 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

0.15.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Deploying Dify on an intranet (without access to the external network) results in an error when creating an intelligent agent: "Application error: a client-side exception has occurred (see the browser console for more information)."

Upon further inspection of the console, the following message is displayed: "Cross-origin request blocked: The Same Origin Policy disallows reading the remote resource at https://api.github.com/repos/langenius/dify. (Reason: CORS request did not succeed)."

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @OneChainTech on GitHub (Mar 2, 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 0.15.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Deploying Dify on an intranet (without access to the external network) results in an error when creating an intelligent agent: "Application error: a client-side exception has occurred (see the browser console for more information)." Upon further inspection of the console, the following message is displayed: "Cross-origin request blocked: The Same Origin Policy disallows reading the remote resource at https://api.github.com/repos/langenius/dify. (Reason: CORS request did not succeed)." ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:28:16 -05:00
yindo closed this issue 2026-02-21 18:28:16 -05:00
yindo commented 2026-02-21 18:28:16 -05:00
Author
Owner
Copy Link
Copy Source

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

I found a similar open discussion regarding Dify deployment on an intranet without external network access, which encounters an error when creating an agent [1]. Additionally, there is an open issue related to CORS errors after upgrading to Dify version 0.14.0, which might be relevant to your situation [2].

To resolve the CORS error, you should:

  1. Verify that the URLs in your docker-compose.yml file match your actual domains for the following:

    • CONSOLE_API_URL (Console API backend URL)
    • CONSOLE_WEB_URL (Console Web frontend URL)
    • SERVICE_API_URL (Service API URL)
    • APP_API_URL (WebApp API backend URL)
    • APP_WEB_URL (WebApp URL)

  2. Ensure that WEB_API_CORS_ALLOW_ORIGINS and CONSOLE_CORS_ALLOW_ORIGINS are set correctly. While using '*' is suitable for testing, specify exact allowed origins in production for better security.

  3. Check for any network issues or proxy settings that might affect the requests [3].

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 2, 2025): <!-- Answer --> I found a similar open discussion regarding Dify deployment on an intranet without external network access, which encounters an error when creating an agent <sup>[[1]](https://github.com/langgenius/dify/discussions/14698)</sup>. Additionally, there is an open issue related to CORS errors after upgrading to Dify version 0.14.0, which might be relevant to your situation <sup>[[2]](https://github.com/langgenius/dify/issues/11712)</sup>. To resolve the CORS error, you should: 1. Verify that the URLs in your `docker-compose.yml` file match your actual domains for the following: - `CONSOLE_API_URL` (Console API backend URL) - `CONSOLE_WEB_URL` (Console Web frontend URL) - `SERVICE_API_URL` (Service API URL) - `APP_API_URL` (WebApp API backend URL) - `APP_WEB_URL` (WebApp URL) 2. Ensure that `WEB_API_CORS_ALLOW_ORIGINS` and `CONSOLE_CORS_ALLOW_ORIGINS` are set correctly. While using '*' is suitable for testing, specify exact allowed origins in production for better security. 3. Check for any network issues or proxy settings that might affect the requests <sup>[[3]](https://github.com/langgenius/dify/issues/12866)</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/aad78b91-fde6-4e09-aa88-b3051cadc118?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/aad78b91-fde6-4e09-aa88-b3051cadc118?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/aad78b91-fde6-4e09-aa88-b3051cadc118?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/aad78b91-fde6-4e09-aa88-b3051cadc118?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/aad78b91-fde6-4e09-aa88-b3051cadc118?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/aad78b91-fde6-4e09-aa88-b3051cadc118?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/aad78b91-fde6-4e09-aa88-b3051cadc118?feedback_type=other)</sup>
yindo commented 2026-02-21 18:28:17 -05:00
Author
Owner
Copy Link
Copy Source

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

This has been fixed in v1.0.0

@crazywoola commented on GitHub (Mar 2, 2025): This has been fixed in v1.0.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
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#8869
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?