Caddy Error: `listening on :443: listen tcp :443: bind: address already in use`

[techsk8]

I'm getting this error and the start process goes into a loop... This is cause I have the apache2 running with all my hosted stuff on the host. If I stop apache2, then caddy works.

root@kvm:/usr/local/docker/searx-docker# ./start.sh
use docker-compose.yaml
Removing caddy   ... done
Removing morty   ... done
Removing searx   ... done
Removing filtron ... done
Removing network searx-docker_searx
No stopped containers
Creating network "searx-docker_searx" with the default driver
Creating filtron ... done
Creating searx   ... done
Creating caddy   ... done
Creating morty   ... done
Attaching to caddy, filtron, searx
caddy      | {"level":"info","ts":1650195459.9049065,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
caddy      | 2022/04/17 11:37:39 [WARNING] Unnecessary header_up ('X-Forwarded-Proto' field): the reverse proxy's default behavior is to pass headers to the upstream
filtron    | 2022/04/17 11:37:41 15 rules loaded from /etc/filtron/rules.json
filtron    | 2022/04/17 11:37:41 API listens on 0.0.0.0:4041
filtron    | 2022/04/17 11:37:41 Proxy listens on 0.0.0.0:4040
caddy      | {"level":"warn","ts":1650195459.9068031,"msg":"input is not formatted with 'caddy fmt'","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":2}
caddy      | {"level":"warn","ts":1650195459.9074922,"logger":"admin","msg":"admin endpoint disabled"}
caddy      | {"level":"info","ts":1650195459.9078841,"logger":"http","msg":"server is listening only on the HTTPS port but has no TLS connection policies; adding one to enabl
e TLS","server_name":"srv0","https_port":443}
caddy      | {"level":"info","ts":1650195459.907897,"logger":"http","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"srv0"}
caddy      | {"level":"info","ts":1650195459.9100049,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc00031ac40"}
caddy      | {"level":"info","ts":1650195459.9100242,"logger":"tls.cache.maintenance","msg":"stopped background certificate maintenance","cache":"0xc00031ac40"}
caddy      | run: loading initial config: loading new config: http app module: start: tcp: listening on :443: listen tcp :443: bind: address already in use
searx      | searx version 1.0.0-369-f522f922
searx      |
searx      | Use existing /etc/searx/uwsgi.ini
searx      | Use existing /etc/searx/settings.yml
searx      | Listen on 0.0.0.0:8080
searx      | [uWSGI] getting INI configuration from /etc/searx/uwsgi.ini
searx      | [uwsgi-static] added mapping for /static => /usr/local/searx/searx/static
caddy exited with code 1
caddy      | {"level":"info","ts":1650195463.9628854,"logger":"pki.ca.local","msg":"root certificate is already trusted by system","path":"storage:pki/authorities/local/root.
crt"}
caddy      | {"level":"info","ts":1650195463.9631245,"logger":"tls","msg":"cleaning storage unit","description":"FileStorage:/data/caddy"}
caddy      | {"level":"info","ts":1650195463.9631758,"logger":"tls","msg":"finished cleaning storage units"}
caddy      | {"level":"info","ts":1650195463.9633884,"logger":"tls.cache.maintenance","msg":"stopped background certificate maintenance","cache":"0xc000324540"}
caddy      | run: loading initial config: loading new config: http app module: start: tcp: listening on :443: listen tcp :443: bind: address already in use
caddy exited with code 1

How can I bypass this error, besides stopping apache2?

Is there a way to change the default port on which caddy communicates, from 443 to something else?

[unixfox]

Duplicate of https://github.com/searx/searx-docker/issues/63