is it problem? #7062

Closed
opened 2025-11-02 07:14:45 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @igor9292 on GitHub (Mar 24, 2021).

  • Gitea version (or commit ref):1.11.6 and 1.13.5
  • Git version: 2.22
  • Operating system:
    RHEL, start systemd
  • Database (use [x]):
    • [x ] PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
  • Log gist:
    in log only one select...

what changed? I upgraded from version 1.11.6 to 1.13.5, and I cannot copy the public repository from the server (git archive).
Gitea: Unauthorized
Your account is disabled.
fatal: The remote end hung up unexpectedly

on version 1.11.6 - all good

Originally created by @igor9292 on GitHub (Mar 24, 2021). - Gitea version (or commit ref):1.11.6 and 1.13.5 - Git version: 2.22 - Operating system: RHEL, start systemd - Database (use `[x]`): - [x ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - Log gist: in log only one select... what changed? I upgraded from version 1.11.6 to 1.13.5, and I cannot copy the public repository from the server (git archive). Gitea: Unauthorized Your account is disabled. fatal: The remote end hung up unexpectedly on version 1.11.6 - all good
GiteaMirror added the issue/needs-feedback label 2025-11-02 07:14:45 -06:00
Author
Owner

@techknowlogick commented on GitHub (Mar 25, 2021):

Please fill out the standard issue form as that information is being requested so we can help you. Logging which is also requested via the standard issue form is necessary for us to provide any assistance: https://docs.gitea.io/en-us/logging-configuration/#debugging-problems

@techknowlogick commented on GitHub (Mar 25, 2021): Please fill out the standard issue form as that information is being requested so we can help you. Logging which is also requested via the standard issue form is necessary for us to provide any assistance: https://docs.gitea.io/en-us/logging-configuration/#debugging-problems
Author
Owner

@igor9292 commented on GitHub (Apr 6, 2021):

The problem turned out to be the following: if the key is loaded, and the user is no longer active, you cannot re-upload the key to gitea. Is this a bug or a feature? Maybe deactivate the keys of inactive users?

@igor9292 commented on GitHub (Apr 6, 2021): The problem turned out to be the following: if the key is loaded, and the user is no longer active, you cannot re-upload the key to gitea. Is this a bug or a feature? Maybe deactivate the keys of inactive users?
Author
Owner

@igor9292 commented on GitHub (Apr 6, 2021):

In general, it would not be bad for the administrator to do something like administering ssh keys so that he can delete, add, modify for each user

@igor9292 commented on GitHub (Apr 6, 2021): In general, it would not be bad for the administrator to do something like administering ssh keys so that he can delete, add, modify for each user
Author
Owner

@zeripath commented on GitHub (Jun 23, 2021):

There's another issue suggesting this. So I think we can close this.

@zeripath commented on GitHub (Jun 23, 2021): There's another issue suggesting this. So I think we can close this.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#7062