Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
4 tasks done
ViesLink opened this issue Jun 4, 2024 · 3 comments
Closed
4 tasks done

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

ViesLink opened this issue Jun 4, 2024 · 3 comments
Labels
🐞 bug Something isn't working

Comments

@ViesLink
Copy link

ViesLink commented Jun 4, 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…

@dosubot dosubot bot added the 🐞 bug Something isn't working label Jun 4, 2024
@crazywoola
Copy link
Member

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

@NCZkevin
Copy link

NCZkevin commented 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.

@leechs
Copy link

leechs commented 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 up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants