Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permissions issues when publishing #39

Open
schragnasher opened this issue Sep 27, 2024 · 0 comments
Open

Permissions issues when publishing #39

schragnasher opened this issue Sep 27, 2024 · 0 comments

Comments

@schragnasher
Copy link

When trying to publish i get this 401 error, but i cant figure out why, i have admin privileges, i am using my token, git seems to be setup right, i am not sure what exactly is failing.

$ cargo publish
note: found `my-cargo` as only allowed registry. Publishing to it automatically.
    Updating `my-cargo` index
warning: manifest has no description, license, license-file, documentation, homepage or repository.
See https://doc.rust-lang.org/cargo/reference/manifest.html#package-metadata for more info.
   Packaging hello_world_lib v0.1.0 (/home/josh/rust-lib/hello_world_lib)
   Verifying hello_world_lib v0.1.0 (/home/josh/rust-lib/hello_world_lib)
   Compiling hello_world_lib v0.1.0 (/home/josh/rust-lib/hello_world_lib/target/package/hello_world_lib-0.1.0)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 1.46s
    Packaged 5 files, 1.1KiB (897.0B compressed)
   Uploading hello_world_lib v0.1.0 (/home/josh/rust-lib/hello_world_lib)
error: failed to publish to registry at https://my.host/repository/my-cargo

Caused by:
  failed to get a 200 OK response, got 401
  headers:
        HTTP/1.1 401 Unauthorized
        Content-Length: 0
        Date: Fri, 27 Sep 2024 15:22:53 GMT
        Server: Nexus/3.68.1-02 (PRO)
        WWW-Authenticate: BASIC realm="Sonatype Nexus Repository Manager"
        X-Content-Type-Options: nosniff
  
  body:
  • What are you trying to do?
    Publish to a private nexus instance

  • What feature or behavior is this required for?
    publishing

  • How could we solve this issue? (Not knowing is okay!)
    no idea

  • Anything else?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant