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

ssrf: Access control configuration prevents your request from being allowed at this time #4655

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

Originally created by @likenamehaojie on GitHub (Jul 17, 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.13

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Access control configuration prevents your request from being allowed at this time

✔️ Expected Behavior

can run

❌ Actual Behavior

can run

Originally created by @likenamehaojie on GitHub (Jul 17, 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.13 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Access control configuration prevents your request from being allowed at this time ### ✔️ Expected Behavior can run ### ❌ Actual Behavior can run
yindo added the 🐞 bug🌚 invalid🤔 cant-reproduce labels 2026-02-21 18:07:25 -05:00
yindo closed this issue 2026-02-21 18:07:25 -05:00
yindo commented 2026-02-21 18:07:25 -05:00
Author
Owner
Copy Link
Copy Source

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

@likenamehaojie Hello there! I'm here to help you with any bugs, questions, or contributions while you wait for a human maintainer.

To resolve the "Access control configuration prevents your request from being allowed at this time" error in Dify version 0.6.13 when self-hosted using Docker, you should check and configure the environment variables in your .env file. Here are the steps to follow:

  1. Navigate to the Dify Docker directory:

    cd dify/docker

  2. Copy the example environment file if you haven't already:

    cp .env.example .env

  3. Edit the .env file to configure the necessary environment variables:
    Open the .env file in your preferred text editor and ensure that all required variables are set correctly. Pay special attention to any variables related to access control and permissions. Specifically, you should verify the following variables:

    • CONSOLE_API_URL
    • APP_API_URL
    • AUTHENTICATION_APIKEY_ENABLED
    • AUTHENTICATION_APIKEY_ALLOWED_KEYS
    • AUTHENTICATION_APIKEY_USERS
    • AUTHORIZATION_ADMINLIST_ENABLED
    • AUTHORIZATION_ADMINLIST_USERS
    • WEB_API_CORS_ALLOW_ORIGINS
    • CONSOLE_CORS_ALLOW_ORIGINS

  4. Restart the Dify services:

    docker compose down
docker compose up -d

By ensuring that the environment variables are correctly configured, you should be able to resolve the access control error [1][2].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jul 17, 2024): <!-- Greeting --> @likenamehaojie Hello there! I'm here to help you with any bugs, questions, or contributions while you wait for a human maintainer. <!-- Answer --> To resolve the "Access control configuration prevents your request from being allowed at this time" error in Dify version 0.6.13 when self-hosted using Docker, you should check and configure the environment variables in your `.env` file. Here are the steps to follow: 1. **Navigate to the Dify Docker directory:** ```bash cd dify/docker ``` 2. **Copy the example environment file if you haven't already:** ```bash cp .env.example .env ``` 3. **Edit the `.env` file to configure the necessary environment variables:** Open the `.env` file in your preferred text editor and ensure that all required variables are set correctly. Pay special attention to any variables related to access control and permissions. Specifically, you should verify the following variables: - `CONSOLE_API_URL` - `APP_API_URL` - `AUTHENTICATION_APIKEY_ENABLED` - `AUTHENTICATION_APIKEY_ALLOWED_KEYS` - `AUTHENTICATION_APIKEY_USERS` - `AUTHORIZATION_ADMINLIST_ENABLED` - `AUTHORIZATION_ADMINLIST_USERS` - `WEB_API_CORS_ALLOW_ORIGINS` - `CONSOLE_CORS_ALLOW_ORIGINS` 4. **Restart the Dify services:** ```bash docker compose down docker compose up -d ``` By ensuring that the environment variables are correctly configured, you should be able to resolve the access control error <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/docker-compose.md)</sup><sup>[[2]](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:07:25 -05:00
Author
Owner
Copy Link
Copy Source

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

Please provide a screenshot of the orchestration view, or other details that may help us to understand.

@crazywoola commented on GitHub (Jul 17, 2024): Please provide a screenshot of the orchestration view, or other details that may help us to understand.
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 🌚 invalid 🐞 bug 🤔 cant-reproduce
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#4655
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?