langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-25 11:59:42 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Stuck while creating administrator account #4335

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

Originally created by @Shuming-Cheng on GitHub (Jun 30, 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

After the normal installation steps, enter the interface and prepare to create an administrator account. Unable to load
image

✔️ Expected Behavior

Creating an account normally

❌ Actual Behavior

Unable to create account

Originally created by @Shuming-Cheng on GitHub (Jun 30, 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 After the normal installation steps, enter the interface and prepare to create an administrator account. Unable to load ![image](https://github.com/langgenius/dify/assets/60544052/fd644463-b573-4f17-acc6-9820080c7a09) ### ✔️ Expected Behavior Creating an account normally ### ❌ Actual Behavior Unable to create account
yindo added the 🐞 bug label 2026-02-21 18:05:50 -05:00
yindo closed this issue 2026-02-21 18:05:50 -05:00
yindo commented 2026-02-21 18:05:50 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 30, 2024):

To resolve the issue with the page not loading properly when trying to create an administrator account in Dify version 0.6.12-fix1, follow these steps:

  1. Check Docker Containers: Ensure all necessary Docker containers are running correctly:

    docker compose ps

  2. Inspect Logs: Check the logs of the web container for any errors:

    docker logs docker-web-1

  3. Network Issues: Ensure there are no network issues or firewall rules blocking access to the necessary ports (e.g., port 80).

  4. Browser Console: Open the browser's developer console (F12) and check for any JavaScript errors or network issues.

  5. Environment Variables: Ensure that the environment variables in your .env file are correctly set up. Compare them with the docker/.env.example file.

  6. Restart Services: Restart the services:

    docker compose down
docker compose up -d

If the issue persists, providing more detailed logs or error messages can help with further diagnosis [1].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jun 30, 2024): <!-- Answer --> To resolve the issue with the page not loading properly when trying to create an administrator account in Dify version 0.6.12-fix1, follow these steps: 1. **Check Docker Containers**: Ensure all necessary Docker containers are running correctly: ```bash docker compose ps ``` 2. **Inspect Logs**: Check the logs of the web container for any errors: ```bash docker logs docker-web-1 ``` 3. **Network Issues**: Ensure there are no network issues or firewall rules blocking access to the necessary ports (e.g., port 80). 4. **Browser Console**: Open the browser's developer console (F12) and check for any JavaScript errors or network issues. 5. **Environment Variables**: Ensure that the environment variables in your `.env` file are correctly set up. Compare them with the `docker/.env.example` file. 6. **Restart Services**: Restart the services: ```bash docker compose down docker compose up -d ``` If the issue persists, providing more detailed logs or error messages can help with further diagnosis <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/docker-compose.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:05:50 -05:00
Author
Owner
Copy Link
Copy Source

@potofo commented on GitHub (Jun 30, 2024):

Hi @Shuming-Cheng

Please confirm the following three points.
I sccesfull to execute Dify-0.6.12-fix1 with this temporary workaround.

  1. Create the dify/docker/.env file (#5744)
    cp dify/docker/.env.example dify/docker/.env
  2. Set CONSOLE_API_URL (#5735)
    vi dify/docker/.env
# The backend URL of the console API,
# used to concatenate the authorization callback.
# If empty, it is the same domain.
# Example: https://api.console.dify.ai
CONSOLE_API_URL=http://localhost
  1. Set CONSOLE_API_URL in the web section of docker-compose.yaml (#5735)
    vi dify/docker/docker-compose.yaml
# Frontend web application.
web:
image: langgenius/dify-web:0.6.12-fix1
restart: always
environment:
#CONSOLE_API_URL: ${CONSOLE_API_URL:-}
CONSOLE_API_URL: ''
``
![Dify-v0 6 12-fix1](https://github.com/langgenius/dify/assets/138992835/cd63a4fd-89c5-49c5-9a3f-e2e67bc0e076)
@potofo commented on GitHub (Jun 30, 2024): Hi @Shuming-Cheng Please confirm the following three points. I sccesfull to execute Dify-0.6.12-fix1 with this temporary workaround. 1. Create the dify/docker/.env file (#5744) cp dify/docker/.env.example dify/docker/.env 2. Set CONSOLE_API_URL (#5735) vi dify/docker/.env ``` # The backend URL of the console API, # used to concatenate the authorization callback. # If empty, it is the same domain. # Example: https://api.console.dify.ai CONSOLE_API_URL=http://localhost ``` 3. Set CONSOLE_API_URL in the web section of docker-compose.yaml (#5735) vi dify/docker/docker-compose.yaml ``` # Frontend web application. web: image: langgenius/dify-web:0.6.12-fix1 restart: always environment: #CONSOLE_API_URL: ${CONSOLE_API_URL:-} CONSOLE_API_URL: '' `` ![Dify-v0 6 12-fix1](https://github.com/langgenius/dify/assets/138992835/cd63a4fd-89c5-49c5-9a3f-e2e67bc0e076)
yindo commented 2026-02-21 18:05:50 -05:00
Author
Owner
Copy Link
Copy Source

@Shuming-Cheng commented on GitHub (Jun 30, 2024):

image
image
Created a new. env file
The following changes have been made to Docker Compose.yaml
docker compose up -d
The problem is still unresolved

@Shuming-Cheng commented on GitHub (Jun 30, 2024): ![image](https://github.com/langgenius/dify/assets/60544052/81450ae7-f79b-494f-bdcf-c201fedeccbe) ![image](https://github.com/langgenius/dify/assets/60544052/b1380a00-06f5-47c8-b07f-a48adf7a6b48) Created a new. env file The following changes have been made to Docker Compose.yaml docker compose up -d The problem is still unresolved
yindo commented 2026-02-21 18:05:51 -05:00
Author
Owner
Copy Link
Copy Source

@Shuming-Cheng commented on GitHub (Jun 30, 2024):

hello @potofo , I still can't fix this problem.

@Shuming-Cheng commented on GitHub (Jun 30, 2024): hello @potofo , I still can't fix this problem.
yindo commented 2026-02-21 18:05:51 -05:00
Author
Owner
Copy Link
Copy Source

@takatost commented on GitHub (Jun 30, 2024):

Hey @Shuming-Cheng 😃, thx a lot for your feedback! You can help us pinpoint the issue by following these steps:

  1. Open your browser’s dev tools, switch to the Network tab, and refresh the page. Check if there are any requests still loading or failing. If you see any suspicious requests, take a screenshot of the request list and the details of those requests

  2. Have you made any changes to the docker-compose.yaml and .env configuration files? Especially configs related to addresses and ports like the nginx port, CONSOLE_API_URL, and CORS settings, etc.

Thx!

@takatost commented on GitHub (Jun 30, 2024): Hey @Shuming-Cheng 😃, thx a lot for your feedback! You can help us pinpoint the issue by following these steps: 1. Open your browser’s dev tools, switch to the Network tab, and refresh the page. Check if there are any requests still loading or failing. If you see any suspicious requests, take a screenshot of the request list and the details of those requests 2. Have you made any changes to the `docker-compose.yaml` and `.env` configuration files? Especially configs related to addresses and ports like the nginx port, `CONSOLE_API_URL`, and CORS settings, etc. Thx!
yindo commented 2026-02-21 18:05:51 -05:00
Author
Owner
Copy Link
Copy Source

@potofo commented on GitHub (Jun 30, 2024):

hello @Shuming-Cheng

Have you confirmed the fix in the dify/docker/docker-compose.yaml file?
You have to change following line 307.

before
307 CONSOLE_API_URL: ${CONSOLE_API_URL:-}
after
307 CONSOLE_API_URL: ''

303   web:
304     image: langgenius/dify-web:0.6.12-fix1
305     restart: always
306     environment:
307       #CONSOLE_API_URL: ${CONSOLE_API_URL:-}
308       CONSOLE_API_URL: ''
309       APP_API_URL: ${APP_API_URL:-}
310       SENTRY_DSN: ${SENTRY_DSN:-}
@potofo commented on GitHub (Jun 30, 2024): hello @Shuming-Cheng Have you confirmed the fix in the dify/docker/docker-compose.yaml file? You have to change following line 307. before 307 **CONSOLE_API_URL: ${CONSOLE_API_URL:-}** after 307 **CONSOLE_API_URL: ''** ``` 303 web: 304 image: langgenius/dify-web:0.6.12-fix1 305 restart: always 306 environment: 307 #CONSOLE_API_URL: ${CONSOLE_API_URL:-} 308 CONSOLE_API_URL: '' 309 APP_API_URL: ${APP_API_URL:-} 310 SENTRY_DSN: ${SENTRY_DSN:-} ```
yindo commented 2026-02-21 18:05:51 -05:00
Author
Owner
Copy Link
Copy Source

@Tomuncle1 commented on GitHub (Jun 30, 2024):

same question,hope to solve it

@Tomuncle1 commented on GitHub (Jun 30, 2024): same question,hope to solve it
yindo commented 2026-02-21 18:05:51 -05:00
Author
Owner
Copy Link
Copy Source

@0sengseng0 commented on GitHub (Jul 2, 2024):

Hey @Shuming-Cheng 😃, thx a lot for your feedback! You can help us pinpoint the issue by following these steps:嘿@Shuming-Cheng 😃，非常感谢您的反馈！您可以按照以下步骤帮助我们查明问题：

  1. Open your browser’s dev tools, switch to the Network tab, and refresh the page. Check if there are any requests still loading or failing. If you see any suspicious requests, take a screenshot of the request list and the details of those requests打开浏览器的开发工具，切换到“网络”选项卡，然后刷新页面。检查是否有任何请求仍在加载或失败。如果您发现任何可疑请求，请截取请求列表以及这些请求的详细信息
  2. Have you made any changes to the docker-compose.yaml and .env configuration files? Especially configs related to addresses and ports like the nginx port, CONSOLE_API_URL, and CORS settings, etc.您是否对 docker-compose.yaml 和 .env 配置文件进行了任何更改？特别是与地址和端口相关的配置，例如 nginx 端口、 CONSOLE_API_URL 和 CORS 设置等。

Thx! 谢谢！
I deployed dify on the server and got a CORS error when initializing on the client:
image
image
image
image
image

milvus-standalone log

image
image

@0sengseng0 commented on GitHub (Jul 2, 2024): > Hey @Shuming-Cheng 😃, thx a lot for your feedback! You can help us pinpoint the issue by following these steps:嘿@Shuming-Cheng 😃，非常感谢您的反馈！您可以按照以下步骤帮助我们查明问题： > > 1. Open your browser’s dev tools, switch to the Network tab, and refresh the page. Check if there are any requests still loading or failing. If you see any suspicious requests, take a screenshot of the request list and the details of those requests打开浏览器的开发工具，切换到“网络”选项卡，然后刷新页面。检查是否有任何请求仍在加载或失败。如果您发现任何可疑请求，请截取请求列表以及这些请求的详细信息 > 2. Have you made any changes to the `docker-compose.yaml` and `.env` configuration files? Especially configs related to addresses and ports like the nginx port, `CONSOLE_API_URL`, and CORS settings, etc.您是否对 `docker-compose.yaml` 和 `.env` 配置文件进行了任何更改？特别是与地址和端口相关的配置，例如 nginx 端口、 `CONSOLE_API_URL` 和 CORS 设置等。 > > Thx! 谢谢！ I deployed dify on the server and got a CORS error when initializing on the client: ![image](https://github.com/langgenius/dify/assets/73268510/3f446da3-0232-4322-9362-08b476749718) ![image](https://github.com/langgenius/dify/assets/73268510/0e6c002a-db78-4451-bfe8-fde6db76878f) ![image](https://github.com/langgenius/dify/assets/73268510/3b434a71-b166-4375-935b-518259feb67d) ![image](https://github.com/langgenius/dify/assets/73268510/ce33e4a6-1085-428b-a49c-1056a3c81b3d) ![image](https://github.com/langgenius/dify/assets/73268510/fae57371-e901-40ca-a4f5-3391653e3e94) # milvus-standalone log ![image](https://github.com/langgenius/dify/assets/73268510/429f779a-3577-4792-b003-a616c0423ff2) ![image](https://github.com/langgenius/dify/assets/73268510/36871a54-64c3-4b74-a39e-b50ed0707b60)
yindo commented 2026-02-21 18:05:51 -05:00
Author
Owner
Copy Link
Copy Source

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

image.
See this, you are trying to access localhost from public ip address. @0sengseng0
You should set this CONSOLE_API_URL to your ip address instead.

@crazywoola commented on GitHub (Jul 5, 2024): <img width="282" alt="image" src="https://github.com/langgenius/dify/assets/100913391/61f3c249-ecfd-4a24-b47a-c134edd4f978">. See this, you are trying to access localhost from public ip address. @0sengseng0 You should set this `CONSOLE_API_URL` to your ip address instead.
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#4335
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?