You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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'll keep my instance up to date, at the very least 1 week old. Example program for keeping up to date: watchtower, cron, ouroboros.
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
The text was updated successfully, but these errors were encountered:
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.
ononoki1
changed the title
Add http://g7nmfjgxe22s7j2hazhlk2p6gbu4jmfgx6m5oa2svphzvoqmbzjy4wad.onion/searxng/
Add http://g7nmfjgxe22s7j2hazhlk2p6gbu4jmfgx6m5oa2svphzvoqmbzjy4wad.onion/searxng
Jul 31, 2024
I apologize, I had forgotten, although it is very clear on the registration form, I made the necessary changes and changed the root path as recommended
aquila0101
changed the title
Add http://g7nmfjgxe22s7j2hazhlk2p6gbu4jmfgx6m5oa2svphzvoqmbzjy4wad.onion/searxng
Add http://g7nmfjgxe22s7j2hazhlk2p6gbu4jmfgx6m5oa2svphzvoqmbzjy4wad.onion
Jul 31, 2024
Requirements (make sure to read all of them)
check.searx.space
to check my instance (every 3 hours for the response times, every 24 hours for the other tests).Bot protection requirement
server.public_instance
parameter.Source code URL
No response
Comment
No response
The text was updated successfully, but these errors were encountered: