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

I deployed dify on the server and got a CORS error when initializing on the client. #4401

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

Originally created by @0sengseng0 on GitHub (Jul 2, 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.12-fix1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I changed everything in.env and docker-compose.yaml that refers to CONSOLE_API_URL to a specific ip address, but when the page is initialized, the interface is still localhost. What is wrong

.env

CONSOLE_API_URL=http://192.168....
CONSOLE_WEB_URL=http://192.168....
SERVICE_API_URL=http://192.168.***
APP_API_URL=http://192.168....
APP_WEB_URL=http://192.168....

docker-compose.yaml

x-shared-env: &shared-api-worker-env
LOG_LEVEL: ${LOG_LEVEL:-INFO}
DEBUG: ${DEBUG:-false}
FLASK_DEBUG: ${FLASK_DEBUG:-false}
SECRET_KEY: ${SECRET_KEY:-sk-9f73s3ljTXVcMT3Blb3ljTqtsKiGHXVcMT3BlbkFJLK7U}
INIT_PASSWORD: ${INIT_PASSWORD:-}
CONSOLE_WEB_URL: ${CONSOLE_WEB_URL:-}
CONSOLE_API_URL: http://192.168.***

web:
image: langgenius/dify-web:0.6.12-fix1
restart: always
environment:
CONSOLE_API_URL: http://192.168.***

✔️ Expected Behavior

The page can be initialized normally

❌ Actual Behavior

CORS error occurred while page initialization

Originally created by @0sengseng0 on GitHub (Jul 2, 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.12-fix1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I changed everything in.env and docker-compose.yaml that refers to CONSOLE_API_URL to a specific ip address, but when the page is initialized, the interface is still localhost. What is wrong # .env CONSOLE_API_URL=http://192.168.... CONSOLE_WEB_URL=http://192.168.... SERVICE_API_URL=http://192.168.*** APP_API_URL=http://192.168.... APP_WEB_URL=http://192.168.... # docker-compose.yaml x-shared-env: &shared-api-worker-env LOG_LEVEL: ${LOG_LEVEL:-INFO} DEBUG: ${DEBUG:-false} FLASK_DEBUG: ${FLASK_DEBUG:-false} SECRET_KEY: ${SECRET_KEY:-sk-9f73s3ljTXVcMT3Blb3ljTqtsKiGHXVcMT3BlbkFJLK7U} INIT_PASSWORD: ${INIT_PASSWORD:-} CONSOLE_WEB_URL: ${CONSOLE_WEB_URL:-} CONSOLE_API_URL: http://192.168.*** web: image: langgenius/dify-web:0.6.12-fix1 restart: always environment: CONSOLE_API_URL: http://192.168.*** ### ✔️ Expected Behavior The page can be initialized normally ### ❌ Actual Behavior CORS error occurred while page initialization
yindo closed this issue 2026-02-21 18:06:15 -05:00
yindo commented 2026-02-21 18:06:15 -05:00
Author
Owner
Copy Link
Copy Source

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

To resolve the CORS error when initializing the client page after deploying Dify version 0.6.12-fix1 on a self-hosted server using Docker with a specific IP address, ensure that the CORS configuration is correctly set in both the .env file and the docker-compose.yaml file. Here are the steps:

  1. Update the .env file:
    Ensure that all URLs are correctly set to your specific IP address:

    CONSOLE_API_URL=http://192.168.x.x:5001
CONSOLE_WEB_URL=http://192.168.x.x
SERVICE_API_URL=http://192.168.x.x/service
APP_API_URL=http://192.168.x.x/app
APP_WEB_URL=http://192.168.x.x

  2. Update the docker-compose.yaml file:
    Make sure the environment variables in the docker-compose.yaml file are also set to the correct IP address:

    x-shared-env: &shared-api-worker-env
  LOG_LEVEL: ${LOG_LEVEL:-INFO}
  DEBUG: ${DEBUG:-false}
  FLASK_DEBUG: ${FLASK_DEBUG:-false}
  SECRET_KEY: ${SECRET_KEY:-sk-9f73s3ljTXVcMT3Blb3ljTqtsKiGHXVcMT3BlbkFJLK7U}
  INIT_PASSWORD: ${INIT_PASSWORD:-}
  CONSOLE_WEB_URL: http://192.168.x.x
  CONSOLE_API_URL: http://192.168.x.x:5001

web:
  image: langgenius/dify-web:0.6.12-fix1
  restart: always
  environment:
    CONSOLE_API_URL: http://192.168.x.x:5001

  3. Set CORS headers in Nginx:
    If you are using Nginx as a reverse proxy, ensure that the CORS headers are correctly set in your nginx.conf:

    server {
    listen 80;
    server_name 192.168.x.x;

    location / {
        proxy_pass http://api:5001;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;

        # Add CORS headers
        add_header 'Access-Control-Allow-Origin' '*';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS, DELETE, PUT';
        add_header 'Access-Control-Allow-Headers' 'Origin, Content-Type, Accept, Authorization';

        # Handle preflight requests
        if ($request_method = OPTIONS) {
            add_header 'Access-Control-Allow-Origin' '*';
            add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS, DELETE, PUT';
            add_header 'Access-Control-Allow-Headers' 'Origin, Content-Type, Accept, Authorization';
            add_header 'Access-Control-Max-Age' 1728000;
            add_header 'Content-Type' 'text/plain charset=UTF-8';
            add_header 'Content-Length' 0;
            return 204;
        }
    }
}

  4. Restart Docker containers:
    After making these changes, restart your Docker containers to apply the new configurations:

    docker-compose down
docker-compose up -d

By ensuring these configurations are correctly set, you should be able to resolve the CORS error [1][2][3][4].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jul 2, 2024): <!-- Answer --> To resolve the CORS error when initializing the client page after deploying Dify version 0.6.12-fix1 on a self-hosted server using Docker with a specific IP address, ensure that the CORS configuration is correctly set in both the `.env` file and the `docker-compose.yaml` file. Here are the steps: 1. **Update the `.env` file**: Ensure that all URLs are correctly set to your specific IP address: ```env CONSOLE_API_URL=http://192.168.x.x:5001 CONSOLE_WEB_URL=http://192.168.x.x SERVICE_API_URL=http://192.168.x.x/service APP_API_URL=http://192.168.x.x/app APP_WEB_URL=http://192.168.x.x ``` 2. **Update the `docker-compose.yaml` file**: Make sure the environment variables in the `docker-compose.yaml` file are also set to the correct IP address: ```yaml x-shared-env: &shared-api-worker-env LOG_LEVEL: ${LOG_LEVEL:-INFO} DEBUG: ${DEBUG:-false} FLASK_DEBUG: ${FLASK_DEBUG:-false} SECRET_KEY: ${SECRET_KEY:-sk-9f73s3ljTXVcMT3Blb3ljTqtsKiGHXVcMT3BlbkFJLK7U} INIT_PASSWORD: ${INIT_PASSWORD:-} CONSOLE_WEB_URL: http://192.168.x.x CONSOLE_API_URL: http://192.168.x.x:5001 web: image: langgenius/dify-web:0.6.12-fix1 restart: always environment: CONSOLE_API_URL: http://192.168.x.x:5001 ``` 3. **Set CORS headers in Nginx**: If you are using Nginx as a reverse proxy, ensure that the CORS headers are correctly set in your `nginx.conf`: ```nginx server { listen 80; server_name 192.168.x.x; location / { proxy_pass http://api:5001; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; # Add CORS headers add_header 'Access-Control-Allow-Origin' '*'; add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS, DELETE, PUT'; add_header 'Access-Control-Allow-Headers' 'Origin, Content-Type, Accept, Authorization'; # Handle preflight requests if ($request_method = OPTIONS) { add_header 'Access-Control-Allow-Origin' '*'; add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS, DELETE, PUT'; add_header 'Access-Control-Allow-Headers' 'Origin, Content-Type, Accept, Authorization'; add_header 'Access-Control-Max-Age' 1728000; add_header 'Content-Type' 'text/plain charset=UTF-8'; add_header 'Content-Length' 0; return 204; } } } ``` 4. **Restart Docker containers**: After making these changes, restart your Docker containers to apply the new configurations: ```sh docker-compose down docker-compose up -d ``` By ensuring these configurations are correctly set, you should be able to resolve the CORS error <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/install-faq.md)</sup><sup>[[2]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml)</sup><sup>[[3]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/learn-more/faq/install-faq.md)</sup><sup>[[4]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/getting-started/install-self-hosted/start-the-frontend-docker-container.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:06:15 -05:00
Author
Owner
Copy Link
Copy Source

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

See bot's reply.

@crazywoola commented on GitHub (Jul 2, 2024): See bot's reply.
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#4401
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?