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

can not git clone #5128

New Issue
Closed
opened 2025-11-02 06:15:16 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 06:15:16 -06:00
Owner
Copy Link

Originally created by @LanceAdd on GitHub (Mar 26, 2020).

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

Description

image

...

Screenshots

Originally created by @LanceAdd on GitHub (Mar 26, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): - Git version: - Operating system: - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: ## Description ![image](https://user-images.githubusercontent.com/22969676/77662110-6a842e80-6fb6-11ea-8b5f-654f8b97d1ea.png) ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the issue/needs-feedback label 2025-11-02 06:15:16 -06:00
GiteaMirror commented 2025-11-02 06:15:17 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (Mar 26, 2020):

What version of Gitea is this? Can you send us some logs?

@jolheiser commented on GitHub (Mar 26, 2020): What version of Gitea is this? Can you send us some logs?
GiteaMirror commented 2025-11-02 06:15:17 -06:00
Author
Owner
Copy Link

@LanceAdd commented on GitHub (Mar 29, 2020):

version:gitea-1.11.3-linux-amd64
sorry,the logs have been delete,but the new problems come,
I have add the ssh keys to the gitea,but i can't git git clone my repository by ssh。https is ok.
if i delete the ssh keys then git clone the public repository, then the same problem come.
you can try my public repository

git clone root@182.92.200.229:lanceadd/webpro.git

image

image
image

@LanceAdd commented on GitHub (Mar 29, 2020): version:gitea-1.11.3-linux-amd64 sorry,the logs have been delete,but the new problems come, I have add the ssh keys to the gitea,but i can't git git clone my repository by ssh。https is ok. if i delete the ssh keys then git clone the public repository, then the same problem come. you can try my public repository ``` git clone root@182.92.200.229:lanceadd/webpro.git ``` ![image](https://user-images.githubusercontent.com/22969676/77842297-3df13200-71c3-11ea-9265-724d03ce6278.png) ![image](https://user-images.githubusercontent.com/22969676/77842220-4eed7380-71c2-11ea-8425-427818ff8484.png) ![image](https://user-images.githubusercontent.com/22969676/77842237-7e9c7b80-71c2-11ea-873d-a6920c6f4af3.png)
GiteaMirror commented 2025-11-02 06:15:17 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Mar 29, 2020):

What happens when you ssh root@182.92.200.229? If you get a shell then you have a duplicate key in your authorized_keys. (I don't think that this is the case here but it may also provide further information.)

The invalid character '<' looking for beginning of value suggests to me that when gitea serv tries to connect to your running Gitea server it cannot. Do you have the correct LOCAL_ROOT_URL?

@zeripath commented on GitHub (Mar 29, 2020): What happens when you `ssh root@182.92.200.229`? If you get a shell then you have a duplicate key in your authorized_keys. (I don't think that this is the case here but it may also provide further information.) The `invalid character '<' looking for beginning of value` suggests to me that when `gitea serv` tries to connect to your running Gitea server it cannot. Do you have the correct `LOCAL_ROOT_URL`?
GiteaMirror commented 2025-11-02 06:15:17 -06:00
Author
Owner
Copy Link

@LanceAdd commented on GitHub (Mar 29, 2020):

@zeripath @jolheiser
The default configuration is this

 LOCAL_ROOT_URL   = http://localhost:80/

if i change it

LOCAL_ROOT_URL   = http://localhost:3000/

then
image

@LanceAdd commented on GitHub (Mar 29, 2020): @zeripath @jolheiser The default configuration is this ``` LOCAL_ROOT_URL = http://localhost:80/ ``` if i change it ``` LOCAL_ROOT_URL = http://localhost:3000/ ``` then ![image](https://user-images.githubusercontent.com/22969676/77850010-487eec00-7202-11ea-9c38-8cb77ed171f3.png)
GiteaMirror commented 2025-11-02 06:15:17 -06:00
Author
Owner
Copy Link

@LanceAdd commented on GitHub (Mar 29, 2020):

@jolheiser @zeripath
i know what happened.
The font I use makes ":" look the same in Chinese and English, but in fact, the ":" of Chinese input method is different from that of English input method. I'm sorry that I did something stupid. Thank you for your help.
You're really great

@LanceAdd commented on GitHub (Mar 29, 2020): @jolheiser @zeripath i know what happened. The font I use makes ":" look the same in Chinese and English, but in fact, the ":" of Chinese input method is different from that of English input method. I'm sorry that I did something stupid. Thank you for your help. You're really great
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 issue/needs-feedback
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#5128
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?