Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
If it's reaponding about the git user, then it's an auth failure. That's about all I could tell you without some logs.
Yeah and I figured that was the case. I'm just trying to figure out the best practice for my use case would be as I'd rather not have to build a new container. Also I've included the vvverbose output of the SSH attempt below.
You've got a lot of errors in there, and it's hard to tell which may be the culprit. I'm going to guess your keys can't be read. I'd go back through the setup steps and make sure your PUBLIC key is setup properly for the git user.
Well that's the thing, there's no git user. I'm trying to directly ssh into the gogs container through the tailscale sidecar container via the tailnet, so I'm not going through the host machine. I'm just trying to see if there's a way I can do it that's a bit less fiddly than having to rebuild the container with the right user and whatnot.