msampaio Hi all, I am trying to configure SSH on Gitea and have problems cloning repositories over SSH despite successfully cloning over HTTP. I followed Gitea FAQ (https://docs.gitea.io/en-us/faq/#ssh-issues), tried to connect to Gitea via SSH (ssh git@myremote.example), and had access to my server shell at Opalstack. According to FAQ, as I didn't get the message below, my "SSH key is not being managed by Gitea." Hi there, You've successfully authenticated, but Gitea does not provide shell access. If this is unexpected, please log in with password and setup Gitea under another user. How do I fix this? Thanks, Marcos
msampaio I found the problem: I used the same SSH key pair to access the server shell and clone the repo. I solved the problem by creating a new SSH key pair to be used only with the repo. I followed these instructions: https://betterprogramming.pub/how-to-set-up-multiple-ssh-keys-ae6688f76570.
HelenaGwyn sean I followed these instructions, but I'm getting a timeout. If my domain is projects.domain.ext, the Host is projects.domain.ext and the keyname is gitea_projects_domain_ext_rsa?
sean HelenaGwyn It's unlikely that a key issue is causing a timeout, but to answer your questions: the Host is projects.domain.ext Yes. the keyname is gitea_projects_domain_ext_rsa The keyname can be whatever you want. Just be sure that you're using the same keypair in steps 1-3.
HelenaGwyn sean What could be causing the timeout? I didn't change anything extra to the app.ini. Cloning with HTTPS works. The message I'm getting is ssh: connect to host projects.domain.ext port 22: Operation timed out fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
sean HelenaGwyn from your description it seems to me like your IP address has been blocked, perhaps due to SSH login failures. If you'd like us to look into it then please email support to let us know your public IP address.
