- 
          
 - 
                Notifications
    
You must be signed in to change notification settings  - Fork 6.2k
 
Closed
Labels
Description
Description
If there is a configuration warning, it gets somehow inserted to gitea serv <key-id> call (which is called with git over ssh access) and thus prevents any git over ssh command to work (clone, fetch, push)
~ GIT_TRACE=1 git clone ssh://gitea@*redacted*/*user*/kubespray.git             
20:20:06.841989 git.c:502               trace: built-in: git clone ssh://gitea@*redacted*/*user/kubespray.git                                                                                   
Cloning into 'kubespray'...                                                                               
20:20:06.844444 run-command.c:673       trace: run_command: unset GIT_DIR; GIT_PROTOCOL=version=2 ssh -o SendEnv=GIT_PROTOCOL -p 2222 gitea@*redacted* 'git-upload-pack '\''/*user*/kubespray.git'\'''
20:20:06.844460 run-command.c:765       trace: start_command: /usr/bin/ssh -o SendEnv=GIT_PROTOCOL -p 2222 gitea@*redacted* 'git-upload-pack '\''/*user*/kubespray.git'\'''                           
fatal: protocol error: unexpected '/10/30 20:20:07 modules/setting/mirror.go:52:loadMirrorFrom() [W] Mirror.DefaultInterval is less than Mirror.MinInterval, set to 8h0m0s                                           
01405dce75d29b0d292080f9005e1d6e5c1f48cd1171 HEAD'
Gitea Version
1.25.0
Can you reproduce the bug on the Gitea demo site?
No
Steps to reproduce:
- set some bad configuration which will produce gitea warning, for example:
 
[mirror]
DEFAULT_INTERVAL = 1h
MIN_INTERVAL = 2h
- git over ssh stops working
 
Git Version
2.43.0
Operating System
Ubuntu 24.04
How are you running Gitea?
Running in LXD container from binary release
Database
SQLite