SSH login is very slow #5033

New Issue

GiteaMirror · 2025-11-02T06:12:01-06:00

GiteaMirror commented

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

Originally created by @MicePilot on GitHub (Mar 9, 2020).

Gitea version (or commit ref):gitea-1.11.1
Git version: 2.25.0
Operating system: Windows Server 2019
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

Gitea is deployed under windows and the built-in ssh server is used, but SSH login is very slow. I think it's a DNS reverse query problem, but I can't find the place to modify the settings

Screenshots

Originally created by @MicePilot on GitHub (Mar 9, 2020).   - Gitea version (or commit ref):gitea-1.11.1 - Git version: 2.25.0 - Operating system: Windows Server 2019 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ## Description Gitea is deployed under windows and the built-in ssh server is used, but SSH login is very slow. I think it's a DNS reverse query problem, but I can't find the place to modify the settings ## Screenshots

GiteaMirror added the type/question label 2025-11-02 06:12:01 -06:00

GiteaMirror closed this issue

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

GiteaMirror commented

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

@guillep2k commented on GitHub (Mar 10, 2020):

After much digging I think you could set VerifyHostKeyDNS = no in your ssh config. But that's tricky because it should be Gitea's service user, actually. For example, if Gitea is running as "myserver\giteauser", you'd need to go to c:\users\giteauser\.ssh and create/edit a config file. There you can add the VerifyHostKeyDNS entry.

This is only just "in theory", because as I could see in the sources we're using this package https://github.com/kevinburke/ssh_config indirectly.

@guillep2k commented on GitHub (Mar 10, 2020): After much digging I _think_ you could set `VerifyHostKeyDNS = no` in your ssh config. But that's tricky because it should be Gitea's service user, actually. For example, if Gitea is running as "myserver\giteauser", you'd need to go to `c:\users\giteauser\.ssh` and create/edit a `config` file. There you can add the [`VerifyHostKeyDNS`](https://man.openbsd.org/ssh_config.5#VerifyHostKeyDNS) entry. This is only just "in theory", because as I could see in the sources we're using this package https://github.com/kevinburke/ssh_config indirectly.

GiteaMirror commented

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

@MicePilot commented on GitHub (Mar 11, 2020):

After much digging I think you could set VerifyHostKeyDNS = no in your ssh config. But that's tricky because it should be Gitea's service user, actually. For example, if Gitea is running as "myserver\giteauser", you'd need to go to c:\users\giteauser\.ssh and create/edit a config file. There you can add the VerifyHostKeyDNS entry.

This is only just "in theory", because as I could see in the sources we're using this package https://github.com/kevinburke/ssh_config indirectly.

I made these settings, but they are invalid, so I changed the server of Linux system, all the problems are gone. Thank you anyway.

@MicePilot commented on GitHub (Mar 11, 2020): > After much digging I _think_ you could set `VerifyHostKeyDNS = no` in your ssh config. But that's tricky because it should be Gitea's service user, actually. For example, if Gitea is running as "myserver\giteauser", you'd need to go to `c:\users\giteauser\.ssh` and create/edit a `config` file. There you can add the [`VerifyHostKeyDNS`](https://man.openbsd.org/ssh_config.5#VerifyHostKeyDNS) entry. > > This is only just "in theory", because as I could see in the sources we're using this package https://github.com/kevinburke/ssh_config indirectly. I made these settings, but they are invalid, so I changed the server of Linux system, all the problems are gone. Thank you anyway.

GiteaMirror commented

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

@MicePilot commented on GitHub (Mar 11, 2020):

I think of another problem. I deployed it through binary files under Linux. If I want to upgrade, can I just replace this binary file

@MicePilot commented on GitHub (Mar 11, 2020): I think of another problem. I deployed it through binary files under Linux. If I want to upgrade, can I just replace this binary file

GiteaMirror commented

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

@guillep2k commented on GitHub (Mar 11, 2020):

Yes. Please do so maintaining the same name and path. The executable path is used in the git hooks and the sshe keys. Also, make sure you use the latest release for upgrading (currently 1.11.3).

@guillep2k commented on GitHub (Mar 11, 2020): Yes. Please do so maintaining the same name and path. The executable path is used in the git hooks and the sshe keys. Also, make sure you use the latest release for upgrading (currently 1.11.3).

GiteaMirror referenced this issue

2025-11-02 14:22:24 -06:00

[PR #5029] [CLOSED] UX Optional Password & Captcha for External Registration #17602

GiteaMirror referenced this issue

2025-11-02 14:23:27 -06:00

[PR #5033] [CLOSED] UX treat register like sign in, even oauth #17604

Sign in to join this conversation.