-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
DS918+ - Impossible to clone / pull / push via SSH Gitea #12755
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Here my ssh log : OpenSSH_8.2p1 Ubuntu-4ubuntu0.1, OpenSSL 1.1.1f 31 Mar 2020 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Ok ignore my first few comments. Could you please explain which server is intended to service SSH requests? Is it Gitea's internal SSH server or an openSSH server that is running on Synology. Gitea can run its own SSH server or it can integrate with an already running openSSH server.
Which is it? |
Assuming you actually intend to use openSSH get rid of the Now, searching for this exact bug implies that there might be some firewall rules that your Synology has. https://www.nas-forum.com/forum/topic/56853-r%C3%A9solussh-permission-denied-connection-closed/
Implying that these might be the problem but read the earlier comments in that thread in case there's something else missing. |
Hi, I tried to deactivate SSH in DSM Panel to use gitea SSH server and now, the SSH connection failed. I tried to change SSH port to : OpenSSH_8.2p1 Ubuntu-4ubuntu0.1, OpenSSL 1.1.1f 31 Mar 2020 The Synology's Firewall is currently deactivated but it's change nothing. |
I deleted the START_SSH_SERVER line too, stop and restart Gitea service, but nothing change |
Here my complete app.ini file : APP_NAME = Gitea: Näser repo
RUN_USER = gitea
RUN_MODE = prod
[oauth2]
JWT_SECRET = <hidden>
[security]
INTERNAL_TOKEN = <hidden>
INSTALL_LOCK = true
SECRET_KEY = <hidden>
[database]
DB_TYPE = mysql
HOST = 127.0.0.1:3307
NAME = gitea
USER = gitea
PASSWD = xxxxxxxxx
SCHEMA =
SSL_MODE = disable
CHARSET = utf8
PATH = /usr/local/gitea/gitea/data/gitea.db
[repository]
ROOT = /usr/local/gitea/gitea/gitea-repositories
[server]
SSH_DOMAIN = domain.local
DOMAIN = domain.local
HTTP_PORT = 8080
ROOT_URL = https://domain.local/
DISABLE_SSH = false
SSH_PORT = 7999
LFS_START_SERVER = true
LFS_CONTENT_PATH = /usr/local/gitea/gitea/data/lfs
LFS_JWT_SECRET = <hidden>
OFFLINE_MODE = false
BUILTIN_SSH_SERVER_USER =
SSH_LISTEN_PORT = %(SSH_PORT)s
SSH_CREATE_AUTHORIZED_KEYS_FILE = true
[mailer]
ENABLED = true
HOST = mail.infomaniak.com
FROM = [email protected]
USER = [email protected]
PASSWD = xxxxxxxxxxxxxx
[service]
REGISTER_EMAIL_CONFIRM = true
ENABLE_NOTIFY_MAIL = true
DISABLE_REGISTRATION = false
ALLOW_ONLY_EXTERNAL_REGISTRATION = false
ENABLE_CAPTCHA = false
REQUIRE_SIGNIN_VIEW = true
DEFAULT_KEEP_EMAIL_PRIVATE = false
DEFAULT_ALLOW_CREATE_ORGANIZATION = true
DEFAULT_ENABLE_TIMETRACKING = true
NO_REPLY_ADDRESS = noreply.localhost
[picture]
DISABLE_GRAVATAR = false
ENABLE_FEDERATED_AVATAR = true
[openid]
ENABLE_OPENID_SIGNIN = true
ENABLE_OPENID_SIGNUP = true
[session]
PROVIDER = file
[log]
MODE = file
LEVEL = info
ROOT_PATH = /usr/local/gitea/gitea/log |
If I had this person's concern, the classic SSH connection should be refused too, right? |
Here all files : /var/packages/Gitea/target/gitea : /var/packages/Gitea/target/gitea/.ssh/ : /etc/ssh/sshd_config : |
@zeripath Do you have any idea ? What have I missed ? |
okay... weird ! Thanks a lot @zeripath to helped me ! |
[x]
):Description
As this issue, I cannot clone, pull / push via SSH Gitea on my Synology
I did all the steps described in the ticket 5497, but I have this error :
`
git clone ssh://[email protected]:7999/xxxxxx/project-example.git
Clonage dans 'project-example'...
Permission denied, please try again.
fatal: Impossible de lire le dépôt distant.
Veuillez vérifier que vous avez les droits d'accès
et que le dépôt existe.
`
But when i try to clone by HTTP mode, it's working perfectly.
What I have done :
I installed Gitea on my Synology by following these steps :
Here my app.ini :
The text was updated successfully, but these errors were encountered: