Cloning/pulling/pushing fails multiple times before succeeding #2399

New Issue

GiteaMirror · 2025-11-02T04:34:48-06:00

GiteaMirror commented

2025-11-02 04:34:48 -06:00

Originally created by @chipsenkbeil on GitHub (Oct 10, 2018).

Gitea version (or commit ref): fc0001c
Git version: 2.19.0
Operating system: Mac 10.13.6 (client); Docker using gitea/gitea:latest image (server)
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

I'm running Gitea through Docker behind jwilder/nginx-proxy. I've exposed port 22 of the Gitea as port 2222 on my server and added my public key to my Gitea account.

Gitea is configured to work with postgres (also in a Docker container) and I followed this doc to get set up via docker-compose.

When cloning, pushing, or pulling from my Gitea instance, it fails one or more times before finally succeeding. Is there anything obvious that I should be checking to see why this is happening?

Nothing in the postgres or gitea docker container logs indicate an issue is happening.

Screenshots

Succeeds on the 4th attempt:

Below is me cloning a repo I made on the try.gitea.org website:

To remove any confusion, gcl is a git clone alias provided by a zsh plugin I'm using:

Originally created by @chipsenkbeil on GitHub (Oct 10, 2018).  - Gitea version (or commit ref): fc0001c - Git version: 2.19.0 - Operating system: Mac 10.13.6 (client); Docker using gitea/gitea:latest image (server) - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ??? ## Description I'm running Gitea through Docker behind [jwilder/nginx-proxy](https://github.com/jwilder/nginx-proxy). I've exposed port 22 of the Gitea as port 2222 on my server and added my public key to my Gitea account. Gitea is configured to work with postgres (also in a Docker container) and I followed [this doc](https://docs.gitea.io/en-us/install-with-docker/) to get set up via _docker-compose_. When cloning, pushing, or pulling from my Gitea instance, it fails one or more times before finally succeeding. Is there anything obvious that I should be checking to see why this is happening? Nothing in the postgres or gitea docker container logs indicate an issue is happening. ## Screenshots Succeeds on the 4th attempt: ![gitea clone failing](https://user-images.githubusercontent.com/2481802/46769039-6c6e0b00-ccb8-11e8-9faa-c94a5b9c19ad.gif) Below is me cloning a repo I made on the try.gitea.org website: <img width="881" alt="screen shot 2018-10-10 at 6 10 41 pm" src="https://user-images.githubusercontent.com/2481802/46769182-eacaad00-ccb8-11e8-8900-93b32bdf286e.png"> To remove any confusion, `gcl` is a git clone alias provided by a zsh plugin I'm using: <img width="274" alt="screen shot 2018-10-10 at 9 27 30 pm" src="https://user-images.githubusercontent.com/2481802/46775036-62a5d100-ccd3-11e8-8e9f-783a02b54466.png">

GiteaMirror added the type/question issue/stale labels 2025-11-02 04:34:48 -06:00

GiteaMirror closed this issue

2025-11-02 04:34:49 -06:00

GiteaMirror commented

2025-11-02 04:34:49 -06:00

@lafriks commented on GitHub (Oct 14, 2018):

Check that you don't have multiple postgresql instances running with same name in same docker network

@lafriks commented on GitHub (Oct 14, 2018): Check that you don't have multiple postgresql instances running with same name in same docker network

GiteaMirror commented

2025-11-02 04:34:49 -06:00

@stale[bot] commented on GitHub (Jan 6, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 6, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:34:50 -06:00

@techknowlogick commented on GitHub (Jan 14, 2019):

Closing issue. Please open a post in the forum if this is still an issue.

@techknowlogick commented on GitHub (Jan 14, 2019): Closing issue. Please open a post in the [forum](https://discourse.gitea.io/) if this is still an issue.

GiteaMirror referenced this issue

2025-11-02 12:09:30 -06:00

[PR #2400] [CLOSED] Fix visibility of organization repositories #16390

GiteaMirror referenced this issue

2025-11-02 12:12:01 -06:00

[PR #2600] [CLOSED] Fix repo search result #16497

GiteaMirror referenced this issue

2025-11-02 12:12:59 -06:00

[PR #2689] [MERGED] Fix repository search function #16539

Sign in to join this conversation.