connecting to agent error: too many colons

[fama-lama]

🔍 Check for existing issues

• Completed

How is Dozzle deployed?

Remote Hosts

📦 Dozzle version

8.9.1

✅ Command used to run Dozzle

  dozzle:
    image: amir20/dozzle:latest
    container_name: dozzle
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - DOZZLE_REMOTE_AGENT=tcp://192.168.100.52:7007,tcp://192.168.100.53:7007,tcp://192.168.100.54:7007,tcp://192.168.100.56:7007,tcp://192.168.100.57:7007,tcp://192.168.100.59:7007,tcp://192.168.100.60:7007
    ports:
      - 8090:8080

🐛 Describe the bug / provide steps to reproduce it

deployed agents in all my lxcs. when trying to connect from my main dozzle instance, all the agents show offline.
logs seems to have one thing in common.

"error info: address tcp://xx:xx:xx:xx:7007:443: too many colons in address"

port 443 is appended to all my addresses, eventhough i have already declared a port.

💻 Environment

root@home-stack:~# docker system info
Client: Docker Engine - Community
 Version:    24.0.5
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.11.2
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.20.3
    Path:     /root/.docker/cli-plugins/docker-compose

Server:
 Containers: 12
  Running: 12
  Paused: 0
  Stopped: 0
 Images: 16
 Server Version: 24.0.5
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: journald
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 8165feabfdfe38c65b599c4993d227328c231fca
 runc version: v1.1.8-0-g82f18fe
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.8.12-5-pve
 Operating System: Debian GNU/Linux 12 (bookworm)
 OSType: linux
 Architecture: x86_64
 CPUs: 2
 Total Memory: 2GiB
 Name: home-stack
 ID: 6b7c6895-ffcf-42c3-88d4-746e6e7e072a
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

root@home-stack:~# 

📸 If applicable, add screenshots to help explain your bug

No response

📜 If applicable, attach your Dozzle logs. You many need to enable debug mode. See https://dozzle.dev/guide/debugging.

root@home-stack:~# docker logs dozzle
{"level":"info","time":"2025-01-08T01:14:17Z","message":"Dozzle version v8.9.1"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.52:7007, error info: address tcp://192.168.100.52:7007:443: too many colons in address","endpoint":"tcp://192.168.100.52:7007","time":"2025-01-08T01:14:17Z","message":"error fetching host info for agent"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.53:7007, error info: address tcp://192.168.100.53:7007:443: too many colons in address","endpoint":"tcp://192.168.100.53:7007","time":"2025-01-08T01:14:17Z","message":"error fetching host info for agent"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.54:7007, error info: address tcp://192.168.100.54:7007:443: too many colons in address","endpoint":"tcp://192.168.100.54:7007","time":"2025-01-08T01:14:17Z","message":"error fetching host info for agent"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.56:7007, error info: address tcp://192.168.100.56:7007:443: too many colons in address","endpoint":"tcp://192.168.100.56:7007","time":"2025-01-08T01:14:17Z","message":"error fetching host info for agent"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.57:7007, error info: address tcp://192.168.100.57:7007:443: too many colons in address","endpoint":"tcp://192.168.100.57:7007","time":"2025-01-08T01:14:17Z","message":"error fetching host info for agent"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.59:7007, error info: address tcp://192.168.100.59:7007:443: too many colons in address","endpoint":"tcp://192.168.100.59:7007","time":"2025-01-08T01:14:17Z","message":"error fetching host info for agent"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.60:7007, error info: address tcp://192.168.100.60:7007:443: too many colons in address","endpoint":"tcp://192.168.100.60:7007","time":"2025-01-08T01:14:17Z","message":"error fetching host info for agent"}
{"level":"info","clients":1,"time":"2025-01-08T01:14:17Z","message":"Connected to Docker"}
{"level":"info","time":"2025-01-08T01:14:17Z","message":"Accepting connections on :8080"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.52:7007, error info: address tcp://192.168.100.52:7007:443: too many colons in address","endpoint":"tcp://192.168.100.52:7007","time":"2025-01-08T01:14:18Z","message":"error fetching host info for agent"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.53:7007, error info: address tcp://192.168.100.53:7007:443: too many colons in address","endpoint":"tcp://192.168.100.53:7007","time":"2025-01-08T01:14:18Z","message":"error fetching host info for agent"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.54:7007, error info: address tcp://192.168.100.54:7007:443: too many colons in address","endpoint":"tcp://192.168.100.54:7007","time":"2025-01-08T01:14:18Z","message":"error fetching host info for agent"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.56:7007, error info: address tcp://192.168.100.56:7007:443: too many colons in address","endpoint":"tcp://192.168.100.56:7007","time":"2025-01-08T01:14:18Z","message":"error fetching host info for agent"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.57:7007, error info: address tcp://192.168.100.57:7007:443: too many colons in address","endpoint":"tcp://192.168.100.57:7007","time":"2025-01-08T01:14:18Z","message":"error fetching host info for agent"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.59:7007, error info: address tcp://192.168.100.59:7007:443: too many colons in address","endpoint":"tcp://192.168.100.59:7007","time":"2025-01-08T01:14:18Z","message":"error fetching host info for agent"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.60:7007, error info: address tcp://192.168.100.60:7007:443: too many colons in address","endpoint":"tcp://192.168.100.60:7007","time":"2025-01-08T01:14:18Z","message":"error fetching host info for agent"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.52:7007, error info: address tcp://192.168.100.52:7007:443: too many colons in address","time":"2025-01-08T01:14:18Z","message":"error listing containers"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.53:7007, error info: address tcp://192.168.100.53:7007:443: too many colons in address","time":"2025-01-08T01:14:18Z","message":"error listing containers"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.54:7007, error info: address tcp://192.168.100.54:7007:443: too many colons in address","time":"2025-01-08T01:14:18Z","message":"error listing containers"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.56:7007, error info: address tcp://192.168.100.56:7007:443: too many colons in address","time":"2025-01-08T01:14:18Z","message":"error listing containers"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.57:7007, error info: address tcp://192.168.100.57:7007:443: too many colons in address","time":"2025-01-08T01:14:18Z","message":"error listing containers"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.59:7007, error info: address tcp://192.168.100.59:7007:443: too many colons in address","time":"2025-01-08T01:14:18Z","message":"error listing containers"}
{"level":"warn","error":"failed to exit idle mode: invalid target address tcp://192.168.100.60:7007, error info: address tcp://192.168.100.60:7007:443: too many colons in address","time":"2025-01-08T01:14:18Z","message":"error listing containers"}

[amir20]

Why do you have tcp://? Just IP:PORT,...

[fama-lama]

ahh ok.
When just ip:port, the web-ui showed none of the agents, whereas using tcp it showed my agents despite them being offline. it seems i was having a different issue.

root@home-stack:~# docker logs dozzle
{"level":"info","time":"2025-01-08T01:52:51Z","message":"Dozzle version v8.9.1"}
{"level":"warn","host":"jellystack","id":"6b7c6895-ffcf-42c3-88d4-746e6e7e072a","time":"2025-01-08T01:52:51Z","message":"duplicate host with same ID found"}
{"level":"warn","host":"nextcloudstack","id":"6b7c6895-ffcf-42c3-88d4-746e6e7e072a","time":"2025-01-08T01:52:52Z","message":"duplicate host with same ID found"}
{"level":"warn","host":"frigatestack","id":"6b7c6895-ffcf-42c3-88d4-746e6e7e072a","time":"2025-01-08T01:52:52Z","message":"duplicate host with same ID found"}
{"level":"warn","host":"netstack","id":"6b7c6895-ffcf-42c3-88d4-746e6e7e072a","time":"2025-01-08T01:52:52Z","message":"duplicate host with same ID found"}
{"level":"warn","host":"arrstack","id":"6b7c6895-ffcf-42c3-88d4-746e6e7e072a","time":"2025-01-08T01:52:52Z","message":"duplicate host with same ID found"}
{"level":"warn","host":"netalertx","id":"6b7c6895-ffcf-42c3-88d4-746e6e7e072a","time":"2025-01-08T01:52:52Z","message":"duplicate host with same ID found"}
{"level":"info","clients":2,"time":"2025-01-08T01:52:52Z","message":"Connected to Docker"}
{"level":"info","time":"2025-01-08T01:52:52Z","message":"Accepting connections on :8080"}
root@home-stack:~# 

[amir20]

That's documented in the help section. There is also other issues you can search for.