ERROR:searx.botdetection: X-Real-IP header is not set!

[rowie]

Hi,

i have tons of this msg. in my log.
is there any config error in my instance or is this normal?

br,
rowie

[return42]

A correct setup of the HTTP request headers X-Forwarded-For and X-Real-IP is essential to be able to assign a request to an IP correctly

[rowie]

Hi, i use the docker version with caddy.

[rowie]

there is no nginx or apache

[rowie]

found this in the Caddyfile:

 # SearXNG
  handle {
        encode zstd gzip

        reverse_proxy localhost:8080 {
               header_up X-Forwarded-Port {http.request.port}
               header_up X-Forwarded-Proto {http.request.scheme}
        }
  }

[dalf]

If X-Real-IP is not required, the log at line 105 should be either removed, throw once as a warning, or at least not be a repeated error.

[return42]

Should be logged "once" in the ERROR log .. but IDK how to log it "once".

[dalf]

using a global variable?

FIRST_NO_REAL_IP = True 

def get_real_ip(request: flask.Request) -> str:
  global FIRST_NO_REAL_IP  # pylint: disable=...
  ...
  if not real_ip and FIRST_NO_REAL_IP:
     FIRST_NO_REAL_IP = True 
     logger.error("X-Real-IP header is not set!") 

---

Side note: Caddy ignores existing value(s) sent by the browser (or whatever HTTP client), and set the value to the browser IP address.

[return42]

using a global variable?

can reduce the number of messages .. but is not "once" in a multi process environment.

Side note: Caddy ignores existing value(s) sent by the browser (or whatever HTTP client), and set the value to the browser IP address.

confused .. from where should caddy know the browser IP address? .. caddy (like any other HTTP server) can only see what client or proxy is in front of caddy ..

[dalf]

but is not "once" in a multi process environment.

not a big deal: it is only at the startup.

confused .. from where should caddy know the browser IP address? .. caddy (like any other HTTP server) can only see what client or proxy is in front of caddy ..

yes, it does not see more what you just wrote (that what I intended to say by whatever HTTP client).

[rowie]

soooo, what should i do now to reduce the log entries? :-)

[return42]

Question has been answered .. @dalf and me just discuss how we can improve the behavior.

[rowie]

if i dont use apache or nginx ... how can it be answered?
my instance is setup correctly like descript in the documentation.

[rowie]

maybe I'm misunderstanding you

[return42]

if i dont use apache or nginx ... how can it be answered?

The answer is to set up the header correctly .. depends on your proxy infrastructure IDK and IDK how to setup headers in a caddy config file.

Please be patient, may be @dalf and me find a solution to reduce the tons of messages in your log .. or you disabling logging at all.

[rowie]

to my "infrastructure" - Hardware Firewall in front of the caddy container (revers proxy) - standard docker deployment of searxng (https://github.com/searxng/searxng-docker)

[return42]

@dalf seems there is already a PR waiting for a review

• Update Caddyfile to Add X-Real-IP to fix bot detection #162

I move this discussion to docker.