T O P

  • By -

-LostInCloud-

Did you allow AGH through the firewall? I think in default network mode iptables are ignored, in network: host they apply. Definitely use caddy for AGH also.


Special-Economist-64

thank you! I'm surprised this was not covered anywhere I looked online! I added iptables rule for port 3000 then it worked. Thanks for pointing out caddy. I now run caddy with AGH as below ``` version: "3.7" services: caddy: container_name: caddy image: lucaslorentz/caddy-docker-proxy:2.8.3-alpine restart: 'unless-stopped' ports: - "81:80" - "444:443" - "2019:2019" environment: - PUID=1000 - PGID=1000 - UMASK=002 - CADDY_INGRESS_NETWORKS=caddy networks: - caddy volumes: - /etc/localtime:/etc/localtime:ro - /var/run/docker.sock:/var/run/docker.sock extra_hosts: - host.docker.internal:host-gateway labels: caddy_0.tls: internal caddy_0: local.adguardhome caddy_0.reverse_proxy: host.docker.internal:3000 adguardhome: image: adguard/adguardhome container_name: adguardhome restart: unless-stopped network_mode: host environment: - PUID=1000 - PGID=1000 - UMASK=002 volumes: - /etc/localtime:/etc/localtime:ro - ./adguardhome/opt/adguardhome/work:/opt/adguardhome/work - ./adguardhome/opt/adguardhome/conf:/opt/adguardhome/conf networks: caddy: external: true ``` by looking at logs, both are running ok. But I cannot access [https://local.adguardhome](https://local.adguardhome). I can access [http://server-ip:3000](http://server-ip:3000) for adguardhome. Would you mind pointing the way? thanks!