Codeberg/Community
60
387
Fork
You've already forked Community
12

Can't update Cargo registry #1701

Closed
opened 2024年11月13日 10:44:44 +01:00 by dcz_pf · 1 comment

Comment

Trying to set up a Cargo registry, I followed this guide: https://forgejo.org/docs/latest/user/packages/cargo/

Then I generated a token using the Web interface at https://codeberg.org/user/settings/applications

When doing cargo publish, the token is rejected:

cargo publish --token=... --index="https://codeberg.org/dcz_pf/_cargo-index.git"
[...]
error: failed to publish to registry at https://codeberg.org/api/packages/dcz_pf/cargo
Caused by:
 failed to get a 200 OK response, got 401
 headers:
 HTTP/2 401
 content-type: text/plain; charset=utf-8
 date: 2024年11月13日 09:39:52 GMT
 content-length: 17
 strict-transport-security: max-age=63072000; includeSubDomains; preload
 permissions-policy: interest-cohort=()
 x-frame-options: sameorigin
 x-content-type-options: nosniff
 
 body:
 authGroup.Verify

Even creating a token with all permissions gives the same result.

The same problem was encountered before: #941

@tok did you manage to find a solution?

### Comment Trying to set up a Cargo registry, I followed this guide: https://forgejo.org/docs/latest/user/packages/cargo/ Then I generated a token using the Web interface at https://codeberg.org/user/settings/applications When doing `cargo publish`, the token is rejected: ``` cargo publish --token=... --index="https://codeberg.org/dcz_pf/_cargo-index.git" [...] error: failed to publish to registry at https://codeberg.org/api/packages/dcz_pf/cargo Caused by: failed to get a 200 OK response, got 401 headers: HTTP/2 401 content-type: text/plain; charset=utf-8 date: 2024年11月13日 09:39:52 GMT content-length: 17 strict-transport-security: max-age=63072000; includeSubDomains; preload permissions-policy: interest-cohort=() x-frame-options: sameorigin x-content-type-options: nosniff body: authGroup.Verify ``` Even creating a token with all permissions gives the same result. The same problem was encountered before: https://codeberg.org/Codeberg/Community/issues/941 @tok did you manage to find a solution?
Author
Copy link

I managed to get things to upload. The problem was: the token is not just the token:

[registries.gitea]
token = "Bearer {token}"

This extra string has not been made prominent enough IMO. Alternatively, the error message is not making it clear that the token type is wrong.

I managed to get things to upload. The problem was: the token is not just the token: ``` [registries.gitea] token = "Bearer {token}" ``` This extra string has not been made prominent enough IMO. Alternatively, the error message is not making it clear that the token type is wrong.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug
Something is not working the way it should. Does not concern outages.
bug
infrastructure
Errors evidently caused by infrastructure malfunctions or outages
Codeberg
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome
Please join the discussion and consider contributing a PR!
docs
No bug, but an improvement to the docs or UI description will help
duplicate
This issue or pull request already exists
enhancement
New feature
infrastructure
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal
An issue directly involving legal compliance
licence / ToS
involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations
Things related to Codeberg's external communication
question
More information is needed
question
user support
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo
Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration
Migration related issues in Forgejo
s/Pages
Issues related to the Codeberg Pages feature
s/Weblate
Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker
Woodpecker CI related issue
security
involves improvements to the sites security
service
Add a new service to the Codeberg ecosystem (instead of implementing into Forgejo)
upstream
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Forgejo, Weblate, etc.)
wontfix
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#1701
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?