Migrating a private gitbucket repo - could not read Username: terminal prompts disabled #14758

New Issue

GiteaMirror · 2025-11-02T11:22:12-06:00

GiteaMirror commented

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

Originally created by @blazej222 on GitHub (Jul 14, 2025).

Description

When trying to migrate a private repository from gitbucket to gitea, it fails with authentication failed: clone error: exit status 128 - fatal: could not read Username for 'http://gitbucket:8080': terminal prompts disabled
Public repos migrate just fine.

Steps to reproduce:

1.Create docker compose the same as the one I included into this report.
2.Create an empty repo on gitbucket, initialize it with README.
3.Try to migrate the repo to gitea (uncheck releases as a workaround of #35049)
4.The described error occurs

Gitea Version

1.24.2 built with GNU Make 4.4.1, go1.24.4 : bindata, timetzdata, sqlite, sqlite_unlock_notify

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

https://gist.github.com/blazej222/b15d0cd702bbc8a484fa047cbae09e30

Screenshots

No response

Git Version

2.49.0

Operating System

Windows 11

How are you running Gitea?

Docker image, here's the whole docker compose:

services:
  db:
    image: postgres:16
    container_name: gitea-db
    restart: unless-stopped
    environment:
      POSTGRES_DB: gitea
      POSTGRES_USER: gitea
      POSTGRES_PASSWORD: xxx
    volumes:
      - ./postgres:/var/lib/postgresql/data
    networks:
      - gitea-net

  gitea:
    image: gitea/gitea:latest
    container_name: gitea
    restart: unless-stopped
    environment:
      DB_TYPE: postgres
      DB_HOST: db:5432
      DB_NAME: gitea
      DB_USER: gitea
      DB_PASSWD: xxx
    volumes:
      - ./gitea:/data
    ports:
      - "3000:3000"  
      - "222:22"   
    networks:
      - gitea-net
    depends_on:
      - db
  gitbucket:
    image: gitbucket/gitbucket:latest
    container_name: gitbucket
    ports:
      - "8080:8080"  
    volumes:
      - ./gitbucket:/gitbucket
    environment:
      - GITBUCKET_HOME=/gitbucket
    restart: unless-stopped
    networks:
      - gitea-net

volumes:
  gitea-db-data:
  gitea-data:

networks:
  gitea-net:
    driver: bridge

Database

PostgreSQL

Originally created by @blazej222 on GitHub (Jul 14, 2025). ### Description When trying to migrate a private repository from gitbucket to gitea, it fails with `authentication failed: clone error: exit status 128 - fatal: could not read Username for 'http://gitbucket:8080': terminal prompts disabled ` Public repos migrate just fine. Steps to reproduce: 1.Create docker compose the same as the one I included into this report. 2.Create an empty repo on gitbucket, initialize it with README. 3.Try to migrate the repo to gitea (uncheck releases as a workaround of #35049) 4.The described error occurs ### Gitea Version 1.24.2 built with GNU Make 4.4.1, go1.24.4 : bindata, timetzdata, sqlite, sqlite_unlock_notify ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist https://gist.github.com/blazej222/b15d0cd702bbc8a484fa047cbae09e30 ### Screenshots _No response_ ### Git Version 2.49.0 ### Operating System Windows 11 ### How are you running Gitea? Docker image, here's the whole docker compose: ``` services: db: image: postgres:16 container_name: gitea-db restart: unless-stopped environment: POSTGRES_DB: gitea POSTGRES_USER: gitea POSTGRES_PASSWORD: xxx volumes: - ./postgres:/var/lib/postgresql/data networks: - gitea-net gitea: image: gitea/gitea:latest container_name: gitea restart: unless-stopped environment: DB_TYPE: postgres DB_HOST: db:5432 DB_NAME: gitea DB_USER: gitea DB_PASSWD: xxx volumes: - ./gitea:/data ports: - "3000:3000" - "222:22" networks: - gitea-net depends_on: - db gitbucket: image: gitbucket/gitbucket:latest container_name: gitbucket ports: - "8080:8080" volumes: - ./gitbucket:/gitbucket environment: - GITBUCKET_HOME=/gitbucket restart: unless-stopped networks: - gitea-net volumes: gitea-db-data: gitea-data: networks: gitea-net: driver: bridge ``` ### Database PostgreSQL

GiteaMirror added the topic/repo-migration type/bug labels 2025-11-02 11:22:12 -06:00

GiteaMirror commented

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

@lunny commented on GitHub (Jul 14, 2025):

I think it's because you haven't input right password/token.

@lunny commented on GitHub (Jul 14, 2025): I think it's because you haven't input right password/token.

GiteaMirror commented

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

@blazej222 commented on GitHub (Jul 14, 2025):

I am 100% percent positive I am inputting a right login and password combination.
In case of gitbucket, it requests only a login/password combination.
In case of github, it requires a token.

So when migrating from gitbucket, I don't even have the option to input token - only login/password.

@blazej222 commented on GitHub (Jul 14, 2025): I am 100% percent positive I am inputting a right login and password combination. In case of gitbucket, it requests only a login/password combination. In case of github, it requires a token. So when migrating from gitbucket, I don't even have the option to input token - only login/password.

GiteaMirror commented

2025-11-02 11:22:13 -06:00

@GiteaBot commented on GitHub (Aug 14, 2025):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Aug 14, 2025): We close issues that need feedback from the author if there were no new comments for a month. :tea:

GiteaMirror commented

2025-11-02 11:22:13 -06:00

@lunny commented on GitHub (Aug 14, 2025):

There is no special migration process for GitBucket. You can use the standard Git migration feature and enter your token in the password field.

@lunny commented on GitHub (Aug 14, 2025): There is no special migration process for GitBucket. You can use the standard Git migration feature and enter your token in the password field.

GiteaMirror commented

2025-11-02 11:22:13 -06:00

@blazej222 commented on GitHub (Aug 24, 2025):

If I migrate using standard Git migration feature, I won't be able to migrate releases/issues/wiki etc.

@blazej222 commented on GitHub (Aug 24, 2025): If I migrate using standard Git migration feature, I won't be able to migrate releases/issues/wiki etc.

GiteaMirror commented

2025-11-02 11:22:13 -06:00

@cboehme commented on GitHub (Sep 9, 2025):

I am expriencing the same error. I did enable debug logging and to me it looks like as if the login information is not included in the git clone command:

2025/09/09 15:42:59 modules/git/command.go:305:(*Command).run() [D] git.Command: git.Run(by:git.CloneWithArgs, repo:): D:\Git\git-current\cmd\git.exe -c protocol.version=2 -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= clone -c http.sslVerify=false --mirror --quiet -- https://`mygitbucket.example.org/gitbucket/git/MY-DEV/my-project.git .../my-dev\my-project.git

2025/09/09 15:43:00 services/task/migrate.go:60:runMigrateTask.1() [E] runMigrateTask[6] by DoerID[4] to RepoID[6] for OwnerID[4] failed: authentication failed: clone error: exit status 128 - fatal: could not read Username for 'https://mygitbucket.example.org': terminal prompts disabled

@cboehme commented on GitHub (Sep 9, 2025): I am expriencing the same error. I did enable debug logging and to me it looks like as if the login information is not included in the git clone command: ``` 2025/09/09 15:42:59 modules/git/command.go:305:(*Command).run() [D] git.Command: git.Run(by:git.CloneWithArgs, repo:): D:\Git\git-current\cmd\git.exe -c protocol.version=2 -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= clone -c http.sslVerify=false --mirror --quiet -- https://`mygitbucket.example.org/gitbucket/git/MY-DEV/my-project.git .../my-dev\my-project.git 2025/09/09 15:43:00 services/task/migrate.go:60:runMigrateTask.1() [E] runMigrateTask[6] by DoerID[4] to RepoID[6] for OwnerID[4] failed: authentication failed: clone error: exit status 128 - fatal: could not read Username for 'https://mygitbucket.example.org': terminal prompts disabled ```

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#14758