When I update to 0.14.0, it prompts an Internal Server Error #7257

Closed
opened 2026-02-21 18:19:40 -05:00 by yindo · 3 comments
Owner

Originally created by @Qinz-shao on GitHub (Dec 18, 2024).

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.14.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

docker pull langgenius/dify-api:0.14.0
docker push harbor-devops.xxx.cn/ai/dify-api:0.14.0

I update to 0.14.0
then open my web

✔️ Expected Behavior

The previous version was 0.13.0 and its worked.

Actual Behavior

image
image

Originally created by @Qinz-shao on GitHub (Dec 18, 2024). ### 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.14.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce docker pull langgenius/dify-api:0.14.0 docker push harbor-devops.xxx.cn/ai/dify-api:0.14.0 I update to 0.14.0 then open my web ### ✔️ Expected Behavior The previous version was 0.13.0 and its worked. ### ❌ Actual Behavior ![image](https://github.com/user-attachments/assets/0fd7b7ef-2258-4d30-8e8f-1cec033b5961) ![image](https://github.com/user-attachments/assets/17f01063-0147-44a3-9708-330dc3bde1cd)
yindo added the 🐞 bug label 2026-02-21 18:19:40 -05:00
yindo closed this issue 2026-02-21 18:19:40 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Dec 18, 2024):

Hey @Qinz-shao! 👋 I'm here to help you with bug fixes, questions, and becoming a contributor. Let's squash those bugs together!

A similar issue was reported and resolved in a closed thread: AttributeError: 'DifyConfig' object has no attribute 'MAX_SUBMIT_COUNT'. This issue was closed by a pull request that updated the Docker environment [1].

Regarding the FileNotFoundError you're encountering, this is commonly caused by switching deployment methods or deleting the api/storage/privkeys file, which is crucial for encrypting large model keys. To resolve this, you can reset the encryption key pair with the following commands:

For Docker Compose deployment:

docker exec -it docker-api-1 flask reset-encrypt-key-pair

For source code startup, navigate to the api directory and run:

flask reset-encrypt-key-pair

Follow the prompts to reset the key pair [2][3].

Additionally, when upgrading from version 0.13.0 to 0.14.0, ensure that you replace 'localhost' or '127.0.0.1' with 'host.docker.internal' in your Dify configuration for the service. This change is necessary for the Docker container to properly access services running on the host machine [4].

To continue talking to Dosu, mention @dosu.


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

@dosubot[bot] commented on GitHub (Dec 18, 2024): <!-- Greeting --> Hey @Qinz-shao! 👋 I'm here to help you with bug fixes, questions, and becoming a contributor. Let's squash those bugs together! <!-- Answer --> A similar issue was reported and resolved in a closed thread: [AttributeError: 'DifyConfig' object has no attribute 'MAX_SUBMIT_COUNT'](https://github.com/langgenius/dify/issues/11703). This issue was closed by a pull request that updated the Docker environment <sup>[[1]](https://github.com/langgenius/dify/issues/11703)</sup>. Regarding the `FileNotFoundError` you're encountering, this is commonly caused by switching deployment methods or deleting the `api/storage/privkeys` file, which is crucial for encrypting large model keys. To resolve this, you can reset the encryption key pair with the following commands: For Docker Compose deployment: ```bash docker exec -it docker-api-1 flask reset-encrypt-key-pair ``` For source code startup, navigate to the `api` directory and run: ```bash flask reset-encrypt-key-pair ``` Follow the prompts to reset the key pair <sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/learn-more/faq/install-faq.md)</sup><sup>[[3]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/install-faq.md)</sup>. Additionally, when upgrading from version 0.13.0 to 0.14.0, ensure that you replace 'localhost' or '127.0.0.1' with 'host.docker.internal' in your Dify configuration for the service. This change is necessary for the Docker container to properly access services running on the host machine <sup>[[4]](https://github.com/langgenius/dify/issues/11739)</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/5decc10c-c2ca-4ab8-b2d0-dd75eb5ef68b?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/5decc10c-c2ca-4ab8-b2d0-dd75eb5ef68b?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/5decc10c-c2ca-4ab8-b2d0-dd75eb5ef68b?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/5decc10c-c2ca-4ab8-b2d0-dd75eb5ef68b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5decc10c-c2ca-4ab8-b2d0-dd75eb5ef68b?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/5decc10c-c2ca-4ab8-b2d0-dd75eb5ef68b?feedback_type=other)</sup>
Author
Owner

@crazywoola commented on GitHub (Dec 18, 2024):

This should be fixed in https://github.com/langgenius/dify/pull/11754

@crazywoola commented on GitHub (Dec 18, 2024): This should be fixed in https://github.com/langgenius/dify/pull/11754
Author
Owner

@laipz8200 commented on GitHub (Dec 18, 2024):

If you're using AWS managed IAM Role for S3, it should be fixed in #11754, otherwise please check if your private key still in your storage directory.

@laipz8200 commented on GitHub (Dec 18, 2024): If you're using AWS managed IAM Role for S3, it should be fixed in #11754, otherwise please check if your private key still in your storage directory.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#7257