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

The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again. #4523

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

Originally created by @duguwanglong on GitHub (Jul 9, 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

Self Hosted (Docker)

Steps to reproduce

I set the .env params as follow:
image
But when I commit the running, get the follow error:
image
image
image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @duguwanglong on GitHub (Jul 9, 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 Self Hosted (Docker) ### Steps to reproduce I set the .env params as follow: ![image](https://github.com/langgenius/dify/assets/48522006/0b711057-8f73-46c5-a6b3-4f729fcde704) But when I commit the running, get the follow error: ![image](https://github.com/langgenius/dify/assets/48522006/8f71f922-4137-4945-89e3-1f6fdb5a3dc3) ![image](https://github.com/langgenius/dify/assets/48522006/1ba5ae0f-e665-42dc-a52b-827ef0efc593) ![image](https://github.com/langgenius/dify/assets/48522006/48436868-7887-4ce4-979d-6e091c078a7a) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 18:06:52 -05:00
yindo commented 2026-02-21 18:06:52 -05:00
Author
Owner
Copy Link
Copy Source

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

To resolve the "404 Not Found" error on your self-hosted Dify instance (version 0.6.11) running on Docker, follow these steps:

  1. Ensure All Containers Are Running:
    Verify that all necessary containers are up and running:

    docker compose ps

    You should see services like api, worker, web, weaviate, db, redis, and nginx running.

  2. Check the Nginx Configuration:
    Ensure the Nginx container is properly configured and running:

    docker compose ps | grep nginx

  3. Access the Correct URL:
    Make sure you are accessing the correct URL. For a local setup, it should be:

    http://localhost

  4. Update and Restart Dify:
    Update and restart your Dify instance:

    cd dify/docker
git pull origin main
docker compose down
docker compose pull
docker compose up -d

  5. Check Logs for Errors:
    Inspect the logs of the Nginx and other relevant containers:

    docker logs docker-nginx-1
docker logs docker-web-1
docker logs docker-api-1

  6. Verify Docker Compose Version:
    Ensure you are using the correct Docker Compose command based on your installed version:

    docker compose version

  7. Verify Environment Variables:
    Ensure all necessary environment variables are correctly set in your docker-compose.yaml file. For example:

    CONSOLE_WEB_URL: ${CONSOLE_WEB_URL}
CONSOLE_API_URL: ${CONSOLE_API_URL}
SERVICE_API_URL: ${SERVICE_API_URL}
APP_WEB_URL: ${APP_WEB_URL}

By following these steps, you should be able to identify and resolve the "404 Not Found" error on your self-hosted Dify instance [1][2][3].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jul 9, 2024): <!-- Answer --> To resolve the "404 Not Found" error on your self-hosted Dify instance (version 0.6.11) running on Docker, follow these steps: 1. **Ensure All Containers Are Running:** Verify that all necessary containers are up and running: ```bash docker compose ps ``` You should see services like `api`, `worker`, `web`, `weaviate`, `db`, `redis`, and `nginx` running. 2. **Check the Nginx Configuration:** Ensure the Nginx container is properly configured and running: ```bash docker compose ps | grep nginx ``` 3. **Access the Correct URL:** Make sure you are accessing the correct URL. For a local setup, it should be: ```plaintext http://localhost ``` 4. **Update and Restart Dify:** Update and restart your Dify instance: ```bash cd dify/docker git pull origin main docker compose down docker compose pull docker compose up -d ``` 5. **Check Logs for Errors:** Inspect the logs of the Nginx and other relevant containers: ```bash docker logs docker-nginx-1 docker logs docker-web-1 docker logs docker-api-1 ``` 6. **Verify Docker Compose Version:** Ensure you are using the correct Docker Compose command based on your installed version: ```bash docker compose version ``` 7. **Verify Environment Variables:** Ensure all necessary environment variables are correctly set in your `docker-compose.yaml` file. For example: ```yaml CONSOLE_WEB_URL: ${CONSOLE_WEB_URL} CONSOLE_API_URL: ${CONSOLE_API_URL} SERVICE_API_URL: ${SERVICE_API_URL} APP_WEB_URL: ${APP_WEB_URL} ``` By following these steps, you should be able to identify and resolve the "404 Not Found" error on your self-hosted Dify instance <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/jp/getting-started/install-self-hosted/docker-compose.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/docker-compose.md)</sup><sup>[[3]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:06:53 -05:00
Author
Owner
Copy Link
Copy Source

@duguwanglong commented on GitHub (Jul 9, 2024):

docker logs docker-web-1

All step is correct and normal
1 docker logs docker_web_1
image
2 docker logs docker_nginx_1
image
3 docker logs docker_api_1
image

@duguwanglong commented on GitHub (Jul 9, 2024): > ```shell > docker logs docker-web-1 > ``` All step is correct and normal 1 docker logs docker_web_1 ![image](https://github.com/langgenius/dify/assets/48522006/a3c58ebd-aadc-49db-a52a-6b84b33da5d5) 2 docker logs docker_nginx_1 ![image](https://github.com/langgenius/dify/assets/48522006/83277f11-3bca-4ff5-a76f-97a7740daff8) 3 docker logs docker_api_1 ![image](https://github.com/langgenius/dify/assets/48522006/8bb0d0af-b9ba-4af7-a539-dc2934e1393f)
yindo commented 2026-02-21 18:06:53 -05:00
Author
Owner
Copy Link
Copy Source

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

The frontend service is trying to access the url you defined. But it's not accessible. Please check the nginx configuration as well. You can test it by using curl command you copy from the chrome console.

From the above information I can not infer what is going on here.

You can inspect the failed request to see it's request url. And check it if this is the same with the CONSOLE_API_URL you set.

@crazywoola commented on GitHub (Jul 10, 2024): The frontend service is trying to access the url you defined. But it's not accessible. Please check the nginx configuration as well. You can test it by using curl command you copy from the chrome console. From the above information I can not infer what is going on here. You can inspect the failed request to see it's request url. And check it if this is the same with the `CONSOLE_API_URL` you set.
yindo commented 2026-02-21 18:06:53 -05:00
Author
Owner
Copy Link
Copy Source

@krmao commented on GitHub (Dec 17, 2024):

image

how to fix?

@krmao commented on GitHub (Dec 17, 2024): ![image](https://github.com/user-attachments/assets/78e7aa36-b9cc-4380-a9cf-7d01e8a2eb70) how to fix?
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#4523
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?