Nope. I tried dozen of conf and tweaks and restart from scratch but couldn’t solve it. I couldn’t understand the relayd code either so I have no clue where the bug lies.
I have switched to using nginx instead. > > Le 9 mars 2025 à 13:11, Dan <d...@nnnne-o-o-o.com> a écrit : > > > Did you solve it? > > I started my own instance as well without an issue by nginx. > > I don't know almost anything about relayd but I continue to > to doubt about these constraints, expecially x-scheme and script-name: > >>>> match request header set "X-Forwarded-For" value "$REMOTE_ADDR" >>>> match request header set "X-Real-IP" value "$REMOTE_ADDR" >>>> match request header set "X-Scheme" value "https" >>>> match request header set "X-Script-Name" value "/searxng" } > > > Dan > > ------ > nuggetsman.com - Repo: https://code.5mode.com > > Please reply to the mailing-list, leveraging technical stuff. > > > Joel Carnat <j...@carnat.net> wrote: > >> At first, I was using HTTPS only. But this prevents reading the data >> in tcpdump. But using HTTPS or HTTP doesn't change anything on w3m >> behaviour. >> >
