this post was submitted on 10 Sep 2025
31 points (89.7% liked)

Selfhosted

51408 readers
807 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
CannaVet@lemmy.world
Loki@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
31
Can’t get SSHing shim to work with forgejo for the life of me (lemmy.world)
submitted 4 days ago by galaxy_nova@lemmy.world to c/selfhosted@lemmy.world
11 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] seang96@spgrn.com 1 points 3 days ago

If public key is denied forgejo is setup, but you have an old connection in your authorized_keys file probably form using gitea. Remove the line, it should prompt you to accept public key on next ssh session. This is a basic ssh functionality probably why you were downvoted I guess.

Gitea and forgejo configs were 100% same at some point,, check forgejo news for when the last version that supported gitea migrations. That said it should still be pretty close.