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

ssh broke #1824

New Issue
Closed
opened 2025-11-02 04:14:23 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 04:14:23 -06:00
Owner
Copy Link

Originally created by @UtechtDustin on GitHub (May 25, 2018).

After install gitea i saw that the ssh login broke with the error message

TY allocation request failed on channel 0
Hi there, You've successfully authenticated, but Gitea does not provide shell access.
If this is unexpected, please log in with password and setup Gitea under another user.
Connection to dustin-utecht.de closed.

So i found that gittea should run with a other user then root.

How i can fix it that i can login with (root) ssh again ?
What should i expect when i run gitea with a other user, that nothing brakes ?

Originally created by @UtechtDustin on GitHub (May 25, 2018). After install gitea i saw that the ssh login broke with the error message > TY allocation request failed on channel 0 > Hi there, You've successfully authenticated, but Gitea does not provide shell access. > If this is unexpected, please log in with password and setup Gitea under another user. > Connection to dustin-utecht.de closed. So i found that gittea should run with a other user then root. How i can fix it that i can login with (root) ssh again ? What should i expect when i run gitea with a other user, that nothing brakes ?
GiteaMirror added the type/question label 2025-11-02 04:14:23 -06:00
GiteaMirror commented 2025-11-02 04:14:24 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (May 27, 2018):

you must not use root user. It is recommended to create separate user for ex. git

@lafriks commented on GitHub (May 27, 2018): you must not use root user. It is recommended to create separate user for ex. `git`
GiteaMirror commented 2025-11-02 04:14:24 -06:00
Author
Owner
Copy Link

@hamaluik commented on GitHub (May 27, 2018):

I foolishly installed gitea under my normal user account (not root), but it still broke ssh. Now all I can do is log in under a root account. How do I revert this silly behaviour?

@hamaluik commented on GitHub (May 27, 2018): I foolishly installed gitea under my normal user account (not root), but it still broke ssh. Now all I can do is log in under a root account. How do I revert this silly behaviour?
GiteaMirror commented 2025-11-02 04:14:24 -06:00
Author
Owner
Copy Link

@daviian commented on GitHub (May 27, 2018):

You've to undo the changes under ~/.ssh/authorized_keys, such that all gitea related stuff is removed and your original ssh public key is in there.

@daviian commented on GitHub (May 27, 2018): You've to undo the changes under ~/.ssh/authorized_keys, such that all gitea related stuff is removed and your original ssh public key is in there.
GiteaMirror commented 2025-11-02 04:14:24 -06:00
Author
Owner
Copy Link

@hamaluik commented on GitHub (May 27, 2018):

Worked for me.. thanks!

@hamaluik commented on GitHub (May 27, 2018): Worked for me.. thanks!
GiteaMirror commented 2025-11-02 04:14:25 -06:00
Author
Owner
Copy Link

@UtechtDustin commented on GitHub (May 28, 2018):

@daviian
After i remove the stuff from authorized_keys, can i run gittea with a other user without permission issues ?

@UtechtDustin commented on GitHub (May 28, 2018): @daviian After i remove the stuff from authorized_keys, can i run gittea with a other user without permission issues ?
GiteaMirror commented 2025-11-02 04:14:25 -06:00
Author
Owner
Copy Link

@daviian commented on GitHub (May 28, 2018):

@Falseee
Yes that's possible. After switching user you should go to the admin panel in gitea and start the rewrite authorized_keys file job.

@daviian commented on GitHub (May 28, 2018): @Falseee Yes that's possible. After switching user you should go to the admin panel in gitea and start the rewrite authorized_keys file job.
GiteaMirror commented 2025-11-02 04:14:25 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (May 28, 2018):

Also you need to do chown -R git:git /path/to/git/repositories

@lafriks commented on GitHub (May 28, 2018): Also you need to do `chown -R git:git /path/to/git/repositories`
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 type/question
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#1824
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?