limiter.toml does not exist when setting server.limiter: true

[thaynes43]

Hello,

Posting for awareness if anyone else encounters this. When I set server.limiter: true I started seeing errors that limiter.toml did not exist and going into the container I did not find it at /etc/serxng. I created a ConfigMap with this value:

apiVersion: v1
kind: ConfigMap
metadata:
  name: configmap-searxng-limiter
  namespace: haynes-intelligence
data:
  limiter.toml: |
    # This configuration file updates the default configuration file
    # See https://github.com/searxng/searxng/blob/master/searx/limiter.toml
    [botdetection.ip_limit]
    link_token = true

And then configured persistence to plop it where the service was looking for it:

    persistence:
      limiter:
        enabled: true
        type: configMap
        name: configmap-searxng-limiter
        mountPath: /etc/searxng/limiter.toml
        subPath: limiter.toml

And it is now there, errors are gone:

/etc/searxng # ls
limiter.toml  settings.yml  uwsgi.ini

And the contents match the map:

/etc/searxng # cat limiter.toml 
# This configuration file updates the default configuration file
# See https://github.com/searxng/searxng/blob/master/searx/limiter.toml
[botdetection.ip_limit]
link_token = true/etc/searxng # 

For reference here are the settings I configured as well to get the limiter working:

/etc/searxng # cat settings.yml 
redis:
  url: redis://searxng-redis:6379
search:
  formats:
  - html
  - json
server:
  limiter: true
  secret_key: $SEARXNG_SECRET

I am using this for Open WebUI which also required - json as a format.

Thanks!

[unixfox]

Could you create a PR please in order to fix the bug?

[disconn3ct]

FYI favicons has the same issue.

The upstream chart has a configmap: block that can solve this whole thing really nicely, especially in newer versions. If I get time I'll see about a PR to update common, but here is a fix using this version. Update your values:

podAnnotations:
  checksum/config: "{{ toYaml .Values.searxng | sha256sum }}"
  checksum/configmap: "{{ toYaml .Values.configmap | sha256sum }}"
configmap:
  limiter:
    enabled: true
    data:
      limiter.toml: |
        [botdetection.ip_limit]
        link_token = true
  favicon:
    enabled: true
    data:
      favicons.toml: |
        [favicons]
        cfg_schema = 1   # config's schema version no.
        [favicons.cache]
        db_url = "/cache/faviconcache.db"  # default: "/tmp/faviconcache.db"
        LIMIT_TOTAL_BYTES = 104857600                 # default: 50 MB
persistence:
  limiter:
    enabled: true
    type: configMap
    name: searxng-limiter
    # identifier: limiter
    mountPath: /etc/searxng/limiter.toml
    subPath: limiter.toml
  favicon:
    enabled: true
    type: configMap
    name: searxng-favicon
    # identifier: favicon
    mountPath: /etc/searxng/favicons.toml
    subPath: favicons.toml
  cache:
    enabled: true
    type: emptyDir
    accessMode: ReadWriteOnce

[derritter88]

@disconn3ct

I followed your approach for the favicon.toml but it created a mounted folder instead of a .toml file.

[derritter88]

Additional I see following error at my pod logs:

2025-03-12 11:50:09,082 ERROR:searx.botdetection: X-Forwarded-For header is not set!
2025-03-12 11:50:09,082 ERROR:searx.botdetection: X-Real-IP header is not set!

But on my proxy I would have set up all the headers correctly

[derritter88]

Okay I solved the problem with the favicon.toml as folder issue.
The problem that searx.botdetection is still there even thought entering "ip" at the searchbar show my real IP address.

Any idea what's wrong with that?