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
I used the docker-compose file from the official github repo: https://github.com/LemmyNet/lemmy/blob/main/docker/docker-compose.yml
But after the comment from @[email protected] I changed it to pull the image from dockerhub instead of building it myself. Now it pulls correctly and the server comes online but is almost unusable. The homepage displays but I cannot login as admin or create a new user :/
Edit: Here is the docker-compose.yml I used
3rd reply :)
Have you edited your lemmy.hjson yet to ensure details match the docker-compose.yml? The instructions for that part are not very clear and I had to do lots of trial and error to get it working.
Don't pull dev use 0.17.4
lemmy: image: dessalines/lemmy:dev
lemmy: image: dessalines/lemmy:0.17.4
Also in your Pictrs environment you may need:
- PICTRS__SERVER__ADDRESS=0.0.0.0:8080
Lastly did you do the following before runing your docker-compose up -d cmd?
mkdir -p volumes/pictrs sudo chown -R 991:991 volumes/pictrs
Also, @[email protected], what does your nginx.conf look like? Now that the webpage is loading, the backend might be blocked/not configured properly in nginx, so nginx isn't properly forwarding requests to the backend.
I had a similar issue, use a more recent version of the lemmy-ui image. I used "latest" and it worked
2nd reply, can you also post the logs from the lemmy-lemmy-1, lemmy-lemmy-ui-1, lemmy-postgres-1, and lemmy-pictrs-1 containers?
I found most of my issues were dealing with communication between networks and IP's binding wrong which wont show anywhere but in the logs as connection issues.