Feedback Title
Report on the issues encountered during the upgrade from version 1.13.3 to 1.14.0
Feedback Type
Please select one:
-
Bug Report (something broken on the forum) -
Feature Suggestion (new feature for the forum) -
Design/UI Improvement -
Content Suggestion (categories, guidelines, etc.) -
Question about the forum -
Appreciation/Compliment -
Other feedback
What’s Your Feedback?
-- Summary –
I performed an in‑place upgrade from version 1.13.3 to 1.14.0.
After the upgrade, the authentication information for my custom models became incomplete and stopped functioning.
A red message appeared with the text “Authentication has been removed”, and none of the operations seemed to work anymore.
Deleting and re‑registering the credentials did not resolve the issue.
In the end, I resolved the problem by manually deleting the relevant DB records and re‑registering the custom model credentials.
-- Environment –
This is a self‑hosted setup running Dify 1.13.3 on Ubuntu 24.04 using Docker.
The only model provider is Ollama, with multiple LLM models installed and used through Dify.
-- What Happened –
First, I upgraded the Ollama plugin from 0.13.0 to 0.15.0.
No issues occurred at this stage, and existing chatbots continued to work normally.
Next, I performed an in‑place upgrade of Dify from 1.13.3 to 1.14.0.
After this upgrade, the authentication information for all Ollama models changed to the state “Authentication has been removed”, and I was unable to modify anything.
Registering another host (adding new credentials) appeared to succeed, but switching between hosts did not work.
Deletion also appeared to work, but incomplete data remained.
Meanwhile, existing chatbots continued functioning without interruption.
-- Resolution –
I decided to manually delete the relevant DB records.
Although I cannot guarantee the safety of this approach, it resolved the issue, and I have not encountered any other problems so far.
-- Operation Log –
~$ sudo docker exec -it docker-db_postgres-1 psql -U postgres
postgres=# \c dify;
dify=# BEGIN;
dify=*# DELETE FROM provider_model_settings
dify-*# WHERE provider_name=‘langgenius/ollama/ollama’;
dify=*# DELETE FROM provider_models
dify-*# WHERE provider_name=‘langgenius/ollama/ollama’;
dify=*# DELETE FROM provider_model_credentials
dify-*# WHERE provider_name=‘langgenius/ollama/ollama’;
dify=*# COMMIT;
dify=# \q
~$ sudo docker exec -it docker-redis-1 redis-cli
127.0.0.1:6379> FLUSHALL
127.0.0.1:6379> exit
~$ cd dify/docker
~/dify/docker$ sudo docker compose down
-- Closing –
I am a beginner with Dify, having started from version 1.13.3, and I only use it privately on weekends.
I hope this information is helpful to someone.
This is my first post, so I apologize if anything is inappropriate.
Since I am not confident in English, I relied on an LLM to help with the translation.
Because the original text is in Japanese, there may be differences in the error messages.
Wishing for a bright future for LLMs.
Screenshots (if applicable)
No Screenshots.
Why Is This Important?
For me, the real hope is in LLMs becoming accessible to everyone.
Suggested Solution (optional)
I wrote Feedback field.
Browser/Device (for bug reports)
- Browser: Microsoft Edge / 147.0.3912.98
- Device: Desktop
- Operating System: Windows 11 Pro 25H2 build 26200.8246
Additional Context
clipper!
Thank you for helping us improve the Dify Community! 