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

【bug】failed to load response data:No data found for resource with given identifier #4641

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

Originally created by @ForgetThatNight on GitHub (Jul 16, 2024).

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).
  • 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.11

Cloud or Self Hosted

Cloud

Steps to reproduce

None of the interfaces received any request after open website
My web/docker-compose.middleware.yaml/ api are installed in remote server.
open website http://gpu-2088:3000/install in my computer
image
image

✔️ Expected Behavior

I expected to create account to login in,but Page not responding and the daemon did not receive any error logs
this is website console

❌ Actual Behavior

this is the web log
image

Originally created by @ForgetThatNight on GitHub (Jul 16, 2024). ### 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] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.6.11 ### Cloud or Self Hosted Cloud ### Steps to reproduce None of the interfaces received any request after open website My web/docker-compose.middleware.yaml/ api are installed in remote server. open website http://gpu-2088:3000/install in my computer ![image](https://github.com/user-attachments/assets/4ae35adf-3a82-4056-8907-831bf340ff63) ![image](https://github.com/user-attachments/assets/cb4ba5b2-02d4-45fc-965f-61352da61da0) ### ✔️ Expected Behavior I expected to create account to login in,but Page not responding and the daemon did not receive any error logs this is website console ### ❌ Actual Behavior this is the web log ![image](https://github.com/user-attachments/assets/1ba9b9d8-67c1-46c4-8c76-c0f0f9a4106c)
yindo added the 🐞 bug label 2026-02-21 18:07:21 -05:00
yindo closed this issue 2026-02-21 18:07:21 -05:00
yindo commented 2026-02-21 18:07:21 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 17, 2024):

The issues you're encountering seem to be related to server connectivity and potential problems in the JavaScript code handling API responses. Here are some steps to diagnose and resolve these issues:

  1. Check Service URLs and Ports:
    Ensure that the service URLs and ports are correctly configured and accessible. Verify the following environment variables in your docker-compose.yaml file:

    CONSOLE_API_URL: 'http://<your_api_host>:<api_port>'
APP_API_URL: 'http://<your_api_host>:<api_port>'

  2. CORS Configuration:
    Ensure that the CORS settings allow the necessary origins. Update the following configurations in your docker-compose.yaml:

    CONSOLE_CORS_ALLOW_ORIGINS: '*'
WEB_API_CORS_ALLOW_ORIGINS: '*'

  3. Enable Debug Mode:
    Set the LOG_LEVEL to DEBUG and enable the DEBUG mode to capture more detailed logs:

    environment:
  LOG_LEVEL: DEBUG
  DEBUG: true

  4. Check Service Health and Status:
    Use Docker commands to check the status and logs of the services:

    docker-compose ps
docker-compose logs api

  5. Network Configuration:
    Ensure that the network configuration in Docker Compose is correct and that there are no network issues preventing the services from communicating.

  6. JavaScript Errors:
    The TypeError: Cannot read properties of undefined (reading 'isM3U8Video') error suggests a problem in the JavaScript code. Ensure that all required properties are defined and accessible in your code.

By following these steps, you should be able to diagnose and resolve the ERR_CONNECTION_REFUSED and TypeError errors in Dify's API or web services [1][2].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jul 17, 2024): <!-- Answer --> The issues you're encountering seem to be related to server connectivity and potential problems in the JavaScript code handling API responses. Here are some steps to diagnose and resolve these issues: 1. **Check Service URLs and Ports**: Ensure that the service URLs and ports are correctly configured and accessible. Verify the following environment variables in your `docker-compose.yaml` file: ```yaml CONSOLE_API_URL: 'http://<your_api_host>:<api_port>' APP_API_URL: 'http://<your_api_host>:<api_port>' ``` 2. **CORS Configuration**: Ensure that the CORS settings allow the necessary origins. Update the following configurations in your `docker-compose.yaml`: ```yaml CONSOLE_CORS_ALLOW_ORIGINS: '*' WEB_API_CORS_ALLOW_ORIGINS: '*' ``` 3. **Enable Debug Mode**: Set the `LOG_LEVEL` to `DEBUG` and enable the `DEBUG` mode to capture more detailed logs: ```yaml environment: LOG_LEVEL: DEBUG DEBUG: true ``` 4. **Check Service Health and Status**: Use Docker commands to check the status and logs of the services: ```sh docker-compose ps docker-compose logs api ``` 5. **Network Configuration**: Ensure that the network configuration in Docker Compose is correct and that there are no network issues preventing the services from communicating. 6. **JavaScript Errors**: The `TypeError: Cannot read properties of undefined (reading 'isM3U8Video')` error suggests a problem in the JavaScript code. Ensure that all required properties are defined and accessible in your code. By following these steps, you should be able to diagnose and resolve the `ERR_CONNECTION_REFUSED` and `TypeError` errors in Dify's API or web services <sup>[[1]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/learn-more/faq/install-faq.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:07:21 -05:00
Author
Owner
Copy Link
Copy Source

@ForgetThatNight commented on GitHub (Jul 17, 2024):

The issues you're encountering seem to be related to server connectivity and potential problems in the JavaScript code handling API responses. Here are some steps to diagnose and resolve these issues:

To continue talking to Dosu, mention @dosu.

I used the docker-compose.middleware.yaml instead of docker-compose.yaml
This is my step https://docs.dify.ai/v/zh-hans/getting-started/install-self-hosted/local-source-code
There were no errors in the deployment process, nothing was changed, and it was done exactly as it was on the link。

@ForgetThatNight commented on GitHub (Jul 17, 2024): > The issues you're encountering seem to be related to server connectivity and potential problems in the JavaScript code handling API responses. Here are some steps to diagnose and resolve these issues: > > _To continue talking to [Dosu](https://dosu.dev), mention @dosu._ I used the docker-compose.middleware.yaml instead of docker-compose.yaml This is my step https://docs.dify.ai/v/zh-hans/getting-started/install-self-hosted/local-source-code There were no errors in the deployment process, nothing was changed, and it was done exactly as it was on the link。
yindo commented 2026-02-21 18:07:21 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 17, 2024):

Since you are using docker-compose.middleware.yaml and have followed the deployment steps exactly as described, let's focus on specific configurations and checks for this setup:

  1. Verify Service URLs and Ports:
    Ensure that the service URLs and ports in your docker-compose.middleware.yaml file are correctly configured and accessible. Here are the key configurations to check:

    environment:
  CONSOLE_API_URL: 'http://<your_api_host>:<api_port>'
  APP_API_URL: 'http://<your_api_host>:<api_port>'

  2. Check CORS Configuration:
    Ensure that the CORS settings allow the necessary origins. Update the following configurations in your docker-compose.middleware.yaml:

    environment:
  CONSOLE_CORS_ALLOW_ORIGINS: '*'
  WEB_API_CORS_ALLOW_ORIGINS: '*'

  3. Enable Debug Mode:
    Set the LOG_LEVEL to DEBUG and enable the DEBUG mode to capture more detailed logs:

    environment:
  LOG_LEVEL: DEBUG
  DEBUG: true

  4. Check Service Health and Status:
    Use Docker commands to check the status and logs of the services:

    docker-compose -f docker-compose.middleware.yaml ps
docker-compose -f docker-compose.middleware.yaml logs api

  5. Network Configuration:
    Ensure that the network configuration in Docker Compose is correct and that there are no network issues preventing the services from communicating.

  6. JavaScript Errors:
    The TypeError: Cannot read properties of undefined (reading 'isM3U8Video') error suggests a problem in the JavaScript code. Ensure that all required properties are defined and accessible in your code.

By following these steps, you should be able to diagnose and resolve the ERR_CONNECTION_REFUSED and TypeError errors in Dify's API or web services [1].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jul 17, 2024): <!-- Answer --> Since you are using `docker-compose.middleware.yaml` and have followed the deployment steps exactly as described, let's focus on specific configurations and checks for this setup: 1. **Verify Service URLs and Ports**: Ensure that the service URLs and ports in your `docker-compose.middleware.yaml` file are correctly configured and accessible. Here are the key configurations to check: ```yaml environment: CONSOLE_API_URL: 'http://<your_api_host>:<api_port>' APP_API_URL: 'http://<your_api_host>:<api_port>' ``` 2. **Check CORS Configuration**: Ensure that the CORS settings allow the necessary origins. Update the following configurations in your `docker-compose.middleware.yaml`: ```yaml environment: CONSOLE_CORS_ALLOW_ORIGINS: '*' WEB_API_CORS_ALLOW_ORIGINS: '*' ``` 3. **Enable Debug Mode**: Set the `LOG_LEVEL` to `DEBUG` and enable the `DEBUG` mode to capture more detailed logs: ```yaml environment: LOG_LEVEL: DEBUG DEBUG: true ``` 4. **Check Service Health and Status**: Use Docker commands to check the status and logs of the services: ```sh docker-compose -f docker-compose.middleware.yaml ps docker-compose -f docker-compose.middleware.yaml logs api ``` 5. **Network Configuration**: Ensure that the network configuration in Docker Compose is correct and that there are no network issues preventing the services from communicating. 6. **JavaScript Errors**: The `TypeError: Cannot read properties of undefined (reading 'isM3U8Video')` error suggests a problem in the JavaScript code. Ensure that all required properties are defined and accessible in your code. By following these steps, you should be able to diagnose and resolve the `ERR_CONNECTION_REFUSED` and `TypeError` errors in Dify's API or web services <sup>[[1]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.middleware.yaml)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:07:21 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 17, 2024):

Duplicated question. Please make sure you have set the right environment variables in .env. Especially those ends with URL.

Also this is not Cloud version.

@crazywoola commented on GitHub (Jul 17, 2024): Duplicated question. Please make sure you have set the right environment variables in `.env`. Especially those ends with `URL`. Also this is not Cloud version.
yindo commented 2026-02-21 18:07:21 -05:00
Author
Owner
Copy Link
Copy Source

@Sololololo commented on GitHub (Jul 18, 2024):

Hello, I am very confused now. I deployed it locally. Should I modify the .env file or the docker-compose.yaml file? Or are the two modified simultaneously?

@Sololololo commented on GitHub (Jul 18, 2024): Hello, I am very confused now. I deployed it locally. Should I modify the .env file or the docker-compose.yaml file? Or are the two modified simultaneously?
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#4641
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?