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

Submitted ⁨⁨6⁩ ⁨months⁩ ago⁩ by ⁨galaxy_nova@lemmy.world⁩ to ⁨selfhosted@lemmy.world⁩

So I initially had been using gitea. It took me a while to get ssh to work properly but then it did. Then I learned of forgejo and decided to go full foss. Only problem is that i cant get ssh to work for the life of me. Here’s my setup

Forgejo is in a docker compose file in which I’ve setup a docker network
My ssh port for my server is not 22
I followed the gitea sshing shim directions I used previously to a T and couldn’t get any sort of anything to work

My best guess is there’s some base configuration difference between the two that I don’t know of that maybe somebody here can point out for me. Any help would be appreciated, thanks.

source

Comments

Sort:hotnew top

bruce965@lemmy.ml ⁨6⁩ ⁨months⁩ ago

Here’s my config for reference, which works for me:

name: forgejo
services:
  forgejo:
    image: codeberg.org/forgejo/forgejo:12
    environment:
      - USER_UID=1000
      - USER_GID=1000
    restart: always
    volumes:
      - ./data:/data
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    ports:
      - 80:3000
      - 2222:22

If you can share your error message we might be able to better pinpoint the issue.

source

suzune@ani.social ⁨6⁩ ⁨months⁩ ago
It would help if you explain “it does not work” further. It’s a bad desciption of the situation and we cannot look directly at your installation.

source
- galaxy_nova@lemmy.world ⁨6⁩ ⁨months⁩ 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
  - frongt@lemmy.zip ⁨6⁩ ⁨months⁩ ago
    What’s in the log on the server?
    
    source
    -> View More Comments
  - doeknius_gloek@discuss.tchncs.de ⁨6⁩ ⁨months⁩ 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
    -> View More Comments
  - suzune@ani.social ⁨6⁩ ⁨months⁩ 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
    -> View More Comments