404 Not Found Error

[nekromantik]

Hi all
So I set up default settings on my RPi 4b and I left host and email commented on .env file as i want to make it work on http localhost first,
It boots up without errors but I get 404 not found when I curl http://localhost.

Log:

caddy | {"level":"info","ts":1732966976.885481,"msg":"using config from file","file":"/etc/caddy/Caddyfile"}
caddy | {"level":"warn","ts":1732966976.8885868,"logger":"caddyfile","msg":"Unnecessary header_up X-Forwarded-Proto: the reverse proxy's default behavior is to pass headers to the upstream"}
caddy | {"level":"info","ts":1732966976.8911526,"msg":"adapted config to JSON","adapter":"caddyfile"}
caddy | {"level":"warn","ts":1732966976.8912091,"msg":"Caddyfile input is not formatted; run 'caddy fmt --overwrite' to fix inconsistencies","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":2}
caddy | {"level":"warn","ts":1732966976.8924627,"logger":"admin","msg":"admin endpoint disabled"}
caddy | {"level":"warn","ts":1732966976.8928428,"logger":"http.auto_https","msg":"server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server","server_name":"srv0","http_port":80}
caddy | {"level":"info","ts":1732966976.8929415,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0x40000be880"}
caddy | {"level":"info","ts":1732966976.8951702,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]}
caddy | {"level":"info","ts":1732966976.8958554,"msg":"autosaved config (load with --resume flag)","file":"/config/caddy/autosave.json"}
caddy | {"level":"info","ts":1732966976.8958898,"msg":"serving initial configuration"}
caddy | {"level":"info","ts":1732966976.9012184,"logger":"tls","msg":"storage cleaning happened too recently; skipping for now","storage":"FileStorage:/data/caddy","instance":"9addc367-6e5b-4216-bd37-853c7604a55f","try_again":1733053376.901213,"try_again_in":86399.99999826}
caddy | {"level":"info","ts":1732966976.901501,"logger":"tls","msg":"finished cleaning storage units"}
searxng | SearXNG version 2024.11.27+55481a637
searxng | Use existing /etc/searxng/uwsgi.ini
searxng | Use existing /etc/searxng/settings.yml
searxng | Listen on 0.0.0.0:8080
searxng | [uWSGI] getting INI configuration from /etc/searxng/uwsgi.ini
searxng | [uwsgi-static] added mapping for /static => /usr/local/searxng/searx/static
searxng | *** Starting uWSGI 2.0.25.1 (64bit) on [Sat Nov 30 11:42:59 2024] ***
searxng | compiled with version: 13.2.1 20240309 on 17 May 2024 06:11:37
searxng | os: Linux-6.6.62+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.62-1+rpt1 (2024-11-25)
searxng | nodename: 19d6c70b0e34
searxng | machine: aarch64
searxng | clock source: unix
searxng | pcre jit disabled
searxng | detected number of CPU cores: 4
searxng | current working directory: /usr/local/searxng
searxng | detected binary path: /usr/sbin/uwsgi
searxng | setgid() to 977
searxng | setuid() to 977
searxng | chdir() to /usr/local/searxng/searx/
searxng | your memory page size is 4096 bytes
searxng | detected max file descriptor number: 1048576
searxng | building mime-types dictionary from file /etc/mime.types...1390 entry found
searxng | lock engine: pthread robust mutexes
searxng | thunder lock: disabled (you can enable it with --thunder-lock)
searxng | uwsgi socket 0 bound to TCP address 0.0.0.0:8080 fd 3
searxng | Python version: 3.12.7 (main, Oct 7 2024, 11:30:19) [GCC 13.2.1 20240309]
searxng | Python main interpreter initialized at 0x7fba8020b0
searxng | python threads support enabled
searxng | your server socket listen backlog is limited to 100 connections
searxng | your mercy for graceful operations on workers is 60 seconds
searxng | mapped 603360 bytes (589 KB) for 16 cores
searxng | *** Operational MODE: preforking+threaded ***
searxng | added /usr/local/searxng/ to pythonpath.
searxng | spawned uWSGI master process (pid: 7)
searxng | spawned uWSGI worker 1 (pid: 10, cores: 4)
searxng | spawned uWSGI worker 2 (pid: 12, cores: 4)
searxng | spawned 4 offload threads for uWSGI worker 1
searxng | spawned uWSGI worker 3 (pid: 19, cores: 4)
searxng | spawned 4 offload threads for uWSGI worker 2
searxng | spawned uWSGI worker 4 (pid: 21, cores: 4)
searxng | spawned 4 offload threads for uWSGI worker 3
searxng | spawned 4 offload threads for uWSGI worker 4
searxng | WSGI app 0 (mountpoint='') ready in 5 seconds on interpreter 0x7fba8020b0 pid: 19 (default app)
searxng | WSGI app 0 (mountpoint='') ready in 5 seconds on interpreter 0x7fba8020b0 pid: 12 (default app)
searxng | WSGI app 0 (mountpoint='') ready in 5 seconds on interpreter 0x7fba8020b0 pid: 21 (default app)
searxng | WSGI app 0 (mountpoint='') ready in 5 seconds on interpreter 0x7fba8020b0 pid: 10 (default app)

[return42]

I moved your thread to discussions / its not a bug of the searxng-docker image.

However, for a lively discussion its recommended to participate from the SearXNG community at #searxng:matrix.org.

---

• READ before posting here! #188