-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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.
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
git push using ssh key doesn't work #6938
Comments
Did you clone and push via SSH or HTTPS ? |
clone and push were done via HTTPS |
Could you check Are you running LFS? Check where the LFS is set for your clone. |
Output from git remote -v No, LFS is not used. |
Ok I'm confused - your issue title says that SSH key doesn't work but you're cloning and pushing via http. |
No, I was confused. Of course you can use authentication using SSH keys while HTTP is being used. |
[x]
):2019/05/13 22:01:54 [I] Log Mode: File(Debug)
2019/05/13 22:01:54 [I] XORM Log Mode: File(Debug)
2019/05/13 22:01:54 [I] Cache Service Enabled
2019/05/13 22:01:54 [I] Session Service Enabled
2019/05/13 22:01:54 [I] Beginning ORM engine initialization.
2019/05/13 22:01:54 [I] ORM engine initialization attempt Rename import paths: "github.com/gogits/gogs" -> "github.com/go-gitea/gitea" #1/10...
2019/05/13 22:01:55 [I] ORM engine initialization successful!
2019/05/13 22:01:55 [I] Git Version: 2.21.0
2019/05/13 22:01:55 [I] Git config user.name set to Gitea
2019/05/13 22:01:55 [I] Git config user.email set to [email protected]
2019/05/13 22:01:55 [I] SQLite3 Supported
2019/05/13 22:01:55 [I] Run Mode: Production
2019/05/13 22:01:57 [I] Listen: http://0.0.0.0:3000/git
2019/05/13 22:01:57 [I] LFS server enabled
2019/05/13 22:03:18 [D] Session ID: 9eedf4c79329c193
2019/05/13 22:03:18 [D] CSRF Token: nc5w1Pl_7AZxIh0SiEWWxW3Nd6w6MTU1Nzc4NDk5ODUzOTM5NzYzMA==
2019/05/13 22:03:18 [D] Session ID: 51b2c5c937025519
2019/05/13 22:03:18 [D] CSRF Token: PfpUkTacs2eEXdh6e390AIvYMZ86MTU1Nzc4NDk5ODYzNjQ0MjkzNg==
2019/05/13 22:04:55 [D] Session ID: 95c6160746303dde
2019/05/13 22:04:55 [D] CSRF Token: R72mpYeBNXFcAmxHy_0zhaerNfQ6MTU1Nzc4NTA5NTYyNzg5MjcxMQ==
2019/05/13 22:04:55 [D] Session ID: f6b412ea8293d149
2019/05/13 22:04:55 [D] CSRF Token: C_97jIk-Ld2Kg-d8g0xkcRFdS8w6MTU1Nzc4NTA5NTY0MTE0NzcxNw==
2019/05/13 22:04:56 [...routers/repo/http.go:211 HTTP()] [E] invalid credentials
Description
Using gitea in combination with apache mod_proxy while using HTTPS.
"git clone" using registered ssh key for authentication works correctly.
"git push" asks for password and "http.go:211 HTTP()] [E] invalid credentials" error message is written to log file.
Screenshots
N/A
The text was updated successfully, but these errors were encountered: