Anyone here running their own #searXNG instance?
Curious to know how 'hands-on' the administrator needs to be with it, e.g., do you need to switch IP addresses often to avoid rate limiting?
0 Boosts
0 Likes
@joel
Thanks - this is super helpful 🙏
Thanks - this is super helpful 🙏
@patatas I haven't had to do any IP address switching, but then again it's a single user instance.
@patatas I host one but hardly anyone uses it so I've never had to roll the ip address because of rate limiting. How many users / queries an hour are you expecting?
@patatas
it depends on the day.
Updates can be required from once a week to once a month, depending on issues with remote engines.
For public instance, you don’t need extra outgoing IPs if you deal with bots incoming requests. If you don’t set up something to limit broken requests, you get quickly blocked by remote engine. There is any antibot feature shipped in but it has only a limited effect on incoming ship. I had to setup a log parser that identifies incoming shit and block IPs at the firewall level.
I have not found a way, via Tor or VPN, to use a different IP for each outgoing requests. I haven’t tested Web proxy offers.
If you use a non-public / private #SearXNG instance, you only have to update the software from time to time; when it starts bugging.
@tag-searxng