- 401 while resolving Cargo packages:
- This generally indicates that you are not Authorized or the token provided during login is expired. In such case, perform cargo login against the cargo-remote repository with a newly generated token and it should fix the issue.
- If the issue persists, enable the “Anonymous download & search” option under the cargo-remote repository configuration.
- NOTE: enabling Anonymous download & search will by-pass authentication
- Package versions are not matching upstream i.e outdated packages being served from Artifactory:
- To fix this, perform ‘Zap Cache’ which will force Artifactory to update the existing metadata files from upstream.
- If the package versions are still not updated, then clear the content of the cargo-remote-cache repository, this will remove all the previously cached packages/metadata, thus fixing the version issue.
- 400/404/500 errors while resolving packages:
- These errors/issues can happen due to multiple reasons but the popular ones are: the Artifactory server is unable to connect to the upstream, the Requested package/version is not available on the upstream & Artifactory cargo-remote repository is not configured correctly. Thus, verifying the connection, package/version & configuration can help in solving the issue.