langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Regarding the issue of email notifications for joining a workspace in local deployment. #8292

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

Originally created by @wang318372 on GitHub (Feb 15, 2025).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Provide a description of requested docs changes

Excuse me, does any expert know where to configure the address inside the "Join" button in the invitation email sent to users after a local deployment of Dify? It seems that there is no server IP or domain name by default.
in the mail: "href="/activate?token=03ec78cd-7ace-4069-8627-227985551daa"

Originally created by @wang318372 on GitHub (Feb 15, 2025). ### 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 report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### Provide a description of requested docs changes Excuse me, does any expert know where to configure the address inside the "Join" button in the invitation email sent to users after a local deployment of Dify? It seems that there is no server IP or domain name by default. in the mail: "href="/activate?token=03ec78cd-7ace-4069-8627-227985551daa"
yindo added the 📚 documentation label 2026-02-21 18:24:54 -05:00
yindo closed this issue 2026-02-21 18:24:54 -05:00
yindo commented 2026-02-21 18:24:54 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 15, 2025):

@wang318372 Hello there! I'm here to help you with any bugs, questions, or contributions you have. Let's tackle this together!

To configure the address inside the "Join" button in the invitation email sent to users after a local deployment of Dify, you need to set the CONSOLE_WEB_URL environment variable in the .env file. This variable is crucial for generating complete URLs in the invitation email, including the domain name. Set it to your server's IP or domain name to ensure the invitation email contains the correct address.

Example:

CONSOLE_WEB_URL=http://your-server-ip-or-domain

Additionally, if you are using Docker Compose, you should update the CONSOLE_WEB_URL in the docker-compose.yml file to reflect the new domain or IP address. This will help prevent cross-domain issues and ensure that the frontend and backend communicate correctly.

This configuration will prevent the issue of incomplete URLs (e.g., http:///activate?token=[login token]) and ensure that new users can access the activation page correctly [1][2][3].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Feb 15, 2025): <!-- Greeting --> @wang318372 Hello there! I'm here to help you with any bugs, questions, or contributions you have. Let's tackle this together! <!-- Answer --> To configure the address inside the "Join" button in the invitation email sent to users after a local deployment of Dify, you need to set the `CONSOLE_WEB_URL` environment variable in the `.env` file. This variable is crucial for generating complete URLs in the invitation email, including the domain name. Set it to your server's IP or domain name to ensure the invitation email contains the correct address. Example: ```plaintext CONSOLE_WEB_URL=http://your-server-ip-or-domain ``` Additionally, if you are using Docker Compose, you should update the `CONSOLE_WEB_URL` in the `docker-compose.yml` file to reflect the new domain or IP address. This will help prevent cross-domain issues and ensure that the frontend and backend communicate correctly. This configuration will prevent the issue of incomplete URLs (e.g., `http:///activate?token=[login token]`) and ensure that new users can access the activation page correctly <sup>[[1]](https://github.com/langgenius/dify/blob/main/docker/.env.example)</sup><sup>[[2]](https://github.com/langgenius/dify/issues/12475)</sup><sup>[[3]](https://github.com/langgenius/dify-docs/blob/main/en/learn-more/faq/install-faq.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/c051d571-3335-4fe5-9566-47272a5d9f6d?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/c051d571-3335-4fe5-9566-47272a5d9f6d?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/c051d571-3335-4fe5-9566-47272a5d9f6d?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/c051d571-3335-4fe5-9566-47272a5d9f6d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c051d571-3335-4fe5-9566-47272a5d9f6d?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/c051d571-3335-4fe5-9566-47272a5d9f6d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c051d571-3335-4fe5-9566-47272a5d9f6d?feedback_type=other)</sup>
yindo commented 2026-02-21 18:24:54 -05:00
Author
Owner
Copy Link
Copy Source

@nixinonana commented on GitHub (Mar 10, 2025):

@dosu
After deploying Dify locally (via Docker) and creating an agent, I’m attempting to share access with other devices on the same local network. When generating an invitation link through the "Members" section in the settings, the link appears valid on the host machine . However, accessing this link from another device (e.g., via http://[hostip]/activate?email=xxxx&token=XXXX) results in an error: "Link Expired or Invalid".
I have tried to update the CONSOLE_WEB_URL both in docker-compose.yaml and .env files ,but it still did not work.

@nixinonana commented on GitHub (Mar 10, 2025): @dosu After deploying Dify locally (via Docker) and creating an agent, I’m attempting to share access with other devices on the same local network. When generating an invitation link through the "Members" section in the settings, the link appears valid on the host machine . However, accessing this link from another device (e.g., via http://[hostip]/activate?email=xxxx&token=XXXX) results in an error: "Link Expired or Invalid". I have tried to update the CONSOLE_WEB_URL both in docker-compose.yaml and .env files ,but it still did not work.
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 📚 documentation
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#8292
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?