225
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 Jun 2023
225 points (97.5% liked)
Selfhosted
38702 readers
149 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:
-
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:
- 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!
founded 1 year ago
MODERATORS
Appreciate if you guys shared some guides on setting it up. I’m not new to selfhosting but tried setting it up and failed with strange errors all day long :(
Not sure if you got it sorted or not, but if you were following the docker-compose method documented by the devs, there were a couple hurdles I ran into. The one that may be relevant here is that at some point their
docker-compose.ymldid not expose the Lemmy backend to the Internet, and so all federation was failing. That said, I checked just now and they seem to have fixed that issue upstream. So you should be able to re-pull theirdocker-compose.ymland it should work.I will try that, thank you.
I would suggest joining us on the Lemmy matrix space, particularly the "Lemmy Instance Admin" channel. It's much easier to help in semi-real time.
No worries, this is a fairly complex piece of software. If you really want to though, try copy pasting your errors into chatgpt if you can. While not perfect, it usually can give you an idea of what steps are going wrong. Some of us can help you too, but it's no pressure. Being a part of the community is more than just the machines, it's the friends we made along the way.
I think it would be better if @marsta@beehaw.org would post the errors so the solution to his problems is documented in case someone else has a similar problem.
This way we could google problems and just add lemmy instead of reddit to find a proper solution.
Of course, the most important aspect of fixing a problem, is writing down how you fixed it. Never know what a different, but similar problem might crop up again. Sometimes getting a quick answer, or having a human readable explanation for an error goes a long way. Often enough I'll have complex logs entries that I can't parse what the problem actually is, I can quick copy paste and get a normal people paragraph. Sometimes "os: error (-4) aborting" actually just means you forgot to change user permissions on your volume folder. In a perfect world, all program's logs would be perfectly readable by machines and people at the same time. :P
It was mainly around this error: https://github.com/LemmyNet/lemmy/issues/2278