mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
[tongyi] Incorrect model credentials provided, please check and try again. #873
Reference in New Issue
Block a user
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?
Originally created by @enternal111 on GitHub (Dec 11, 2025).
Self Checks
Dify version
latest
Plugin version
tongyi 0.1.7
Cloud or Self Hosted
Cloud
Steps to reproduce
llm node run with an error：[tongyi] Incorrect model credentials provided, please check and try again.
create the apikey in day 12.11 and it works,but find the error in 12.12.the key is not expired, revoked, or not updated in the plugin,checkd with ali
use the deepseek r1 model in ali bailian,api key has been proved normal checked with ali,supposed to be caused by dify or the tongyi plugin?
renew an api key in bailian ,update in tongyi plugin，and it works.
✔️ Error log
[tongyi] Incorrect model credentials provided, please check and try again.
@dosubot[bot] commented on GitHub (Dec 11, 2025):
The "[tongyi] Incorrect model credentials provided" error in Dify Cloud with the Tongyi plugin is most often caused by credential caching and validation logic in the Dify backend, not by the Tongyi plugin itself or the Ali Bailian API key. When you update or rotate your API key, Dify may continue using a cached (stale) credential for up to 24 hours unless you explicitly update or switch the credential in the UI, which triggers a cache clear and forces the new key to be used immediately. This explains why your renewed key worked after you updated it in the plugin config—manual update invalidates the cache and resolves the error.
Other common causes include mismatches between the API key region (domestic vs international) and the plugin's endpoint setting (
use_international_endpoint), or stricter backend validation that expects keys in a specific format (often starting withsk-). Recent changes also require new fields likeauth_methodin some credential forms, so missing or misconfigured fields can trigger similar errors [source].For best results: always update or re-save your credentials in the Dify UI after rotating or renewing your API key, double-check that your endpoint matches your key's region, and ensure all required fields are filled. If you see this error again after a key change, updating the credential in the UI should resolve it immediately [source].
If you recently upgraded Dify or the plugin, check for new required fields in the credential form and fill them in as needed [source].
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@hjlarry commented on GitHub (Dec 17, 2025):
please try 0.1.10 version