Access private networks which are behind zero trust using cloudflared cli daemon app?

I'm trying to access my 10.X,X,X ip (postgres) using the below command
cloudflared access tcp --hostname=dev-db.abc.xyz --url=localhost:9210 --log-level=debug --service-token-id=xxxx --service-token-secret=xxxx
cloudflared access tcp --hostname=dev-db.abc.xyz --url=localhost:9210 --log-level=debug --service-token-id=xxxx --service-token-secret=xxxx
What I have done - Created a public hostname with the ip within the same tunnel (have confirmed the ip is accessible through the warp acess app [1.1.1.1 app] ) Also created relevant SERVICE AUTH policies and made sure the target is above hostname which I created before. The error is downstream->upstream copy: read tcp 192.168.0.119:35524->104.21.21.32:443: use of closed network connection Any help will be appreciated. Also the internal IPs can be accessed through an public hostname under the tunnel (Tested that using a different but http service which uses similar ip within same ip range)
1 Reply
smartass08
smartass083mo ago
This happens for both redis and postgres - Which are tcp nvm solved