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

dify邀请别人出现链接已失效 #13966

New Issue
Closed
opened 2026-02-21 19:14:48 -05:00 by yindo · 6 comments
yindo commented 2026-02-21 19:14:48 -05:00
Owner
Copy Link
Copy Source

Originally created by @xiaotang-12-ops on GitHub (May 16, 2025).

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).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.4.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When dify invites someone to become an administrator or member, no matter what, the link will immediately become invalid when the other person clicks on it. I used to invite someone, and when they clicked on the link, they would automatically jump to the registration account page. Now, no matter how you click on the link immediately, it will show that the link has expired

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

When dify invites someone to become an administrator or member, no matter what, the link will immediately become invalid when the other person clicks on it. I used to invite someone, and when they clicked on the link, they would automatically jump to the registration account page. Now, no matter how you click on the link immediately, it will show that the link has expired

Originally created by @xiaotang-12-ops on GitHub (May 16, 2025). ### 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] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.4.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When dify invites someone to become an administrator or member, no matter what, the link will immediately become invalid when the other person clicks on it. I used to invite someone, and when they clicked on the link, they would automatically jump to the registration account page. Now, no matter how you click on the link immediately, it will show that the link has expired ![Image](https://github.com/user-attachments/assets/8b35658b-b53d-453f-ab13-10917d04e0bf) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior When dify invites someone to become an administrator or member, no matter what, the link will immediately become invalid when the other person clicks on it. I used to invite someone, and when they clicked on the link, they would automatically jump to the registration account page. Now, no matter how you click on the link immediately, it will show that the link has expired
yindo added the 🐞 bug label 2026-02-21 19:14:48 -05:00
yindo closed this issue 2026-02-21 19:14:49 -05:00
yindo commented 2026-02-21 19:14:49 -05:00
Author
Owner
Copy Link
Copy Source

@xiaotang-12-ops commented on GitHub (May 16, 2025):

这只是手机页面的一个截图，无论是电脑还是手机都是一样的，点击链接都是失效

@xiaotang-12-ops commented on GitHub (May 16, 2025): 这只是手机页面的一个截图，无论是电脑还是手机都是一样的，点击链接都是失效
yindo commented 2026-02-21 19:14:49 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 16, 2025):

Hello @xiaotang-12-ops! I'm Dosu, your friendly bot here to help you tackle bugs, answer questions, and guide you on your way to becoming a contributor. I'm on standby while you wait for a human maintainer. Let’s get started! 🚀

The issue you're experiencing with invitation links immediately becoming invalid might be related to the default expiration settings or a recent change in the codebase. By default, invitation links in Dify expire after 72 hours, but this can be configured using the INVITE_EXPIRY_HOURS environment variable [1].

To troubleshoot, you can check the following:

  1. Environment Variable: Ensure that the INVITE_EXPIRY_HOURS is set correctly in your environment configuration. If it's set to a very low value, it might cause the links to expire immediately.

  2. Version and Updates: Verify if there have been any recent updates or changes in the Dify codebase that might affect invitation link functionality. Although I couldn't find specific updates related to this issue, checking the changelog or recent commits might provide insights.

  3. Logs and Error Messages: Look for specific error messages in the logs when the invitation link is clicked. The message "Неверный пригласительный код" (Invalid invitation code) might appear if the link is deemed invalid [2].

If these steps don't resolve the issue, consider reviewing the configuration and setup of your self-hosted environment to ensure everything is correctly configured.

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 (May 16, 2025): <!-- Greeting --> Hello @xiaotang-12-ops! I'm [Dosu](https://dosu.dev), your friendly bot here to help you tackle bugs, answer questions, and guide you on your way to becoming a contributor. I'm on standby while you wait for a human maintainer. Let’s get started! 🚀 <!-- Answer --> The issue you're experiencing with invitation links immediately becoming invalid might be related to the default expiration settings or a recent change in the codebase. By default, invitation links in Dify expire after 72 hours, but this can be configured using the `INVITE_EXPIRY_HOURS` environment variable <sup>[[1]](https://github.com/crazywoola/dify-docs-mintlify/blob/main/ja-jp/getting-started/install-self-hosted/environments.mdx)</sup>. To troubleshoot, you can check the following: 1. **Environment Variable**: Ensure that the `INVITE_EXPIRY_HOURS` is set correctly in your environment configuration. If it's set to a very low value, it might cause the links to expire immediately. 2. **Version and Updates**: Verify if there have been any recent updates or changes in the Dify codebase that might affect invitation link functionality. Although I couldn't find specific updates related to this issue, checking the changelog or recent commits might provide insights. 3. **Logs and Error Messages**: Look for specific error messages in the logs when the invitation link is clicked. The message "Неверный пригласительный код" (Invalid invitation code) might appear if the link is deemed invalid <sup>[[2]](https://github.com/langgenius/dify/blob/main/web/i18n/ru-RU/login.ts)</sup>. If these steps don't resolve the issue, consider reviewing the configuration and setup of your self-hosted environment to ensure everything is correctly configured. <!-- 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/b8b11b94-5bdb-4247-869e-344fd9fd1aa6?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/b8b11b94-5bdb-4247-869e-344fd9fd1aa6?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/b8b11b94-5bdb-4247-869e-344fd9fd1aa6?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/b8b11b94-5bdb-4247-869e-344fd9fd1aa6?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b8b11b94-5bdb-4247-869e-344fd9fd1aa6?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/b8b11b94-5bdb-4247-869e-344fd9fd1aa6?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b8b11b94-5bdb-4247-869e-344fd9fd1aa6?feedback_type=other)</sup>
yindo commented 2026-02-21 19:14:49 -05:00
Author
Owner
Copy Link
Copy Source

@xiaotang-12-ops commented on GitHub (May 16, 2025):

Hello @xiaotang-12-ops! I'm Dosu, your friendly bot here to help you tackle bugs, answer questions, and guide you on your way to becoming a contributor. I'm on standby while you wait for a human maintainer. Let’s get started! 🚀

The issue you're experiencing with invitation links immediately becoming invalid might be related to the default expiration settings or a recent change in the codebase. By default, invitation links in Dify expire after 72 hours, but this can be configured using the INVITE_EXPIRY_HOURS environment variable [1].

To troubleshoot, you can check the following:

  1. Environment Variable: Ensure that the INVITE_EXPIRY_HOURS is set correctly in your environment configuration. If it's set to a very low value, it might cause the links to expire immediately.
  2. Version and Updates: Verify if there have been any recent updates or changes in the Dify codebase that might affect invitation link functionality. Although I couldn't find specific updates related to this issue, checking the changelog or recent commits might provide insights.
  3. Logs and Error Messages: Look for specific error messages in the logs when the invitation link is clicked. The message "Неверный пригласительный код" (Invalid invitation code) might appear if the link is deemed invalid [2].

If these steps don't resolve the issue, consider reviewing the configuration and setup of your self-hosted environment to ensure everything is correctly configured.

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

I confirm that there are no issues with the first and second points. For the third point, I checked the container docker-nngix-1 and there were no errors. Should I check which one?

Image

@xiaotang-12-ops commented on GitHub (May 16, 2025): > Hello [@xiaotang-12-ops](https://github.com/xiaotang-12-ops)! I'm [Dosu](https://dosu.dev), your friendly bot here to help you tackle bugs, answer questions, and guide you on your way to becoming a contributor. I'm on standby while you wait for a human maintainer. Let’s get started! 🚀 > > The issue you're experiencing with invitation links immediately becoming invalid might be related to the default expiration settings or a recent change in the codebase. By default, invitation links in Dify expire after 72 hours, but this can be configured using the `INVITE_EXPIRY_HOURS` environment variable [[1]](https://github.com/crazywoola/dify-docs-mintlify/blob/main/ja-jp/getting-started/install-self-hosted/environments.mdx). > > To troubleshoot, you can check the following: > > 1. **Environment Variable**: Ensure that the `INVITE_EXPIRY_HOURS` is set correctly in your environment configuration. If it's set to a very low value, it might cause the links to expire immediately. > 2. **Version and Updates**: Verify if there have been any recent updates or changes in the Dify codebase that might affect invitation link functionality. Although I couldn't find specific updates related to this issue, checking the changelog or recent commits might provide insights. > 3. **Logs and Error Messages**: Look for specific error messages in the logs when the invitation link is clicked. The message "Неверный пригласительный код" (Invalid invitation code) might appear if the link is deemed invalid [[2]](https://github.com/langgenius/dify/blob/main/web/i18n/ru-RU/login.ts). > > If these steps don't resolve the issue, consider reviewing the configuration and setup of your self-hosted environment to ensure everything is correctly configured. > > _To continue talking to [Dosu](https://dosu.dev), mention [@dosu](https://github.com/dosu)._ > > Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/b8b11b94-5bdb-4247-869e-344fd9fd1aa6?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/b8b11b94-5bdb-4247-869e-344fd9fd1aa6?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/b8b11b94-5bdb-4247-869e-344fd9fd1aa6?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/b8b11b94-5bdb-4247-869e-344fd9fd1aa6?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b8b11b94-5bdb-4247-869e-344fd9fd1aa6?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/b8b11b94-5bdb-4247-869e-344fd9fd1aa6?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b8b11b94-5bdb-4247-869e-344fd9fd1aa6?feedback_type=other) I confirm that there are no issues with the first and second points. For the third point, I checked the container docker-nngix-1 and there were no errors. Should I check which one? ![Image](https://github.com/user-attachments/assets/6c6a77d5-4eb3-4bcb-a7f6-4fd8d61124ef)
yindo commented 2026-02-21 19:14:49 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 16, 2025):

Since you've confirmed that the environment variable and version updates are not the issue, and there are no errors in the docker-nginx-1 container logs, you might want to check the following:

  1. Backend Logs: Look into the logs of the backend service handling the invitation activation. This might provide more detailed error messages or exceptions that are not visible in the nginx logs.

  2. Database Entries: Verify the database entries related to the invitation tokens. Ensure that the tokens are being generated and stored correctly, and check their expiration timestamps to see if they align with the expected settings.

  3. Token Validation Logic: Review the code responsible for validating the invitation tokens. There might be a bug or misconfiguration causing the tokens to be considered expired immediately.

  4. Network Configuration: Ensure there are no network issues or proxy configurations that might be altering the request or response, potentially affecting the token validation process.

These steps should help you identify any underlying issues with the invitation link processing.

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 (May 16, 2025): <!-- Answer --> Since you've confirmed that the environment variable and version updates are not the issue, and there are no errors in the `docker-nginx-1` container logs, you might want to check the following: 1. **Backend Logs**: Look into the logs of the backend service handling the invitation activation. This might provide more detailed error messages or exceptions that are not visible in the nginx logs. 2. **Database Entries**: Verify the database entries related to the invitation tokens. Ensure that the tokens are being generated and stored correctly, and check their expiration timestamps to see if they align with the expected settings. 3. **Token Validation Logic**: Review the code responsible for validating the invitation tokens. There might be a bug or misconfiguration causing the tokens to be considered expired immediately. 4. **Network Configuration**: Ensure there are no network issues or proxy configurations that might be altering the request or response, potentially affecting the token validation process. These steps should help you identify any underlying issues with the invitation link processing. <!-- 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/a8913ad3-db6a-4298-a973-0564c9f16492?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/a8913ad3-db6a-4298-a973-0564c9f16492?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/a8913ad3-db6a-4298-a973-0564c9f16492?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/a8913ad3-db6a-4298-a973-0564c9f16492?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a8913ad3-db6a-4298-a973-0564c9f16492?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/a8913ad3-db6a-4298-a973-0564c9f16492?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a8913ad3-db6a-4298-a973-0564c9f16492?feedback_type=other)</sup>
yindo commented 2026-02-21 19:14:49 -05:00
Author
Owner
Copy Link
Copy Source

@xiaotang-12-ops commented on GitHub (May 17, 2025):

好的，我已经解决了

@xiaotang-12-ops commented on GitHub (May 17, 2025): 好的，我已经解决了
yindo commented 2026-02-21 19:14:49 -05:00
Author
Owner
Copy Link
Copy Source

@Genlovy-Hoo commented on GitHub (Jan 6, 2026):

好的，我已经解决了

查出来是啥原因？

@Genlovy-Hoo commented on GitHub (Jan 6, 2026): > 好的，我已经解决了 查出来是啥原因？
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#13966
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?