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.

Sign up for GitHub

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

Jump to bottom

LFS and deploy key: Authorization error on private repos #7227

Closed
jonas-hagen opened this issue Jun 17, 2019 · 3 comments
Closed

LFS and deploy key: Authorization error on private repos #7227

jonas-hagen opened this issue Jun 17, 2019 · 3 comments
Labels
issue/duplicate The issue has already been reported.

Comments

@jonas-hagen
Copy link

jonas-hagen commented Jun 17, 2019 •
edited
Loading

  • Gitea version: 1.8.2
  • Git version: 2.19
  • Operating system: Alpine (Server), Ubuntu (Client)
  • Database: SQLite
  • Setup: nginx as reverse proxy, OpenSSH server

Description

LFS content can't be read from private repos via SSH using a deploy key. On public repos, this works (presumably since pull request #5939 as mentioned in #6127).

gitea.log:
2019/06/17 07:17:07 [D] LFS request - Method: POST, URL: /user/test.git/info/lfs/objects/batch, Status 401

Possibly related: #7219.
@jonas-hagen jonas-hagen changed the title LFS and deploy keys: Authorization error on private repos LFS and deploy key: Authorization error on private repos Jun 17, 2019
@zeripath zeripath added the issue/duplicate The issue has already been reported. label Jun 17, 2019
@zeripath
Copy link
Contributor

This is definitely a duplicate of #5478 and presumably of #7219 - and would definitely be fixed by #7224.

@zeripath
Copy link
Contributor

Fix should be in next release of 1.8 - this was fixed in 1.9 since #6993

@jonas-hagen
Copy link
Author

Thanks!

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
issue/duplicate The issue has already been reported.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zeripath @jonas-hagen