Error 500 when trying to add ed25519 ssh key #1614

New Issue

GiteaMirror · 2025-11-02T04:06:39-06:00

GiteaMirror commented

2025-11-02 04:06:39 -06:00

Originally created by @allgoewer on GitHub (Mar 9, 2018).

Gitea version (or commit ref): 1.4.0+rc2-2-g92a3061
Git version: 2.7.4
Operating system: CentOS 6
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant (try.gitea.io is offline)
Log gist: https://gist.github.com/allgoewer/5cdc94ce997b9e1e5b2eb23a5678bb64

Description

As the title says. When I try to add a ed25519 key, I get an Error 500

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMW2IwdNx+cZrptZLTa4JhtbkuJPmh0OsJRTlSWGJyrB testkey

Screenshots

Originally created by @allgoewer on GitHub (Mar 9, 2018).  - Gitea version (or commit ref): 1.4.0+rc2-2-g92a3061 - Git version: 2.7.4 - Operating system: CentOS 6 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant (try.gitea.io is offline) - Log gist: https://gist.github.com/allgoewer/5cdc94ce997b9e1e5b2eb23a5678bb64 ## Description As the title says. When I try to add a ed25519 key, I get an Error 500 ``` ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMW2IwdNx+cZrptZLTa4JhtbkuJPmh0OsJRTlSWGJyrB testkey ``` ## Screenshots ![ed25519](https://user-images.githubusercontent.com/6408150/37215632-c95b8dbe-23b8-11e8-80c6-204263af63da.png)

GiteaMirror added the type/enhancement issue/stale labels 2025-11-02 04:06:39 -06:00

GiteaMirror closed this issue

2025-11-02 04:06:40 -06:00

GiteaMirror commented

2025-11-02 04:06:40 -06:00

@ptrunk commented on GitHub (Mar 12, 2018):

I dont think it's a generic problem. I can't reproduce it in a fresh installation. I think CentOS6 is the problem here. It is pretty old with a very old OpenSSH release which does not support ed25519 keys (so far as i know).

The error 500 is not nice. Maybe the documentation should be updated to make clear that it is not a good idea to run Gitea on such old systems or even better there could be a check and a warning in the Webui if an unsupported OpenSSH version is running :-).

@ptrunk commented on GitHub (Mar 12, 2018): I dont think it's a generic problem. I can't reproduce it in a fresh installation. I think CentOS6 is the problem here. It is pretty old with a very old OpenSSH release which does not support ed25519 keys (so far as i know). The error 500 is not nice. Maybe the documentation should be updated to make clear that it is not a good idea to run Gitea on such old systems or even better there could be a check and a warning in the Webui if an unsupported OpenSSH version is running :-).

GiteaMirror commented

2025-11-02 04:06:41 -06:00

@allgoewer commented on GitHub (Mar 12, 2018):

You are absolutely right, openssh is too old. Other than the missing ed25519 support, gitea seems to work fine.

@allgoewer commented on GitHub (Mar 12, 2018): You are absolutely right, openssh is too old. Other than the missing ed25519 support, gitea seems to work fine.

GiteaMirror commented

2025-11-02 04:06:41 -06:00

@lafriks commented on GitHub (Mar 12, 2018):

Best would be to detect this when checking key and return correct error that OpenSSH server does not support such key

@lafriks commented on GitHub (Mar 12, 2018): Best would be to detect this when checking key and return correct error that OpenSSH server does not support such key

GiteaMirror commented

2025-11-02 04:06:41 -06:00

@stale[bot] commented on GitHub (Feb 5, 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 (Feb 5, 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:06:41 -06:00

@lunny commented on GitHub (Feb 6, 2019):

I'll close this now and please feel free to reopen it.

@lunny commented on GitHub (Feb 6, 2019): I'll close this now and please feel free to reopen it.

GiteaMirror commented

2025-11-02 04:06:41 -06:00

@bogdanpetrea commented on GitHub (Feb 21, 2019):

I have tried adding the deploy key provided in the issue description and it worked.
What always causes a 500 response for me is when I reuse an existing's deploy key title of the same repository, so maybe that was the issue @allgoewer experienced. It happens for any type of key, both in UI and API.

@bogdanpetrea commented on GitHub (Feb 21, 2019): I have tried adding the deploy key provided in the issue description and it worked. What always causes a 500 response for me is when I reuse an existing's deploy key title of the same repository, so maybe that was the issue @allgoewer experienced. It happens for any type of key, both in UI and API.

GiteaMirror referenced this issue

2025-11-02 11:58:44 -06:00

[PR #1614] [MERGED] update git and fix #1133 #15950

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