Open kurehajime opened 2 weeks ago
@kurehajime Hello! I'm here to help you with bugs, questions, and becoming a contributor. Let me know how I can assist you!
To resolve the issue of invitation links not being generated correctly in Dify version 0.6.11 when re-inviting users or inviting deleted users in a self-hosted Docker environment, you should check and correctly configure the following environment variables:
Example configuration:
CONSOLE_API_URL=https://api.console.dify.ai
CONSOLE_WEB_URL=https://console.dify.ai
Additionally, ensure that other related environment variables are correctly set, as they might also impact the generation of invitation links:
Example configuration:
SERVICE_API_URL=https://api.dify.ai
APP_API_URL=https://app.dify.ai
APP_WEB_URL=https://app.dify.ai
Make sure these URLs are accessible and correctly point to your Dify instance's API and web frontend [1][2].
If the issue persists, you may need to clear any cache or database entries related to user invitations. Here are the steps:
Access the Docker Container:
docker exec -it <container_name> /bin/bash
Access the Database:
psql -U <username> -d <database_name>
Clear Invitation Entries:
DELETE FROM account WHERE <condition>;
DELETE FROM tenant_account_role WHERE <condition>;
Clear Cache:
redis-cli DEL member_invite:token:<token>
redis-cli DEL member_invite_token:<workspace_id>, <email_hash>:<token>
Restart the Docker Container:
docker restart <container_name>
By following these steps, you can ensure that invitation links are generated correctly for re-invited or deleted users [3][4].
To continue talking to Dosu, mention @dosu.
Thank you dosubot 👍
Deleting the data in the accounts
table correctly created the invitation link.
I have found a workaround, but it would be a better product if there was also a way to resolve this from the GUI. I don't know if data integrity can be maintained by manual deletion.
Self Checks
Dify version
0.6.11
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
Invitation links to other users are correctly generated. This problem is serious in environments where a mail server is not provided.
✔️ Expected Behavior
❌ Actual Behavior