Proxy forwarding into Cloud returns TCP error
After configuring policy on a local proxy to forward http and https traffic into the Cloud all sites were unaccessible and the local proxy would return either a "tcp error" or "connection refused" exception. Health checks against the forwarder returned OK.
The root cause was the forward policy was copied into the local file but included extra characters and was not being matched. Corrected the policy and forwarding worked as expected.
Rate this Page
Please take a moment to complete this form to help us better serve you.