github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Cloning via SSH doesn't work #971

New Issue
Closed
opened 2025-11-02 03:43:49 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 03:43:49 -06:00
Owner
Copy Link

Originally created by @kiirkegaard on GitHub (Aug 17, 2017).

  • Gitea version (or commit ref): 1.1.3
  • Git version: 2.7.4
  • Operating system: Ubuntu 16.04.2 LTS
  • Database (use [x]):
    • PostgreSQL
    • [x ] MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • [x ] Not relevant
  • Log gist:

Description

I found a few similar issues on the gog and gitea tracker, but in my case it's a fresh install.

My repositories reside in "/home/garfield/gitea-repositories/garfield/"

When trying to clone via ssh, the clone URL omits the "/home/garfield" part but displays ssh://domain.com/garfield/example.git. Which leads to the git error:


garfield@machine>git clone ssh://garfield@mydomain:222/garfield/playground.git
Cloning into 'playground'...
fatal: '/garfield/playground.git' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Adding "/home/garfield/gitea-repositories" between domain name and "garfield/example.git" makes it work.

Originally created by @kiirkegaard on GitHub (Aug 17, 2017). - Gitea version (or commit ref): 1.1.3 - Git version: 2.7.4 - Operating system: Ubuntu 16.04.2 LTS - Database (use `[x]`): - [ ] PostgreSQL - [x ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x ] Not relevant - Log gist: ## Description I found a few similar issues on the gog and gitea tracker, but in my case it's a fresh install. My repositories reside in "/home/garfield/gitea-repositories/garfield/" When trying to clone via ssh, the clone URL omits the "/home/garfield" part but displays ssh://domain.com/garfield/example.git. Which leads to the git error: ``` garfield@machine>git clone ssh://garfield@mydomain:222/garfield/playground.git Cloning into 'playground'... fatal: '/garfield/playground.git' does not appear to be a git repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. ``` Adding "/home/garfield/gitea-repositories" between domain name and "garfield/example.git" makes it work.
GiteaMirror added the type/question label 2025-11-02 03:43:49 -06:00
GiteaMirror commented 2025-11-02 03:43:50 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Aug 17, 2017):

Do you run gitea under garfield user?

@lafriks commented on GitHub (Aug 17, 2017): Do you run gitea under garfield user?
GiteaMirror commented 2025-11-02 03:43:50 -06:00
Author
Owner
Copy Link

@kiirkegaard commented on GitHub (Aug 17, 2017):

So far, yes. It's not running a service yet.

@kiirkegaard commented on GitHub (Aug 17, 2017): So far, yes. It's not running a service yet.
GiteaMirror commented 2025-11-02 03:43:50 -06:00
Author
Owner
Copy Link

@bkcsoft commented on GitHub (Aug 24, 2017):

Looks like the git-hooks are broken, can you try pressing the "rebuild git-hooks" button in the admin-panel and see if that fixes it?

@bkcsoft commented on GitHub (Aug 24, 2017): Looks like the git-hooks are broken, can you try pressing the "rebuild git-hooks" button in the admin-panel and see if that fixes it?
GiteaMirror commented 2025-11-02 03:43:50 -06:00
Author
Owner
Copy Link

@kiirkegaard commented on GitHub (Aug 25, 2017):

The problem was in the SSH-keys section in the user control panel. I previously added my keys to the authorized_keys, which apparently I should have done via the web frontend.
Afterwards the authorized_key file had to be recreated via the admin control panel.
It's working now, thanks

@kiirkegaard commented on GitHub (Aug 25, 2017): The problem was in the SSH-keys section in the user control panel. I previously added my keys to the authorized_keys, which apparently I should have done via the web frontend. Afterwards the authorized_key file had to be recreated via the admin control panel. It's working now, thanks
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
Mirrored from GitHub 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
No Label type/question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#971
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?