User Authentication Error During Gitea Repository Migration #13672

New Issue

GiteaMirror · 2025-11-02T10:49:51-06:00

GiteaMirror commented

2025-11-02 10:49:51 -06:00

Originally created by @SmartVDS on GitHub (Nov 4, 2024).

Description

I am facing an issue while attempting to migrate a repository from one Gitea instance to another. Both Gitea instances are running inside Docker containers, set up using a docker-compose file as mentioned in Gitea's installation documentation.

However, during the migration process, I encountered an error related to user authentication.

I am using the same user account on both the source and target Gitea servers, which are configured to use LDAP credentials from the same Active Directory. Additionally, I have a valid authentication token with the necessary permissions. I have tried using tokens with various permission combinations, but the issue persists.

Relevant log entries have been included for reference.

Gitea Version

1.22.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.45.2

Operating System

Alpine Linux

How are you running Gitea?

Docker container

Database

SQLite

Originally created by @SmartVDS on GitHub (Nov 4, 2024). ### Description I am facing an issue while attempting to migrate a repository from one Gitea instance to another. Both Gitea instances are running inside Docker containers, set up using a docker-compose file as mentioned in [Gitea's installation documentation](https://docs.gitea.com/installation/install-with-docker). ![image](https://github.com/user-attachments/assets/e3a2b6ff-0c39-4968-bd90-af572574664c) However, during the migration process, I encountered an error related to user authentication. ![image](https://github.com/user-attachments/assets/a4f87eaa-43a5-4d35-b3b5-06895bbc8d4e) I am using the same user account on both the source and target Gitea servers, which are configured to use LDAP credentials from the same Active Directory. Additionally, I have a valid authentication token with the necessary permissions. I have tried using tokens with various permission combinations, but the issue persists. Relevant log entries have been included for reference. ![image](https://github.com/user-attachments/assets/71066941-7f3f-4727-9823-a948af26fe2a) ### Gitea Version 1.22.3 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.45.2 ### Operating System Alpine Linux ### How are you running Gitea? Docker container ### Database SQLite

GiteaMirror added the topic/authentication topic/repo-migration type/bug labels 2025-11-02 10:49:51 -06:00

GiteaMirror commented

2025-11-02 10:49:52 -06:00

@yp05327 commented on GitHub (Nov 5, 2024):

After checking the code, I can only image it will return version error, but not user does not exist error. Where does it come from? 🤔

@yp05327 commented on GitHub (Nov 5, 2024): After checking the code, I can only image it will return version error, but not user does not exist error. Where does it come from? 🤔

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#13672