this post was submitted on 06 Mar 2026
12 points (92.9% liked)

Selfhosted

57238 readers
468 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I run a SearXNG instance and rate limiting has never been a issue until now. so i wanted to ask what the cheapest and most privacy respecting vpn/proxys are to use.

you are viewing a single comment's thread
view the rest of the comments
[–] potatoguy@mbin.potato-guy.space 5 points 9 hours ago (1 children)

On the vpn/proxy idk, I think the bots would pass through it.

There are some nginx blocklists like the ultimate bad bot blocker, I could share my Cloudflare rules if you want it, as these are rules, it can be abstracted to anywhere.

[–] SteveTech@aussie.zone 4 points 8 hours ago

Nginx also has support for rate limiting built in.

On the topic of blocking, I block useragents starting with Mozilla/5.0 that are using HTTP/1.X, since all modern browsers default to HTTP/2.0 and anything else is usually always bad bots. You can also return 426 with the Upgrade: h2c header to let some older browsers know to use HTTP/2.0.