this post was submitted on 15 Jun 2023
139 points (97.9% liked)

Selfhosted

40747 readers
682 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
Loki
CannaVet
devve
HybridSarcasm
[email protected]
139
[SOLVED] Why is my Lemmy instance not finding other instances' communities? (self.selfhosted)
submitted 2 years ago* (last edited 2 years ago) by sdg to c/selfhosted
58 comments fedilink hide all child comments
 

Edit: YOOOOOOOO YOU CAN EDIT TITLES HERE

Anyway, you have to first search for the community in the format [[email protected]](/c/[email protected]). It doesn't show up the first time but if you mash Enter for a while it will...

Also, this FAQ linked by @[email protected] is pretty helpful and covers some of the pitfalls of being the first (or only!) person in an instance to subscribe to a community: https://lemm.ee/post/37715

Edit 2: Found https://github.com/LemmyNet/lemmy/issues/3055 requesting better support for discovering federated communities. Please consider upvoting that issue if you have a github account and think it would be helpful!

I made myself a lemmy: https://tortoisewrath.com

You may notice I am not writing to you from said lemmy... because https://tortoisewrath.com/c/[email protected] is a 404. In fact, though it appears to have federated itself with a bunch of other servers, it only appears to be able to see two communities. These were among the first few communities I tried to access ([email protected] didn't work but those two did) - since adding those two, I haven't been able to see any others, even on lemmy.ml where the first two were.

Is this normal? Do I just need to be more patient and it'll figure it out on its own, or is there some switch I need to flip to make it do the thing?

(Apologies if this is obvious to those who understand the fediverse but I have no idea what I'm doing)

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 2 years ago* (last edited 2 years ago) (2 children)

If you can read this, the Ansible playbook mostly Just Worked™ to install it on a clean Debian VPS. I actually did start over at one point because I wanted to change the domain name after learning there's not currently any way to use different domains for the UI and usernames like there is in Mastodon (relevant github issue); from that, I suspect it should be good about not clobbering anything except maybe SSL certs for existing nginx sites.

For some reason, my nginx also now seems to try to use the cert lemmy installed by default, even on a site I just set up to only listen on port 80 (http://gillen.dev). So that's kinda weird, but just installing a new cert for such a site with certbot fixes it (https://sdg.fyi).

It still seems to be struggling a little bit: votes and comments on this thread are taking a looong time to show up here (your comment just got here and it says it was from 24 minutes ago)... or maybe I'm just impatient :)

Of course, the real test will be when it comes time to update to the next Lemmy version...

[–] sirdavidxvi 4 points 2 years ago* (last edited 2 years ago)

Thanks, that's good info. If I do go forward, I was planning on going the Ansible route, though I've never used it before.

I've read that it can take a bit of time to sync when you first federate, but that after some period of time it gets closer to real-time with posts and comments.

[–] [email protected] 1 points 2 years ago

Of course, the real test will be when it comes time to update to the next Lemmy version…

it is easy enough. Simply run the playbook again. well, git pull the ansible playbook again and then run it. alternatively you can just use docker compose now on your lemmy server. I made some aliases on my lemmy instance based on what i use elsewhere. I think I got them from a linuxserver.io tutorial ages ago. you will need to adjust the container versions for this to be viable as the version is hardcoded and they only have a "latest" tag for arm.

alias dckill='docker kill $(docker ps -q)'

alias dclogs='docker-compose -f /srv/lemmy/lemmy.domain/docker-compose.yml logs -tf --tail="50" '

alias dcpull='docker-compose -f /srv/lemmy/lemmy.domain/docker-compose.yml pull'