summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorMarkus Heiser <markus.heiser@darmarit.de>2023-05-21 20:50:14 +0200
committerMarkus Heiser <markus.heiser@darmarit.de>2023-05-22 10:46:10 +0200
commit0ee27ba3aa0cc1a8b5c9d37a04d3667fae6dba76 (patch)
tree33195f6c4d73a6de3feb84114e5a477cd151217c /docs
parentddbab4b3c95feaaf2b5c113980b10b022ea01ec1 (diff)
[doc] answer CAPTCHA from server's IP
Related: https://github.com/searxng/searxng/issues/2011#issuecomment-1553317619 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Diffstat (limited to 'docs')
-rw-r--r--docs/admin/answer-captcha.rst69
-rw-r--r--docs/admin/answer-captcha/ffox-setting-proxy-socks.pngbin0 -> 60796 bytes
-rw-r--r--docs/admin/index.rst1
3 files changed, 70 insertions, 0 deletions
diff --git a/docs/admin/answer-captcha.rst b/docs/admin/answer-captcha.rst
new file mode 100644
index 00000000..7ae29be0
--- /dev/null
+++ b/docs/admin/answer-captcha.rst
@@ -0,0 +1,69 @@
+===============================
+Answer CAPTCHA from server's IP
+===============================
+
+With a SSH tunnel we can send requests from server's IP and solve a CAPTCHA that
+blocks requests from this IP. If your SearXNG instance is hosted at
+``example.org`` and your login is ``user`` you can setup a proxy simply by
+:man:`ssh`:
+
+.. code:: bash
+
+ # SOCKS server: socks://127.0.0.1:8080
+
+ $ ssh -q -N -D 8080 user@example.org
+
+The ``socks://localhost:8080`` from above can be tested by:
+
+.. tabs::
+
+ .. group-tab:: server's IP
+
+ .. code:: bash
+
+ $ curl -x socks://127.0.0.1:8080 http://ipecho.net/plain
+ n.n.n.n
+
+ .. group-tab:: desktop's IP
+
+ .. code:: bash
+
+ $ curl http://ipecho.net/plain
+ x.x.x.x
+
+In the settings of the WEB browser open the *"Network Settings"* and setup a
+proxy on ``SOCKS5 127.0.0.1:8080`` (see screenshot below). In the WEB browser
+check the IP from the server is used:
+
+- http://ipecho.net/plain
+
+Now open the search engine that blocks requests from your server's IP. If you
+have `issues with the qwant engine
+<https://github.com/searxng/searxng/issues/2011#issuecomment-1553317619>`__,
+solve the CAPTCHA from `qwant.com <https://www.qwant.com/>`__.
+
+-----
+
+.. tabs::
+
+ .. group-tab:: Firefox
+
+ .. kernel-figure:: answer-captcha/ffox-setting-proxy-socks.png
+ :alt: FFox proxy on SOCKS5, 127.0.0.1:8080
+
+ Firefox's network settings
+
+
+.. admonition:: :man:`ssh` manual:
+
+ -D [bind_address:]port
+ Specifies a local “dynamic” application-level port forwarding. This works
+ by allocating a socket to listen to port on the local side .. Whenever a
+ connection is made to this port, the connection is forwarded over the
+ secure channel, and the application protocol is then used to determine
+ where to connect to from the remote machine .. ssh will act as a SOCKS
+ server ..
+
+ -N
+ Do not execute a remote command. This is useful for just forwarding ports.
+
diff --git a/docs/admin/answer-captcha/ffox-setting-proxy-socks.png b/docs/admin/answer-captcha/ffox-setting-proxy-socks.png
new file mode 100644
index 00000000..3da85d2c
--- /dev/null
+++ b/docs/admin/answer-captcha/ffox-setting-proxy-socks.png
Binary files differ
diff --git a/docs/admin/index.rst b/docs/admin/index.rst
index 70516730..4b41cd2a 100644
--- a/docs/admin/index.rst
+++ b/docs/admin/index.rst
@@ -14,6 +14,7 @@ Administrator documentation
installation-nginx
installation-apache
update-searxng
+ answer-captcha
engines/index
api
architecture