Selfhosted

40041 readers

675 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:

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!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

[Solved] Search bar on personal instance only returns local results (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by penguin_ex_machina@lemmy.world to c/selfhosted@lemmy.world

7 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:

Searching with the bang prefix (ie, !lemmy_support@lemmy.ml)

Searching with the whole URL (https://lemmy.ml/c/lemmy_support)

Keywords ("lemmy support")

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 6 comments

sorted by: hot top controversial new old

[–] jeena@jemmy.jeena.net 4 points 1 year ago (1 children)

I have a simmilar problem, but I found out when you search for !communit@example.com 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.

[–] arp@lemmy.studio 1 points 1 year ago

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

[–] cyps@typemi.me 1 points 1 year ago* (last edited 1 year 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@lemmy.world 1 points 1 year 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.

[–] cyps@typemi.me 1 points 1 year 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@lemmy.world 1 points 1 year ago

!!!! THAT DID IT.

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

load more comments