github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-24 23:46:30 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

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

New Issue
Closed
opened 2025-11-02 05:14:17 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 05:14:17 -06:00
Owner
Copy Link

Originally created by @jonas-hagen on GitHub (Jun 17, 2019).

  • 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.

Originally created by @jonas-hagen on GitHub (Jun 17, 2019). - 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.
GiteaMirror added the issue/duplicate label 2025-11-02 05:14:17 -06:00
GiteaMirror commented 2025-11-02 05:14:18 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jun 17, 2019):

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

@zeripath commented on GitHub (Jun 17, 2019): This is definitely a duplicate of #5478 and presumably of #7219 - and would definitely be fixed by #7224.
GiteaMirror commented 2025-11-02 05:14:18 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jun 17, 2019):

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

@zeripath commented on GitHub (Jun 17, 2019): Fix should be in next release of 1.8 - this was fixed in 1.9 since #6993
GiteaMirror commented 2025-11-02 05:14:19 -06:00
Author
Owner
Copy Link

@jonas-hagen commented on GitHub (Jun 19, 2019):

Thanks!

@jonas-hagen commented on GitHub (Jun 19, 2019): Thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3480
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?