fix(paseo): trust the platform proxy so the web UI can connect

The daemon trusts X-Forwarded-Proto from loopback only by default, but
Coolify's Traefik reaches it from the Docker bridge network. It therefore
reported the request as plain HTTP and handed the UI useTls: false, so the
UI built a ws:// URL on an https:// page. The browser blocked it as mixed
content and the UI fell back to its built-in localhost:6767 default.

uniquelocal covers the private ranges Docker uses. An exact CIDR is
tighter but Coolify assigns a fresh subnet per project.

paseo/.env.example

@@ -9,3 +9,10 @@ PASEO_PASSWORD=
 # Comma-separated DNS names allowed to reach the daemon. The domain mapped in
 # Coolify/Dokploy must be listed here. IPs and localhost are always allowed.
 PASEO_HOSTNAMES=
+
+# Proxy addresses whose X-Forwarded-Proto the daemon trusts. Without this the
+# daemon only trusts loopback, so behind Coolify/Dokploy it sees plain HTTP,
+# tells the web UI the connection is not TLS, and the UI falls back to trying
+# ws://...:6767 from an HTTPS page -- which the browser blocks.
+# `uniquelocal` covers the private ranges Docker bridge networks use.
+PASEO_TRUSTED_PROXIES=uniquelocal