mirror of
https://github.com/go-gitea/gitea.git
synced 2026-05-22 05:15:42 -05:00
I've added my root key to gitea, but why can't I still pull code without a password? #5029
Closed
opened 2025-11-02 06:11:49 -06:00 by GiteaMirror
·
15 comments
No Branch/Tag Specified
main
release/v1.25
release/v1.24
release/v1.23
release/v1.22
release/v1.21
release/v1.20
release/v1.19
release/v1.18
release/v1.17
release/v1.16
release/v1.15
release/v1.14
release/v1.13
release/v1.12
release/v1.11
release/v1.10
release/v1.9
release/v1.8
v1.25.3
v1.25.2
v1.25.1
v1.25.0
v1.24.7
v1.25.0-rc0
v1.26.0-dev
v1.24.6
v1.24.5
v1.24.4
v1.24.3
v1.24.2
v1.24.1
v1.24.0
v1.23.8
v1.24.0-rc0
v1.25.0-dev
v1.23.7
v1.23.6
v1.23.5
v1.23.4
v1.23.3
v1.23.2
v1.23.1
v1.23.0
v1.23.0-rc0
v1.24.0-dev
v1.22.6
v1.22.5
v1.22.4
v1.22.3
v1.22.2
v1.22.1
v1.22.0
v1.23.0-dev
v1.22.0-rc1
v1.21.11
v1.22.0-rc0
v1.21.10
v1.21.9
v1.21.8
v1.21.7
v1.21.6
v1.21.5
v1.21.4
v1.21.3
v1.21.2
v1.20.6
v1.21.1
v1.21.0
v1.21.0-rc2
v1.21.0-rc1
v1.20.5
v1.22.0-dev
v1.21.0-rc0
v1.20.4
v1.20.3
v1.20.2
v1.20.1
v1.20.0
v1.19.4
v1.21.0-dev
v1.20.0-rc2
v1.20.0-rc1
v1.20.0-rc0
v1.19.3
v1.19.2
v1.19.1
v1.19.0
v1.19.0-rc1
v1.20.0-dev
v1.19.0-rc0
v1.18.5
v1.18.4
v1.18.3
v1.18.2
v1.18.1
v1.18.0
v1.17.4
v1.18.0-rc1
v1.19.0-dev
v1.18.0-rc0
v1.17.3
v1.17.2
v1.17.1
v1.17.0
v1.17.0-rc2
v1.16.9
v1.17.0-rc1
v1.18.0-dev
v1.16.8
v1.16.7
v1.16.6
v1.16.5
v1.16.4
v1.16.3
v1.16.2
v1.16.1
v1.16.0
v1.15.11
v1.17.0-dev
v1.16.0-rc1
v1.15.10
v1.15.9
v1.15.8
v1.15.7
v1.15.6
v1.15.5
v1.15.4
v1.15.3
v1.15.2
v1.15.1
v1.14.7
v1.15.0
v1.15.0-rc3
v1.14.6
v1.15.0-rc2
v1.14.5
v1.16.0-dev
v1.15.0-rc1
v1.14.4
v1.14.3
v1.14.2
v1.14.1
v1.14.0
v1.13.7
v1.14.0-rc2
v1.13.6
v1.13.5
v1.14.0-rc1
v1.15.0-dev
v1.13.4
v1.13.3
v1.13.2
v1.13.1
v1.13.0
v1.12.6
v1.13.0-rc2
v1.14.0-dev
v1.13.0-rc1
v1.12.5
v1.12.4
v1.12.3
v1.12.2
v1.12.1
v1.11.8
v1.12.0
v1.11.7
v1.12.0-rc2
v1.11.6
v1.12.0-rc1
v1.13.0-dev
v1.11.5
v1.11.4
v1.11.3
v1.10.6
v1.12.0-dev
v1.11.2
v1.10.5
v1.11.1
v1.10.4
v1.11.0
v1.11.0-rc2
v1.10.3
v1.11.0-rc1
v1.10.2
v1.10.1
v1.10.0
v1.9.6
v1.9.5
v1.10.0-rc2
v1.11.0-dev
v1.10.0-rc1
v1.9.4
v1.9.3
v1.9.2
v1.9.1
v1.9.0
v1.9.0-rc2
v1.10.0-dev
v1.9.0-rc1
v1.8.3
v1.8.2
v1.8.1
v1.8.0
v1.8.0-rc3
v1.7.6
v1.8.0-rc2
v1.7.5
v1.8.0-rc1
v1.9.0-dev
v1.7.4
v1.7.3
v1.7.2
v1.7.1
v1.7.0
v1.7.0-rc3
v1.6.4
v1.7.0-rc2
v1.6.3
v1.7.0-rc1
v1.7.0-dev
v1.6.2
v1.6.1
v1.6.0
v1.6.0-rc2
v1.5.3
v1.6.0-rc1
v1.6.0-dev
v1.5.2
v1.5.1
v1.5.0
v1.5.0-rc2
v1.5.0-rc1
v1.5.0-dev
v1.4.3
v1.4.2
v1.4.1
v1.4.0
v1.4.0-rc3
v1.4.0-rc2
v1.3.3
v1.4.0-rc1
v1.3.2
v1.3.1
v1.3.0
v1.3.0-rc2
v1.3.0-rc1
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.2.0-rc3
v1.2.0-rc2
v1.1.4
v1.2.0-rc1
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.2
v1.0.1
v1.0.0
v0.9.99
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
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
Mirrored from GitHub Pull Request
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/gitea#5029
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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?
Originally created by @pptfz on GitHub (Mar 9, 2020).
My system is centos7.7
I add the repository using SSH
git remote add origin git@10.0.0.10:pptfz/test.git
I've added my root key to gitea, but why can't I still pull code without a password?
@dacheng-gao commented on GitHub (Mar 9, 2020):
What did your get from the terminal
@pptfz commented on GitHub (Mar 10, 2020):
I've added the key, but I'm still prompted to enter the password
[root@test1 test]# git push origin master
git@10.0.0.10's password:
@lunny commented on GitHub (Mar 10, 2020):
you can try
ssh -vvv git@10.0.0.10@lunny commented on GitHub (Mar 10, 2020):
Can you confirm that you have put your private key on the right place?
@pptfz commented on GitHub (Mar 10, 2020):
I confirm that my operation is correct, because I have the same operation on github, there is no problem, this may be gitea still need some other configuration I did not complete
I just checked some information on the Internet to modify the gitea configuration file app.ini, and then added the following line under [server], START_SSH_SERVER, to enable the internal SSH service, but there is no effect after restarting gitea, the push code still prompts for the password
@lunny commented on GitHub (Mar 10, 2020):
It seems you haven't put your private key on your local machine.
@pptfz commented on GitHub (Mar 10, 2020):
I just made sure again that I created a repository on github called test, added my key to the repository, and then pushed the code using password-free methods
So it must be that I lack the relevant configuration of gitea or my configuration is not correct
@guillep2k commented on GitHub (Mar 10, 2020):
A basic question: if you enter your password.... does it complete successfully?
@guillep2k commented on GitHub (Mar 10, 2020):
@lunny,
id_rsadoes exist and is found.@pptfz commented on GitHub (Mar 10, 2020):
The way I used the SSH key should be no password input, which indicates that gitea has not been configured correctly, because my same operation is ok on github. I created a test repository on github, and then added my server key to the github repository, which is password-free login, but now it is not ok on gitea
And I entered the password as follows, but I have already executed git remote add origin git@10.0.0.10: PPTFZ /test.git
git push origin master
git@10.0.0.10 's password:
Fatal: 'PPTFZ /test.git' does not appear to be a git repository
Fatal: Could not read from remote repository.
@guillep2k commented on GitHub (Mar 10, 2020):
Could you run the following and paste the results?
@pptfz commented on GitHub (Mar 10, 2020):
[root@test1 ssh-gitea]# echo By port: ; netstat -ltnp | grep -w :22 ; echo By name: ; netstat -ltnp | grep -w gitea
By port:
tcp6 0 0 :::22 :::* LISTEN 3794/sshd
By name:
My gitea was started with docker
[root@test1 ssh-gitea]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
adfdc736b707 gitea/gitea:1.11.1 "/usr/bin/entrypoint…" 2 days ago Up About an hour 0.0.0.0:3000->3000/tcp, 0.0.0.0:222->22/tcp gitea_server_1
992eced83fa9 postgres:9.6 "docker-entrypoint.s…" 2 days ago Up About an hour 5432/tcp gitea_db_1
@guillep2k commented on GitHub (Mar 11, 2020):
I don't know much about docker, but is it possible that you're redirecting port 22 to port 222? If so, maybe you need to change your command to something like:
@stale[bot] commented on GitHub (May 10, 2020):
This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
@stale[bot] commented on GitHub (May 24, 2020):
This issue has been automatically closed because of inactivity. You can re-open it if needed.