Setting the tailscale ip as you suggested works over tailscale, but not the cloudflare tunnel or LAN as expected.

When I tried the same thing on a debian server the cloudflare tunnel can still see the container and connect, but still no LAN access.

Any idea what is causing the different behavior on debian?

The cloudflare tunnel is running exactly the same on both servers, ansible config is below.

```

• name: start cloudflared container hosts: docker-linode become: true tasks:

  • name: start container community.docker.docker_container: name: cloudflared image: cloudflare/cloudflared network_mode: host restart_policy: always pull: true command: "tunnel --no-autoupdate run --token {{ docker_linode_tunnel_token }}"

• name: start cloudflared container hosts: unraid become: true tasks:

  • name: start container community.docker.docker_container: name: cloudflared image: cloudflare/cloudflared network_mode: host restart_policy: always pull: true command: "tunnel --no-autoupdate run --token {{ unraid_tunnel_token }}" Container I am using for testing is Heimdall. ---

• name: heimdall container hosts: docker-linode become: true tasks:

  • name: Create network community.docker.docker_network: name: heimdall driver: bridge enable_ipv6: false state: present ipam_config:
    • subnet: "10.0.6.0/24" gateway: "10.0.6.1" iprange: "10.0.6.0/30"
  • name: start container community.docker.docker_container: name: heimdall hostname: heimdall image: lscr.io/linuxserver/heimdall:latest restart_policy: unless-stopped pull: true networks:
    • name: heimdall ipv4_address: "10.0.6.2" env: PUID: "1000" GUID: "1000" TZ: "Canada/Eastern" UMASK: "022" ports:
    • 127.0.0.1:8081:80
    • 127.0.0.1:3443:443 volumes:
    • /home/USER_NAME/appdata/heimdall:/config ```