Hunyuan auth failures come from the key, the clock, or the signature math
Shows how to fix hunyuan auth failures come from the key, the clock, or the signature math. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Check key existence and paste it without surrounding whitespace when SecretIdNotFound appears. AuthFailure.SecretIdNotFound means the key does not exist: check whether it was deleted or disabled in the console, and make sure no whitespace sits before or after the key.
Steps
- Check key existence and paste it without surrounding whitespace when SecretIdNotFound appears. Sync your clock when signatures expire, since more than five minutes of drift fails every request. Recalculate the signature step by step on SignatureFailure. Separate quota failures from rate failures before retrying, since retrying through a quota failure never works.
When to use
You are seeing this: Sync your clock when signatures expire, since more than five minutes of drift fails every request. Use this skill when you run into "Hunyuan auth failures come from the key, the clock, or the signature math".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.