Documentation on Caddyserver/Reverse Proxy

[Error00101]

Hello,

I realy like the Project. I have made my personal instance via Docker and I think it is great!
A thing that bothered me was the reverse proxy setup for HTTPS/SSL.
I first wanted to make it work via caddy (as it is included in the package) -
after some time i found the topic that i searched for but at that time i decided to use nginX (as it is more convinient for me to set up)

• Yes i overlooked the button that says docks on the website for Caddy.
• But there is no link to the Caddy-docks from the searXNG-docks either.

How did you install SearXNG?
Docker - RaspberryPi 4 (8GB)

What happened?
Relativly hard to find documentation for Caddy.

How To Reproduce

• search for Caddy on the wiki
• or looking through the index

Expected behavior
Finding a brief explanation on what a "reverse proxy" is and how to use caddy, (simmilar to nginX and Apache)
with a link to the Caddy Documentation

Screenshots & Logs
'-

Additional context
People new to the project will more likely use caddy and complain less if they find the documentation easier

Thank you very much!

[dalf]

In docker-compose.yml, the docker container searxng/searxng listen on the port 8080.

With NGINX, you can use this section of the documentation: https://docs.searxng.org/admin/installation-nginx.html#nginx-s-searxng-site
In the documentation you can see the path is /searxng, feel free to change it. Here without /searxng:

location / {
    proxy_pass http://127.0.0.1:8080;  # 127.0.0.1 or wherever is SearxNG

    proxy_set_header   Host             $host;
    proxy_set_header   Connection       $http_connection;

    # see flaskfix.py
    proxy_set_header   X-Scheme         $scheme;
    proxy_set_header   X-Script-Name    /;

    # see limiter.py
    proxy_set_header   X-Real-IP        $remote_addr;
    proxy_set_header   X-Forwarded-For  $proxy_add_x_forwarded_for;

    # proxy_buffering  off;
    # proxy_request_buffering off;
    # proxy_buffer_size 8k;

}

You most probably want to have a HTTPS connection, so you can embed the above section in a server section: https://ssl-config.mozilla.org/#server=nginx&version=1.17.7&config=intermediate&openssl=1.1.1k&guideline=5.6

[Error00101]

Thanks for the response!
Yep this is what i was using instead of Caddy. (these are even the same resources)
I still would suggest to add a Section in the Index for Caddy on how to configure it.

[y0nei]

what about all the headers that caddyfile sets? i have those in mine and i get issues on other locations like /static
#93