HTTPS in use

[sqpp]

Hey.

I am trying to get SearXNG working, but it doesn't seems to help, no matter how do I change its ports.

I have OpenLiteSpeed running on 80 and 443, as well as some other containers that are passed to 8080.

I was trying to use 8081 for SearXNG - Caddy, but it fails with the following output apperently.

caddy | run: loading initial config: loading new config: http app module: start: tcp: listening on :443: listen tcp :443: bind: address already in use

Everything else starts.

Starting redis   ... done
Starting caddy   ... done
Starting searxng ... done
Attaching to caddy, redis, searxng
caddy      | {"level":"info","ts":1659177144.7212582,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
caddy      | {"level":"warn","ts":1659177144.7264159,"logger":"caddyfile","msg":"Unnecessary header_up X-Forwarded-Proto: the reverse proxy's default behavior is to pass headers to the upstream"}
caddy      | {"level":"warn","ts":1659177144.7338524,"msg":"Caddyfile input is not formatted; run the 'caddy fmt' command to fix inconsistencies","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":2}
caddy      | {"level":"warn","ts":1659177144.7366042,"logger":"admin","msg":"admin endpoint disabled"}
caddy      | {"level":"info","ts":1659177144.7377737,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0x40004eabd0"}
caddy      | {"level":"info","ts":1659177144.737867,"logger":"http","msg":"server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS","server_name":"srv0","https_port":443}
caddy      | {"level":"info","ts":1659177144.7379482,"logger":"http","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"srv0"}
caddy      | {"level":"info","ts":1659177144.7424207,"logger":"tls","msg":"cleaning storage unit","description":"FileStorage:/data/caddy"}
caddy      | {"level":"info","ts":1659177144.7426138,"logger":"tls","msg":"finished cleaning storage units"}
caddy      | {"level":"info","ts":1659177144.743557,"logger":"tls.cache.maintenance","msg":"stopped background certificate maintenance","cache":"0x40004eabd0"}
caddy      | run: loading initial config: loading new config: http app module: start: tcp: listening on :443: listen tcp :443: bind: address already in use
redis      | 1:C 30 Jul 2022 10:32:25.516 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis      | 1:C 30 Jul 2022 10:32:25.516 # Redis version=7.0.4, bits=64, commit=00000000, modified=0, pid=1, just started
redis      | 1:C 30 Jul 2022 10:32:25.516 # Configuration loaded
redis      | 1:M 30 Jul 2022 10:32:25.519 * monotonic clock: POSIX clock_gettime
redis      | 1:M 30 Jul 2022 10:32:25.522 * Running mode=standalone, port=6379.
redis      | 1:M 30 Jul 2022 10:32:25.522 # Server initialized
redis      | 1:M 30 Jul 2022 10:32:25.522 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis      | 1:M 30 Jul 2022 10:32:25.527 * Ready to accept connections
caddy exited with code 1
searxng    | SearXNG version 2022.07.29-0cf53109
searxng    | Use existing /etc/searxng/uwsgi.ini
searxng    | Use existing /etc/searxng/settings.yml
searxng    | Listen on 0.0.0.0:8080
searxng    | [uWSGI] getting INI configuration from /etc/searxng/uwsgi.ini
searxng    | [uwsgi-static] added mapping for /static => /usr/local/searxng/searx/static
searxng    | *** Starting uWSGI 2.0.20 (64bit) on [Sat Jul 30 10:32:26 2022] ***
searxng    | compiled with version: 11.2.1 20220219 on 21 December 2021 13:20:05
searxng    | os: Linux-5.13.0-1031-raspi #34-Ubuntu SMP PREEMPT Thu Jun 2 00:58:22 UTC 2022
searxng    | nodename: ad3b59ea973a
searxng    | machine: aarch64
searxng    | clock source: unix
searxng    | pcre jit disabled
searxng    | detected number of CPU cores: 4
searxng    | current working directory: /usr/local/searxng
searxng    | detected binary path: /usr/sbin/uwsgi
searxng    | chdir() to /usr/local/searxng/searx/
searxng    | your memory page size is 4096 bytes
searxng    | detected max file descriptor number: 1048576
searxng    | building mime-types dictionary from file /etc/mime.types...1323 entry found
searxng    | lock engine: pthread robust mutexes
searxng    | thunder lock: disabled (you can enable it with --thunder-lock)
searxng    | *** Cache "searxngcache" initialized: 11MB (key: 2136 bytes, keys: 4272000 bytes, data: 8192000 bytes, bitmap: 250 bytes) preallocated ***
searxng    | uwsgi socket 0 bound to TCP address 0.0.0.0:8080 fd 4
searxng    | Python version: 3.10.5 (main, Jul 25 2022, 15:52:08) [GCC 11.2.1 20220219]
searxng    | Python main interpreter initialized at 0xffff8d9a2b30
searxng    | python threads support enabled
searxng    | your server socket listen backlog is limited to 100 connections
searxng    | your mercy for graceful operations on workers is 60 seconds
searxng    | mapped 603360 bytes (589 KB) for 16 cores
searxng    | *** Operational MODE: preforking+threaded ***
searxng    | added /usr/local/searxng/ to pythonpath.
searxng    | spawned uWSGI master process (pid: 8)
searxng    | spawned uWSGI worker 1 (pid: 11, cores: 4)
searxng    | spawned uWSGI worker 2 (pid: 13, cores: 4)
searxng    | spawned 4 offload threads for uWSGI worker 1
searxng    | spawned uWSGI worker 3 (pid: 17, cores: 4)
searxng    | spawned 4 offload threads for uWSGI worker 2
searxng    | spawned uWSGI worker 4 (pid: 22, cores: 4)
searxng    | cache sweeper thread enabled
searxng    | spawned 4 offload threads for uWSGI worker 4
searxng    | spawned 4 offload threads for uWSGI worker 3
searxng    | 2022-07-30 10:32:31,090 ERROR:searx.shared: uwsgi.ini configuration error, add this line to your uwsgi.ini
searxng    | cache2 = name=searxcache,items=2000,blocks=2000,blocksize=4096,bitmap=1
searxng    | 2022-07-30 10:32:31,094 ERROR:searx.shared: uwsgi.ini configuration error, add this line to your uwsgi.ini
searxng    | cache2 = name=searxcache,items=2000,blocks=2000,blocksize=4096,bitmap=1
searxng    | 2022-07-30 10:32:31,094 ERROR:searx.shared: uwsgi.ini configuration error, add this line to your uwsgi.ini
searxng    | cache2 = name=searxcache,items=2000,blocks=2000,blocksize=4096,bitmap=1
searxng    | 2022-07-30 10:32:31,094 ERROR:searx.shared: uwsgi.ini configuration error, add this line to your uwsgi.ini
searxng    | cache2 = name=searxcache,items=2000,blocks=2000,blocksize=4096,bitmap=1

Anyone perhaps could assist?

[sqpp]

Figured out at least that it was for the LetsEncrypt Validation, however, still I am unable to change the port to 8081.

    ports:
     - "127.0.0.1:8081:8080"

Even though, I set this to 8081, it still seems to use 443. As once soon as I start the container, I get 502 on :443, while OpenLiteSpeed is stopped.

[mrpaulblack]

Hi,
Caddy is set to use the host network. Means it can use any port on your host. By default it wants to bind to port 443 and port 80, but both are already in use, as you can see in the caddy log:

caddy      | run: loading initial config: loading new config: http app module: start: tcp: listening on :443: listen tcp :443: bind: address already in use

You can remove caddy if you dont need it (its a reverse proxy and maes sure https is working), without you can still access SearXNG from port 8081...

Also if you want to access SearXNG from outside your host change ports for SearXNG to:

    ports:
     - 8081:8080