From a45abe3cf9d6e2934e6d6792d58a4bdb8a20408e Mon Sep 17 00:00:00 2001 From: Cal Corum Date: Sat, 28 Feb 2026 16:10:33 -0600 Subject: [PATCH] =?UTF-8?q?store:=20Gitea=20SSH=20push=20fails=20with=20pa?= =?UTF-8?q?ssword=20prompt=20=E2=80=94=20use=20HTTPS=20instead?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- ...assword-prompt-use-https-instead-5994fe.md | 34 +++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 graph/solutions/gitea-ssh-push-fails-with-password-prompt-use-https-instead-5994fe.md diff --git a/graph/solutions/gitea-ssh-push-fails-with-password-prompt-use-https-instead-5994fe.md b/graph/solutions/gitea-ssh-push-fails-with-password-prompt-use-https-instead-5994fe.md new file mode 100644 index 00000000000..6744a5be158 --- /dev/null +++ b/graph/solutions/gitea-ssh-push-fails-with-password-prompt-use-https-instead-5994fe.md @@ -0,0 +1,34 @@ +--- +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:10:33.357713+00:00" +--- + +# 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`.