@@ -180,8 +180,8 @@ Started wiki`_ is always a good resource *to keep in the pocket*.
180180 .. code:: yaml
181181
182182 result_proxy:
183− # replace searx.example.com with your server's public name
184− url : http://searx.example.com/
183+ # replace example.org with your server's public name
184+ url : https://example.org/
185185
186186
187187 .. group-tab:: proxy or uWSGI
@@ -221,8 +221,8 @@ Started wiki`_ is always a good resource *to keep in the pocket*.
221221 .. code:: nginx
222222
223223 server {
224− # replace searx.example.com with your server's public name
225− server_name searx.example.com;
224+ # replace example.org with your server's public name
225+ server_name example.org;
226226
227227 listen 80;
228228 listen [::]:80;
@@ -248,8 +248,7 @@ Started wiki`_ is always a good resource *to keep in the pocket*.
248248
249249 Be warned, with these setups, your Instance isn't :ref:`protected <searx
250250 filtron>`. The examples are just here to demonstrate how to export the
251− searx application from a subdirectory URL
252− http://searx.example.com/searx/\.
251+ searx application from a subdirectory URL ``https://example.org/searx/``.
253252
254253 .. code:: nginx
255254
@@ -290,8 +289,8 @@ Started wiki`_ is always a good resource *to keep in the pocket*.
290289 .. code:: yaml
291290
292291 server:
293− # replace searx.example.com with your server's public name
294− base_url : http://searx.example.com/searx/
292+ # replace example.org with your server's public name
293+ base_url : https://example.org/searx/
295294
296295
297296Restart service: