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

error :The dify source code I started locally, #12109

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

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

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

Provide a description of requested docs changes

The dify source code I started locally, I accessed it http://localhost:3000/ There is an error when it occurs.

Image

Image

Originally created by @zuodr on GitHub (Mar 25, 2025). ### Self Checks - [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 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. ### Provide a description of requested docs changes The dify source code I started locally, I accessed it http://localhost:3000/ There is an error when it occurs. ![Image](https://github.com/user-attachments/assets/c81e7e9d-8cf8-40da-91f2-ef426360c628) ![Image](https://github.com/user-attachments/assets/f89af0d7-87db-4005-9aa7-7c1571f91afd)
yindo closed this issue 2026-02-21 19:05:49 -05:00
yindo commented 2026-02-21 19:05:49 -05:00
Author
Owner
Copy Link
Copy Source

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

I got the same, have you overcame that?

@HojaMuerta commented on GitHub (Mar 25, 2025): I got the same, have you overcame that?
yindo commented 2026-02-21 19:05:49 -05:00
Author
Owner
Copy Link
Copy Source

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

I got the same, have you overcame that?

NO，I need help

@zuodr commented on GitHub (Mar 25, 2025): > I got the same, have you overcame that? NO，I need help
yindo commented 2026-02-21 19:05:49 -05:00
Author
Owner
Copy Link
Copy Source

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

Hello, @zuodr! I'm here to help you with any bugs, questions, or contributions you may have regarding the dify source code. Let's work together to resolve the issue you're experiencing.

I found a similar closed issue that might be relevant to your problem. The issue involved a page not loading properly due to a 400 Bad Request error. The suggested solutions were:

  1. Cross-Domain Issues: Ensure that the CORS settings in your environment variables are correctly configured. Set WEB_API_CORS_ALLOW_ORIGINS and CONSOLE_CORS_ALLOW_ORIGINS to '*' to allow all origins.

  2. Environment Configuration: Verify that your environment variables are correctly set up. Ensure you have a .env.local file in your web directory with configurations like NEXT_PUBLIC_API_PREFIX and NEXT_PUBLIC_PUBLIC_API_PREFIX pointing to your backend services.

  3. Redis Configuration: Enable vm.overcommit_memory by adding vm.overcommit_memory = 1 to your /etc/sysctl.conf file and running sysctl vm.overcommit_memory=1.

  4. Backend Services: Ensure all backend services are running and accessible. Check logs for connectivity issues with services like Redis or PostgreSQL.

  5. Frontend Build and Start: Build and start the frontend correctly. Navigate to the web directory, run npm install, npm run build, and npm run start. Access the application at http://127.0.0.1:3000.

Addressing these areas should help resolve the issue with the page not loading properly [1].

Regarding the UTF-8 decoding error, I couldn't find specific information in the repository about how Dify handles UTF-8 encoding and decoding. However, such errors typically occur when the data being processed contains bytes that are not valid UTF-8 sequences. You might want to check the data being sent in the request to ensure it is properly encoded in UTF-8.

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 --> Hello, @zuodr! I'm here to help you with any bugs, questions, or contributions you may have regarding the dify source code. Let's work together to resolve the issue you're experiencing. <!-- Answer --> I found a similar closed issue that might be relevant to your problem. The issue involved a page not loading properly due to a 400 Bad Request error. The suggested solutions were: 1. **Cross-Domain Issues**: Ensure that the CORS settings in your environment variables are correctly configured. Set `WEB_API_CORS_ALLOW_ORIGINS` and `CONSOLE_CORS_ALLOW_ORIGINS` to `'*'` to allow all origins. 2. **Environment Configuration**: Verify that your environment variables are correctly set up. Ensure you have a `.env.local` file in your web directory with configurations like `NEXT_PUBLIC_API_PREFIX` and `NEXT_PUBLIC_PUBLIC_API_PREFIX` pointing to your backend services. 3. **Redis Configuration**: Enable `vm.overcommit_memory` by adding `vm.overcommit_memory = 1` to your `/etc/sysctl.conf` file and running `sysctl vm.overcommit_memory=1`. 4. **Backend Services**: Ensure all backend services are running and accessible. Check logs for connectivity issues with services like Redis or PostgreSQL. 5. **Frontend Build and Start**: Build and start the frontend correctly. Navigate to the web directory, run `npm install`, `npm run build`, and `npm run start`. Access the application at [http://127.0.0.1:3000](http://127.0.0.1:3000/). Addressing these areas should help resolve the issue with the page not loading properly <sup>[[1]](https://github.com/langgenius/dify/issues/16001)</sup>. Regarding the UTF-8 decoding error, I couldn't find specific information in the repository about how Dify handles UTF-8 encoding and decoding. However, such errors typically occur when the data being processed contains bytes that are not valid UTF-8 sequences. You might want to check the data being sent in the request to ensure it is properly encoded in UTF-8. <!-- 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/f17cfb9f-79a2-4401-ad3d-68aa23549fe2?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/f17cfb9f-79a2-4401-ad3d-68aa23549fe2?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/f17cfb9f-79a2-4401-ad3d-68aa23549fe2?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/f17cfb9f-79a2-4401-ad3d-68aa23549fe2?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f17cfb9f-79a2-4401-ad3d-68aa23549fe2?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/f17cfb9f-79a2-4401-ad3d-68aa23549fe2?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f17cfb9f-79a2-4401-ad3d-68aa23549fe2?feedback_type=other)</sup>
yindo commented 2026-02-21 19:05:49 -05:00
Author
Owner
Copy Link
Copy Source

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

We do not provide technical support for starting from the source. Thank you for your understanding. We assume you have the necessary expertise to set it up independently. If you require technical support, please obtain our business license by contacting us at business@dify.ai.

@crazywoola commented on GitHub (Mar 25, 2025): We do not provide technical support for starting from the source. Thank you for your understanding. We assume you have the necessary expertise to set it up independently. If you require technical support, please obtain our business license by contacting us at business@dify.ai.
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#12109
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?