Any of you guys self-host searx? I set it up with an outbound socks5 proxy through my vpn provider. I figured this way is more private because it hides my ip from google. The question is: how do I know now if the proxying works? As a test I tried changing one character in the auth passw. however this did not break searx. This makes me suspicious that it is not proxying at all. Does anyone have an idea how to test which IP google sees for my search requests? :-)) i hope that was clear...

Β· Β· Tusky Β· 3 Β· 2 Β· 1

Ok so the only way for me to solve this was by isolating the searx docker container and routing all of it's network traffic through a vpn client container. Wireshark says: no more connections to google bing or whatever :-) speed is great too.

@gabor Hmm, have you run Wireshark to see what's going on?

It's quite plausible that it isn't working as expected.

@urusan never used Wireshark before but it looks like this could be a task for it....

@urusan so I looked at the server traffic with wireshark however the noise is not managable for me :-)

@gabor It's pretty impressive you were able to get up and running with Wireshark so quickly.

You might want to ask around for tips to reduce that noise.

@urusan thanks :-) yeah I might dig into this, it looks like a useful tool

@gabor What IP does Google think you are? This seems so simple it must be wrong. Go to and tell it to translate from Spanish to English for either of:
(Most other header tools get the wrong answer)

Look for "X-Forwarded-For".

That's who Google thinks you are.

@ericphelps actually this is not applicable to my case (or at least I don't see how), since searx doesn't have google translate as an engine... is there any similar solution using just a "normal" google search query?

Sign in to participate in the conversation

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.