langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-24 22:11:36 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

"Internal Server Error" on Dify Cloud Pro account multiple times today, making it not possible to use account #5245

New Issue
Closed
opened 2026-02-21 18:10:03 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 18:10:03 -05:00
Owner
Copy Link
Copy Source

Originally created by @CodingDane on GitHub (Aug 27, 2024).

Originally assigned to: @JohnJyong, @crazywoola on GitHub.

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

0.7.2

Cloud or Self Hosted

Cloud

Steps to reproduce

Issue happened after uploading files to Knowledge through API earlier today.

✔️ Expected Behavior

Knowledge being uploaded and vectorized.

❌ Actual Behavior

Screenshot 2024-08-27 at 19 28 12

After doing the above, multiple times during today, I have been unable to use my account. Even now, I cannot use my account.
Experiencing the following issues:

  • Cannot use the chatbots (even through API access)
  • Knowledge tab disappeared
  • Plan is shown as Sandbox (even though I have the Professional plan)
Originally created by @CodingDane on GitHub (Aug 27, 2024). Originally assigned to: @JohnJyong, @crazywoola on GitHub. ### 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 0.7.2 ### Cloud or Self Hosted Cloud ### Steps to reproduce Issue happened after uploading files to Knowledge through API earlier today. ### ✔️ Expected Behavior Knowledge being uploaded and vectorized. ### ❌ Actual Behavior ![Screenshot 2024-08-27 at 19 28 12](https://github.com/user-attachments/assets/c9ffae06-818a-48e0-9905-271c242af41f) After doing the above, multiple times during today, I have been unable to use my account. Even now, I cannot use my account. Experiencing the following issues: - Cannot use the chatbots (even through API access) - Knowledge tab disappeared - Plan is shown as Sandbox (even though I have the Professional plan)
yindo added the 🐞 bug label 2026-02-21 18:10:03 -05:00
yindo closed this issue 2026-02-21 18:10:03 -05:00
yindo commented 2026-02-21 18:10:04 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 27, 2024):

@CodingDane Hello there! I'm here to help you with bug reports, answer questions, and assist you while waiting for a human maintainer. Let's tackle this issue together!

I found some similar issues and discussions that might be relevant to your problem:

  1. Help (open) - Last updated on 2024-08-19.
  2. Interface error 500 after startup (open) - Last updated on 2024-08-15.
  3. 云服务https://cloud.dify.ai/ 经常无法访问 (closed) - Last updated on January 21, 2024.
  4. Internal Server Error (closed) - Last updated on July 08, 2023.

The suggested solution for similar issues includes ensuring that the API Key in the Bearer token is correctly replaced and checking if the database is full, which might have caused the problem. The database has been upgraded to resolve such issues, so trying your request again might help [1][2][3][4].

Additionally, your plan reverting to Sandbox could be due to exceeding usage limits or a subscription payment issue. The default plan is set to Sandbox, which has basic features and limitations. If you exceed the limits of your current plan or there is a subscription issue, your plan will revert to Sandbox [5][6].

To resolve the issue, you might want to:

  1. Verify your API Key and ensure it is correctly used.
  2. Check if your database has enough space.
  3. Confirm your subscription status and ensure there are no payment issues.

If the problem persists, you may need to contact Dify support for further assistance.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Aug 27, 2024): <!-- Greeting --> @CodingDane Hello there! I'm here to help you with bug reports, answer questions, and assist you while waiting for a human maintainer. Let's tackle this issue together! <!-- Answer --> I found some similar issues and discussions that might be relevant to your problem: 1. [Help](https://github.com/langgenius/dify/discussions/7398) (open) - Last updated on 2024-08-19. 2. [Interface error 500 after startup](https://github.com/langgenius/dify/discussions/7252) (open) - Last updated on 2024-08-15. 3. [云服务https://cloud.dify.ai/ 经常无法访问](https://github.com/langgenius/dify/issues/2116) (closed) - Last updated on January 21, 2024. 4. [Internal Server Error](https://github.com/langgenius/dify/issues/526) (closed) - Last updated on July 08, 2023. The suggested solution for similar issues includes ensuring that the API Key in the Bearer token is correctly replaced and checking if the database is full, which might have caused the problem. The database has been upgraded to resolve such issues, so trying your request again might help <sup>[[1]](https://github.com/langgenius/dify/discussions/7398)</sup><sup>[[2]](https://github.com/langgenius/dify/discussions/7252)</sup><sup>[[3]](https://github.com/langgenius/dify/issues/2116)</sup><sup>[[4]](https://github.com/langgenius/dify/issues/526)</sup>. Additionally, your plan reverting to Sandbox could be due to exceeding usage limits or a subscription payment issue. The default plan is set to Sandbox, which has basic features and limitations. If you exceed the limits of your current plan or there is a subscription issue, your plan will revert to Sandbox <sup>[[5]](https://github.com/langgenius/dify/blob/main/web/app/components/billing/config.ts)</sup><sup>[[6]](https://github.com/langgenius/dify-docs/blob/main/en/guides/workspace/billing.md)</sup>. To resolve the issue, you might want to: 1. Verify your API Key and ensure it is correctly used. 2. Check if your database has enough space. 3. Confirm your subscription status and ensure there are no payment issues. If the problem persists, you may need to contact Dify support for further assistance. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:10:04 -05:00
Author
Owner
Copy Link
Copy Source

@CodingDane commented on GitHub (Aug 27, 2024):

The database limits being exceeded might be the issue.
But I cannot access the knowledge tab to delete the excess knowledges, because the account is reverted to Sandbox.

@CodingDane commented on GitHub (Aug 27, 2024): The database limits being exceeded might be the issue. But I cannot access the knowledge tab to delete the excess knowledges, because the account is reverted to Sandbox.
yindo commented 2026-02-21 18:10:04 -05:00
Author
Owner
Copy Link
Copy Source

@CodingDane commented on GitHub (Aug 27, 2024):

(update) As of this morning (JST), the account is still reverted from PRO to sandbox, and we still cannot use the chatbots even when accessing through the API.

@CodingDane commented on GitHub (Aug 27, 2024): (update) As of this morning (JST), the account is still reverted from PRO to sandbox, and we still cannot use the chatbots even when accessing through the API.
yindo commented 2026-02-21 18:10:04 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 28, 2024):

What's your current plan?

@crazywoola commented on GitHub (Aug 28, 2024): What's your current plan?
yindo commented 2026-02-21 18:10:04 -05:00
Author
Owner
Copy Link
Copy Source

@CodingDane commented on GitHub (Aug 29, 2024):

Sorry for the very late response.
I am using the PRO plan.
However, I was able to access the knowledge tab, and delete the excess knowledges.
This fixed the issue, which I then assume happened because of uploading excess knowledge for indexing via the API.

Thank you for your response!

@CodingDane commented on GitHub (Aug 29, 2024): Sorry for the very late response. I am using the PRO plan. However, I was able to access the knowledge tab, and delete the excess knowledges. This fixed the issue, which I then assume happened because of uploading excess knowledge for indexing via the API. Thank you for your response!
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#5245
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?