Troubleshoot Ravenstash package clients
Start with the exact setup shown on the repository page. Most client failures come from a mismatched host, repository path, token owner, or environment variable.
Authentication fails
Section titled “Authentication fails”Check the following:
- The token is active and has not been rotated, revoked, or deleted.
- The token targets the account that owns the repository, its grants include the operation, and any member access is still valid.
- The environment variable is available to the actual package-manager process.
- The username is
__token__where the generated setup requires a basic-auth username. - npm auth configuration includes the full host and repository path.
- Maven’s
<server>ID matches its repository or distribution-management ID.
The repository or package cannot be found
Section titled “The repository or package cannot be found”- Copy the stable namespace and repository references from the app.
- Confirm the repository supports the requested PyPI, npm, Maven, Container, or Helm registry kind.
- Select that type’s tab and compare its generated URL with the client configuration.
- Check whether the repository was renamed.
- Confirm you are using the download host for installs and the upload host for publication.
- Verify letter case and ecosystem-specific package naming.
- Confirm the requested package version exists and has not been deleted.
A publish command targets the wrong host
Section titled “A publish command targets the wrong host”Uploads use push.{kind}.rvsta.sh. Downloads and dependency resolution use
{kind}.rvsta.sh; private mirrors use mirror.{kind}.rvsta.sh.
| Action | Host family |
|---|---|
| Publish or deploy | push.pypi.rvsta.sh, push.npm.rvsta.sh, or push.maven.rvsta.sh |
| Install or resolve | pypi.rvsta.sh, npm.rvsta.sh, or maven.rvsta.sh |
A public dependency does not resolve
Section titled “A public dependency does not resolve”- Confirm the repository’s official upstream is enabled.
- Confirm it is connected to the requested ecosystem.
- Check the explicit minimum and maximum package age on the selected upstream connection, or whether new releases are allowed immediately.
- Verify the package and version exist in the official upstream registry.
- Confirm the request is going through the correct private Ravenstash repository URL.
- Retry metadata resolution after checking the client is not using a stale negative cache.
An ecosystem cannot be removed
Section titled “An ecosystem cannot be removed”The repository must retain at least one ecosystem, and Ravenstash removes only empty ecosystems. Delete private packages and complete any cleanup reported by the app before retrying. Deleting the entire repository is a different action and affects every enabled ecosystem.
Ravenstash does not bulk-copy unknown upstream packages. The first eligible request fetches and caches the package.
The client keeps using an old URL
Section titled “The client keeps using an old URL”Inspect project files, user-level configuration, environment variables, CI variables, container build arguments, and dependency-manager credential stores. Repository renames do not leave an alias at the previous URL.
Collect useful support information
Section titled “Collect useful support information”Before contacting support, record:
- Ecosystem and package-manager version.
- Namespace and repository references, without including the token.
- The command shape with credentials removed.
- UTC time of the request.
- HTTP status and client error text.
- Whether the same operation succeeds from another environment.
Send the details to [email protected]. Never send the token secret.