Failed to read within 20 seconds error

[Nikhil Shivanath]

### Describe the bug:

I am trying to run ZAP daemon using a docker compose file ( given below ) ,  but it seems to inevitably run into this error : "Failed to read http://servers_public_ipv4_address:8090 within 20 seconds .... " error .

i tried setting -config network.localServers.aliases.name=<public_ipv4>

My server setup :
the public ip v4 address ports 3000, 8080 and 8081 are mapped to the following domains respectively using nginx reverse proxies : custom.domain.com , another_custom.domain.com and yet_another_custom.domain.com

then i get the same error , but for the domain : "Failed to read http://custom.domain.com ..... "

note: i have mutliple apps deployed at this public_ipv4 address .  and custom.domain.com is one of them . Somehow zap identifies that custom.domain.com is an alias for the public ip v4 address ( im not sure why ) . ( judging by this message , whenever i access the custom.domain.com application on my browser , im guessing its trying to connect to ZAP too ? and causing this error ? im not sure , just thinking out loud here
setup

Some help would really be appreciated:

docker-compose.yml
```
services:
  ZAP:
    image: zaproxy/zap-stable
    container_name: devsecshield-zap-daemon
    ports:
      - 8090:8090
    command: zap-x.sh -daemon -host 0.0.0.0 -port 8090 -config api.addrs.addr.name=.* -config api.addrs.addr.regex=true -config api.key=${ZAP_API_KEY} -config network.localServers.aliases.alias.name=<publicIPv4>    
    volumes:
      - zap_volume:/zap
      - zap_home_volume:/home
volumes:
  zap_volume:
    driver: local
  zap_home_volume:
    driver: local
```

### Steps to reproduce the behavior:

1. docker-compose up

### Expected behavior:

able to connect to zap daemon without any hiccups

[Simon Bennetts]

Does this help?

https://www.zaproxy.org/docs/docker/diagnosing-problems/#zap-cannot-connect-to-the-target

Cheers,

Simon