Comment on Can’t get SSHing shim to work with forgejo for the life of me

suzune@ani.social ⁨4⁩ ⁨days⁩ ago

• galaxy_nova@lemmy.world ⁨4⁩ ⁨days⁩ ago

  Ok. The issues lies somewhere in the actually connection. Adding ssh keys to my instance shows up properly in the known keys. Whenever I attempt to connect either on the actual server itself as a test or via trying to clone over ssh or even connect via ssh itself I get public key denials. If you want I can provide you my ssh config on sever, my docked compose file, the verbose output of the ssh connections in various facets although they haven’t appeared to be very helpful, or whatever else can be helpful

  source

  • doeknius_gloek@discuss.tchncs.de ⁨4⁩ ⁨days⁩ ago

    Check the permissions/owner of the authorized_keys file. I’m not at home right now to give you the path to it, but I have had a similar problem after I add a new ssh key to my gitea/forgejo account. It often turns out that in doing so, sometime the permissions change and gitea/forgejo then refuses to use the file.

    In my case the problem is probably rooted within the uid/gid thats used inside the container and/or the nfs mount I use for the container volume. I never bothered to get to the bottom of it though.

    source

    • galaxy_nova@lemmy.world ⁨3⁩ ⁨days⁩ ago

      I did check that first after a lot of googling and I think everything is all set there

      source
  • suzune@ani.social ⁨4⁩ ⁨days⁩ ago

    So sshd is running. The first question is: is it running on the port you expect it to run? The main host can have sshd too and maybe you connect to the wrong port? Did you use a ~/.ssh/config for your forgejo connection?

    source

    • galaxy_nova@lemmy.world ⁨3⁩ ⁨days⁩ ago

      I don’t have an explicit config file no, I don’t remember needing it before though. I’ve followed the steps https://docs.gitea.com/installation/install-with-docker which worked with gitea but doesn’t work with forgejo. I didn’t see anything that mentioned needing a config for the first method listed there at least. I suppose I could try some of the other methods listed there but I liked option A the best generally.

      source

      • suzune@ani.social ⁨3⁩ ⁨days⁩ ago

        If you have forgejo or gitea ssh running on port 222, you need to specify it somewhere. Or else git could connect to port 22, which is default for ssh.

        source
  • frongt@lemmy.zip ⁨4⁩ ⁨days⁩ ago

    What’s in the log on the server?

    source

    • galaxy_nova@lemmy.world ⁨3⁩ ⁨days⁩ ago

      Logs for what the container?

      source