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

404 found on initial login dify #1820

New Issue
Closed
opened 2026-02-21 17:38:16 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:38:16 -05:00
Owner
Copy Link
Copy Source

Originally created by @hanxuanliang on GitHub (Apr 7, 2024).

Self Checks

  • 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).
  • Pleas do not modify this template :) and fill in all the required fields.

Dify version

v0.5.11-fix1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. first login dify
    image

  2. then I reset my email and password
    image

  3. update docker-compose.yaml

    • expose port: api & web & db
    • add COOKIE_HTTPONLY config
    • update CONSOLE_WEB_URL and CONSOLE_API_URL config
    CONSOLE_WEB_URL: 'http://127.0.0.1:3000'
  # Password for admin user initialization.
  # If left unset, admin user will not be prompted for a password when creating the initial admin account.
  INIT_PASSWORD: ''
  # The base URL of console application api server, refers to the Console base URL of WEB service if console domain is
  # different from api or web app domain.
  # example: http://cloud.dify.ai
  CONSOLE_API_URL: 'http://127.0.0.1:5001'
  # The URL prefix for Service API endpoints, refers to the base URL of the current API service if api domain is
  # different from console domain.
  # example: http://api.dify.ai
  SERVICE_API_URL: 'http://127.0.0.1:5001'
  # The URL prefix for Web APP frontend, refers to the Web App base URL of WEB service if web app domain is different from
  # console or api domain.
  # example: http://udify.app
  APP_WEB_URL: 'http://127.0.0.1:3000'
  ...
  COOKIE_HTTPONLY: 'true'
  COOKIE_SAMESITE: 'Lax'
  COOKIE_SECURE: 'true'
  ...

✔️ Expected Behavior

I've gone through almost all the documentation and issues and still haven't found the right solution. This issue seems to appear many times in issues, why not provide a default docker-compose.dafult.yaml for the convenience of standalone deployment users to experience?

❌ Actual Behavior

image
Originally created by @hanxuanliang on GitHub (Apr 7, 2024). ### Self Checks - [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] Pleas do not modify this template :) and fill in all the required fields. ### Dify version v0.5.11-fix1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1. first login dify <img width="1792" alt="image" src="https://github.com/langgenius/dify/assets/29874640/5e3c6186-108e-4250-8447-f5a65ffd97de"> 2. then I reset my email and password <img width="886" alt="image" src="https://github.com/langgenius/dify/assets/29874640/2086b03c-c0e2-4834-8a53-ee410d22afe4"> 3. update docker-compose.yaml - expose port: api & web & db - add `COOKIE_HTTPONLY` config - update `CONSOLE_WEB_URL` and `CONSOLE_API_URL` config ```yaml CONSOLE_WEB_URL: 'http://127.0.0.1:3000' # Password for admin user initialization. # If left unset, admin user will not be prompted for a password when creating the initial admin account. INIT_PASSWORD: '' # The base URL of console application api server, refers to the Console base URL of WEB service if console domain is # different from api or web app domain. # example: http://cloud.dify.ai CONSOLE_API_URL: 'http://127.0.0.1:5001' # The URL prefix for Service API endpoints, refers to the base URL of the current API service if api domain is # different from console domain. # example: http://api.dify.ai SERVICE_API_URL: 'http://127.0.0.1:5001' # The URL prefix for Web APP frontend, refers to the Web App base URL of WEB service if web app domain is different from # console or api domain. # example: http://udify.app APP_WEB_URL: 'http://127.0.0.1:3000' ... COOKIE_HTTPONLY: 'true' COOKIE_SAMESITE: 'Lax' COOKIE_SECURE: 'true' ... ``` ### ✔️ Expected Behavior I've gone through almost all the documentation and issues and still haven't found the right solution. This issue seems to appear many times in issues, why not provide a default docker-compose.dafult.yaml for the convenience of standalone deployment users to experience? ### ❌ Actual Behavior <img width="1792" alt="image" src="https://github.com/langgenius/dify/assets/29874640/e140db62-67aa-449f-a2c5-cfee8e305a3a">
yindo added the 🐞 bug label 2026-02-21 17:38:16 -05:00
yindo closed this issue 2026-02-21 17:38:16 -05:00
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#1820
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?