this post was submitted on 13 Jun 2023
5 points (100.0% liked)

Selfhosted

40730 readers
664 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]
5
[Solved] Search bar on personal instance only returns local results (self.selfhosted)
submitted 2 years ago* (last edited 2 years ago) by penguin_ex_machina to c/selfhosted
13 comments fedilink hide all child comments
 

Wanted to cross post this here in case someone has had this issue before. Been dealing with this for a couple of days now.

cross-posted from: https://lemmy.world/post/94985

I set up my own personal Lemmy instance yesterday and everything seems to be up and running. I installed it on Docker with SSL enabled on a Digital Ocean droplet.

The only thing that doesn't seem to work is federated search. I can search local communities, but no matter what I do I can't get it to recognize other instances. I've tried:

And nothing shows up. I've tried the same search terms multiple times over the past day or so and nothing is changing. My instance has federation and federation debugging enabled (although I can't figure out where the federation debugging outputs yet, because nothing in console log changes), and as far as I can tell there are no errors in the Docker logs that could point me in a specific direction. Where can I start looking to properly debug this?

EDIT: I needed to expose my lemmy backend to the proxy network. This answer here helped me get to the solution. Thanks so much! https://lemmy.world/comment/150173

top 12 comments
sorted by: hot top controversial new old
[–] [email protected] 4 points 2 years ago (1 children)

I have a simmilar problem, but I found out when you search for [email protected] then wait a second and go to the Communities tab and choos "All" then you will see the one you searched for in the list and then you can subscribe to it.

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

yeah, sometimes just refreshing (or waiting) on the search window works, and then a instance friendly link will show up

[–] [email protected] 3 points 2 years ago* (last edited 2 years ago) (1 children)

Check sudo docker logs lemmy_lemmy_1 right after you search. I was getting http get request failures to the other servers.

Add 'lemmyexternalproxy' to networks for the lemmy service in docker-compose.yml and rebuild 'sudo docker-compose up -d --build'

Fixed it for me.

Edit: just read the part about nothing in the logs. If this is not it, I'm not sure.

[–] penguin_ex_machina 3 points 2 years ago (1 children)

I'm almost positive that network is already there but I'm definitely going to check the Lemmy-specific logs. I only knew how to check the general server logs when I last looked at it. If I ever get my kid to bed I'll take another look.

[–] [email protected] 2 points 2 years ago (1 children)

Might be, the current docker-compose.yml has it in there properly. However, when I used the install with docker guide a day or two ago it hard linked to the 0.17 version which didn't give external network access to the lemmy service. Sounded similar to the problem I was facing, but if you used the current docker-compose.yml I guess that is not it.

It sounds like the back end has no external network access. You can check with something like sudo docker exec -it lemmy_lemmy_1 ping archlinux.org

[–] penguin_ex_machina 3 points 2 years ago (1 children)

!!!! THAT DID IT.

Thank you so much I would have never gotten to that solution on my own. Works beautifully now.

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

Awesome! No problems, I'm glad I could help. Took me a bit to figure out what was going on too.

[–] PriorProject 2 points 2 years ago

Have you read option two of finding a community in https://lemmy.blahaj.zone/post/61827 and followed the steps there exactly? Lemmy's search for remote communities is pretty confusing and there are lots of ways to get an empty resultset for no good reason. That post will get you on the golden path if that's your issue though.

[–] [email protected] 1 points 2 years ago (1 children)

Try searching either way and wait. At first it will show "No results" or similar but after about 10 seconds it should go away. Then either the result will show, or you need to change selector to "Local" (its a bug). But you need to wait for "No results" to go away.

[–] penguin_ex_machina 1 points 2 years ago (2 children)

"No results" never goes away though. I've straight up left it and walked away for like 10 min and no change. That's why I'm starting to wonder if it's an issue with my instance.

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

Yeah it might very well be. Check here for possible help.

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

My current flow is: search "[email protected]", wait a few seconds, browse to https://ymmel.nl/c/[email protected] - when it opens I'm able to subscribe.

load more comments
view more: next ›