46 lines
1.4 KiB
Markdown
46 lines
1.4 KiB
Markdown
---
|
|
id: 5994fea1-f787-41a3-ad5b-0f3349c00343
|
|
type: solution
|
|
title: "Gitea SSH push fails with password prompt — use HTTPS instead"
|
|
tags: [gitea, git, ssh, workaround, networking, homelab]
|
|
importance: 0.5
|
|
confidence: 0.8
|
|
created: "2026-02-28T22:10:33.357713+00:00"
|
|
updated: "2026-02-28T22:11:08.332788+00:00"
|
|
relations:
|
|
- target: a41644f1-2dd1-4706-8fc8-e2242c1702cb
|
|
type: CAUSES
|
|
direction: incoming
|
|
strength: 0.8
|
|
edge_id: 896c5f7c-6b09-4eab-b697-064f92d7f882
|
|
- target: d326094f-63eb-4b42-8aa6-f2d53d6f2628
|
|
type: RELATED_TO
|
|
direction: outgoing
|
|
strength: 0.7
|
|
edge_id: ae71b8bf-3993-4ca6-90a4-b5a3a8f5b46a
|
|
---
|
|
|
|
# Gitea SSH Push Failure Workaround
|
|
|
|
## Problem
|
|
`git push` via SSH to `git@git.manticorum.com` fails with a password prompt rather than authenticating with a key.
|
|
|
|
## Root Cause
|
|
`~/.ssh/config` has a `gitea` alias pointing to host `10.10.0.225` as `root` using `homelab_rsa`. However this alias uses the hostname `gitea`, not `git.manticorum.com`, so git's SSH format (`git@git.manticorum.com`) does not match the config entry.
|
|
|
|
## Workaround
|
|
Use HTTPS URL instead:
|
|
```
|
|
https://git.manticorum.com/cal/repo.git
|
|
```
|
|
HTTPS works without auth issues.
|
|
|
|
## Proper Fix (TODO)
|
|
Add an SSH config entry for the git hostname:
|
|
```
|
|
Host git.manticorum.com
|
|
User git
|
|
IdentityFile ~/.ssh/homelab_rsa
|
|
```
|
|
Or update the remote URL to use the `gitea` alias: `git@gitea:cal/repo.git`.
|