Skip to content
MyDSHMy DSH Field Notes
中文
Independently maintained; not affiliated with DeepSeek. No association with mydsh.dev or other MyDSH sites.

Home/Models, permissions & security/Model & routing

What a wrong model ID looks like, and the order to check

The error is opaque, the first instinct is network or key, and half an hour later neither was it.

To be testedVersion and environmentChecked 2026-11-14
Host version
0.1.2-alpha.5
Status
error texts not yet captured per gateway; this page is the order to check
Checked
2026-11-14

Copyable command

dsh --dump-config | grep -i -A3 model
Honest note: gateways word a bad model ID very differently — 404, 400, or silently falling back to a default. We have not captured each one, so this page gives the order to check rather than 'the canonical error', which is usually copied from somewhere else.

Check in this order, do not skip

  1. Confirm the effective model ID from dsh --dump-config. The file you edited and what it prints are often two different things.
  2. Check spelling and case: gateway model IDs are usually case sensitive and carry version suffixes. deepseek-chat and DeepSeek-Chat are not the same.
  3. Check whether the gateway offers it: the same vendor can differ by region or plan. Query the gateway's model list.
  4. Only then suspect key and network. Reversed order wastes time on parts that never broke.

A cheap discriminator

Swap in an ID the gateway documents, change nothing else, rerun the same task:

Read package.json in the current directory and report only the name field.

Works with the known-good ID → the problem is the ID. Still fails → key, endpoint, or network. This halves the search space faster than testing one factor at a time.

What to record

  • The verbatim error, not your paraphrase ('it said the model does not exist' drops the signal).
  • The model ID, gateway address (mask as needed), and host version.
  • What you did that fixed it.

What counts as working

Check every line. All of them pass or the job is not done.

  • You can state the effective model ID
  • You can classify the error (ID, key, gateway, network)
  • The task passes with a known-good ID

Where it fails

Symptom, cause, what to do — written in the order it actually happens.

SymptomCauseWhat to do
Still failing with a known-good IDNot a model ID problem: key, endpoint, or networkCheck key scope and gateway reachability in that order
The error never mentions 'model'The request may never have left, or was rejected at authCheck key and base URL before the model ID

Sources

Verified means measured here. Compiled means every line carries a source.

Other topics in this group

Back to this group All topics