git密码正确还提示git Permission denied, please try again.

在gitlab上传项目的时候出现Permission denied, please try again问题。

在使用git克隆或上传项目的时候出现 git@xxx password: 让你输入密码,你发现无论输入什么都会出现Permission denied, please try again问题,其实这个主要是工程的SSH key没有加入到你的gitlab账户下。

在git中输入cd ~/.ssh/ 回车
如果提示 “ No such file or directory”,可以手动在系统路径下新建一个 .ssh文件夹即可。再输入 mkdir ~/.ssh 回车,进入.ssh路径下。

接下来在.ssh路径下配置全局的name和email,输入以下命令:
git config --global user.name “xxxxx”
git config --global user.email “xxxxx@xx.com”
此处分别指工程文件名,和gitlab账号绑定的邮箱地址。

输入:ssh-keygen -t rsa -C “xxxx@xxxx.com”(xxx为上一句输入的邮箱地址)语句,回车之后生成SSH key,后面出现让输入口令的语句,直接按回车即可,这样系统路径下就生成了两个文件:id_rsa和id_rsa.pub

打开秘钥从上面的 路径找到对应的文件

cat id_rsa.pub

复制秘钥

将生成的SSH key添加到账户里

,在SSH Keys页面里,在页面的右上角点击添加add SSH keys,将之前生成的两个文件中的id_rsa.pub文件里的内容粘贴到key文本框里,title会自动生成,再点击add key,这样key就添加成功了。
验证成功

Started by user zzl Running as SYSTEM Building in workspace /var/lib/jenkins/workspace/ruoyi The recommended git tool is: NONE using credential b3b80ec1-c9a6-4dcc-96f6-a06af4609ae3 > git rev-parse --resolve-git-dir /var/lib/jenkins/workspace/ruoyi/.git # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url git@192.168.254.11:zzl/rouyi.git # timeout=10 Fetching upstream changes from git@192.168.254.11:zzl/rouyi.git > git --version # timeout=10 > git --version # 'git version 1.8.3.1' using GIT_SSH to set credentials Verifying host key using known hosts file > git fetch --tags --progress git@192.168.254.11:zzl/rouyi.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 Checking out Revision ce3d6ec6001acce71745489686c6d74c893e5f6e (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ce3d6ec6001acce71745489686c6d74c893e5f6e # timeout=10 Commit message: "213" > git rev-list --no-walk ce3d6ec6001acce71745489686c6d74c893e5f6e # timeout=10 [ruoyi] $ /bin/sh -xe /tmp/jenkins9596733342913347267.sh + sudo ssh root@192.168.254.12 ./maven-deploy.sh Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). 192.168.254.13 /app create sucessful!!! Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). lost connection Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). 192.168.254.14 /app create sucessful!!! Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). lost connection Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). Build step 'Execute shell' marked build as failure Finished: FAILURE
08-24
### Git克隆仓库时权限被拒绝的解决方案 当遇到`git clone`命令返回`Permission denied (publickey)`错误时,这通常意味着客户端无法通过SSH密钥验证身份。为了成功执行操作,需确认几个方面: #### 1. 检查本地SSH配置 确保`.ssh`目录存在并包含有效的私钥文件(通常是`id_rsa`)。如果缺少此文件,则需要创建一对新的SSH密钥对[^3]。 ```bash ls -al ~/.ssh/ ``` #### 2. 创建或更新SSH密钥对 如果没有现成的SSH密钥对,可以通过以下命令生成新密钥,并将其添加到代理服务中以便后续使用[^4]。 ```bash ssh-keygen -t rsa -b 4096 -C "your_email@example.com" eval "$(ssh-agent -s)" ssh-add ~/.ssh/id_rsa ``` #### 3. 添加公钥至远程服务器 将生成的公钥(`id_rsa.pub`)内容复制下来,在目标Git托管平台(如GitHub/GitLab等)账户设置中的SSH Keys部分新增一条记录。 #### 4. 测试连接 完成上述步骤后,尝试再次访问远程库之前先测试一下能否顺利建立安全连接: ```bash ssh -T git@github.com ``` 对于特定情况下的Linux环境,可能还需要调整某些系统级别的参数来解决问题。 #### 5. 确认主机真实性 首次连接某个未知主机时,可能会弹出关于该主机真实性的警告对话框;此时应输入`yes`继续前进,允许保存其指纹信息以供将来识别[^5]。 以上措施应该能够有效处理大部分由SSH认证引起的问题。然而,如果仍然遭遇困难,则建议进一步排查网络状况或是联系管理员获取帮助。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值