Add https://search.2-a.net

[hzm170]

Requirements (make sure to read all of them)

• It is my instance. I bought the domain myself and I own this domain. Free domains (e.g. Freenom) and shared domains (e.g. noip.com) are not allowed.
• I give the right to check.searx.space to check my instance (every 3 hours for the response times, every 24 hours for the other tests).
• I acknowledge that managing a public instance is not an easy task and require spending time to keep the instance in good health. E.g. look after your instance by using a monitoring system.
• I guarantee to keep an uptime per month of my instance at minimum 90%. Please ask for a removal of your instance if there is a planned long downtime or notify us here for a short downtime.
• I do not track the users of my instance with any analytics or tracking software.
• I won't try to manipulate the ranking of my instance in a way that give an unfair advantage over the other public instances in the list. (e.g. caching requests for searx.space server)
• I control the final webserver (software) that is serving the requests to the users of my instance. Here is a non-exhaustive list of forbidden hosting types: Cloudflare, PaaS, managed (hosting provider controlled) HTTP(S) load balancer (e.g. AWS ALB), shared Web hosting. TCP load balancer is fine. Cloudflare DNS only (grey cloud) is fine.
• If needed, I can restrict users from accessing my instance for the only sole reason of keeping my instance in working conditions for the other users (detailed description - evidence need to be provided when asked). Other means of restriction is forbidden.

Bot protection requirement

• Yes I have configured the server.public_instance parameter.

Source code URL

No response

Comment

No response

[github-actions]

Please consider joining our Matrix room for public instance maintainers by joining our Matrix room: https://matrix.to/#/#searxng:matrix.org
then pinging @ unixfox, @ dalf and @ mrpaulblack for asking to be invited to the Matrix room.
We discuss troubles managing a public instance, sharing some advices (like how to protect against bots), announcing big changes in searxng and more.

[unixfox]

Please configure the parameter server.public_instance: #417

[hzm170]

Please configure the parameter server.public_instance: #417

i did how ever it's crashing the system and everything is config right.. is there bug or file missing from it?

[unixfox]

what do you mean by crashing the system? the whole system? or just searxng?

check your logs...

[hzm170]

what do you mean by crashing the system? the whole system? or just searxng?

check your logs...

it's crashing the docker system, from what the logs says

Respawned uWSGI worker 4 (new pid: 229) spawned 4 offload threads for uWSGI worker 7 spawned 4 offload threads for uWSGI worker 3 spawned 4 offload threads for uWSGI worker 4 2023-10-17 18:21:55,549 WARNING:searx: Be aware you have activated features intended only for public instances. This force the usage of the bot limiter and link_token plugins. 2023-10-17 18:21:55,564 WARNING:searx: Be aware you have activated features intended only for public instances. This force the usage of the bot limiter and link_token plugins. 2023-10-17 18:21:56,800 WARNING:searx: Be aware you have activated features intended only for public instances. This force the usage of the bot limiter and link_token plugins. 2023-10-17 18:21:56,841 WARNING:searx: Be aware you have activated features intended only for public instances. This force the usage of the bot limiter and link_token plugins. 2023-10-17 18:21:56,851 WARNING:searx: Be aware you have activated features intended only for public instances. This force the usage of the bot limiter and link_token plugins.

then it shuts down the docker..

[unixfox]

please explain how you installed searxng

also please remove cloudflare it's against this rule:

I control the final webserver (software) that is serving the requests to the users of my instance. Here is a non-exhaustive list of forbidden hosting types: Cloudflare, PaaS, managed (hosting provider controlled) HTTP(S) load balancer (e.g. AWS ALB), shared Web hosting. TCP load balancer is fine. Cloudflare DNS only (grey cloud) is fine.

[hzm170]

ah yes, i use it for DNS from RProxy due to i don't get static IP here yet.. but u can close this out i will try again soon with a static

[unixfox]

Ask for a reopen of this issue once:

• You have removed cloudflare
• You have public_instance parameter enabled.