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

been stuck on the web page of “http://localhost:3000/install” #3968

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

Originally created by @ViesLink on GitHub (Jun 3, 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).
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.9

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

【Has tried many times, including re-pulling the image】
① https://hub.docker.com/r/langgenius/dify-web
② docker pull langgenius/dify-web
③ Run a new containers from the image on port 3006
④ http://localhost:3000/signin and click the "Setting up an admin account"
⑤ stuck on the web page of “http://localhost:3000/install”

✔️ Expected Behavior

It can smoothly adjust to the configuration interface of the administrator account, complete the administrator registration and log in to the system

❌ Actual Behavior

Been going around in circles without any new tips
Uploading 2024-06-04 085932.png…

Originally created by @ViesLink on GitHub (Jun 3, 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] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.6.9 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 【Has tried many times, including re-pulling the image】 ① https://hub.docker.com/r/langgenius/dify-web ② docker pull langgenius/dify-web ③ Run a new containers from the image on port 3006 ④ http://localhost:3000/signin and click the "[Setting up an admin account](http://localhost:3006/install)" ⑤ stuck on the web page of “http://localhost:3000/install” ### ✔️ Expected Behavior It can smoothly adjust to the configuration interface of the administrator account, complete the administrator registration and log in to the system ### ❌ Actual Behavior Been going around in circles without any new tips ![Uploading 2024-06-04 085932.png…]()
yindo added the 🐞 bug label 2026-02-21 18:04:10 -05:00
yindo closed this issue 2026-02-21 18:04:10 -05:00
yindo commented 2026-02-21 18:04:10 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jun 3, 2024):

Please provider container logs and check if you have setup the right env variables.

@crazywoola commented on GitHub (Jun 3, 2024): Please provider container logs and check if you have setup the right env variables.
yindo commented 2026-02-21 18:04:11 -05:00
Author
Owner
Copy Link
Copy Source

@NCZkevin commented on GitHub (Jun 4, 2024):

I encountered the same issue, are there any solutions available?

a few minutes later, I resolved the issue. The key point seemed to be the NEXT_PUBLIC_API_PREFIX and NEXT_PUBLIC_PUBLIC_API_PREFIX variables. The constant spinning was due to the frontend being unable to connect to the backend. Once I changed these parameters to my local IP address, everything started working as expected. note: After modifying these parameters, you need to run npm run build for the changes to take effect.

@NCZkevin commented on GitHub (Jun 4, 2024): I encountered the same issue, are there any solutions available? ---- a few minutes later, I resolved the issue. The key point seemed to be the **NEXT_PUBLIC_API_PREFIX** and **NEXT_PUBLIC_PUBLIC_API_PREFIX** variables. The constant spinning was due to the frontend being unable to connect to the backend. Once I changed these parameters to my local IP address, everything started working as expected. note: After modifying these parameters, you need to run **npm run build** for the changes to take effect.
yindo commented 2026-02-21 18:04:11 -05:00
Author
Owner
Copy Link
Copy Source

@leechs commented on GitHub (Jun 29, 2024):

NEXT_PUBLIC_API_PREFIX=http://localhost:5001/console/api
NEXT_PUBLIC_PUBLIC_API_PREFIX=http://localhost:5001/api
I got the same issue. But it looks both variables look good to me...

@leechs commented on GitHub (Jun 29, 2024): NEXT_PUBLIC_API_PREFIX=http://localhost:5001/console/api NEXT_PUBLIC_PUBLIC_API_PREFIX=http://localhost:5001/api I got the same issue. But it looks both variables look good to me...
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#3968
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?