Troubleshooting
Fix dsh plugin add not working
If dsh plugin add is not working, separate command parsing, package resolution, profile selection, and dependency installation before retrying.
01
Validate the command as data
Compare the package or local path and profile with current upstream documentation. Do not repair copied placeholders by guessing.
- Remove Markdown formatting
- Replace documented placeholders deliberately
- Avoid shell pipelines from unreviewed sources
02
Inspect the stage that failed
A registry 404, permission error, ignored build, and profile error need different fixes. Keep the exact exit code and package-manager output.
- Confirm network and registry independently
- Check write permission
- Retry only after identifying the failed stage
Review sources
Sources help verify current facts. Their inclusion does not imply endorsement of this page.
dsh plugin add not working questions
Why is dsh plugin add not working when I copied the command from the docs?
Copied commands often carry Markdown artifacts, smart quotes, or a placeholder you were supposed to replace. Read the command as plain text and check each argument before concluding the tool is at fault.
How do I tell which stage failed?
A registry 404 means the package name or version does not exist, a permission error means the install path is not writable, an ignored-build warning means dependency scripts were blocked, and a profile error means the target profile is missing. Each of those needs a different fix.
Can I guess the package name from the plugin's display name?
No. Catalog names are display labels, and guessing is exactly how people end up installing a typosquatted package. Take the package name from the repository itself.
Does retrying help with dsh plugin add not working?
Only for genuine network failures. Repeating the command after a 404 or a permission error simply repeats the error and can obscure which stage failed originally.
What if the same command works on another machine?
Compare the package-manager version, the registry configuration, and the active profile between the two. Those three account for most installs that work in one place and not the other.