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

Selfhosted

38886 readers
139 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 1 year ago
MODERATORS
 

I self-host a SearXNG instance that is public facing. On a VPS. I share it with friends and family, and I do not mind if some strangers use it as well.

What I'm afraid of is getting my IP rate limited or even blacklisted by search engines. I would like to keep the instance public facing for UX reasons (no VPN, no SSO).

I enabled SearXNG internal limiter, which I'm not sure what it does.

Additionally, I am rate limiting at the reverse proxy level (Caddy) as follows:

rate_limit {remote.host} 10r/s
rate_limit {path.*} 50r/s

That is, 10 requests per second for a single IP address, and 50 requests per second in general. 

Would you have improvements to suggest  me, or further measures I could take?

Edit: I’m not using Cloudflare or any similar solution and I want to avoid it.

no comments (yet)
sorted by: hot top controversial new old
there doesn't seem to be anything here