Cloud temporal (7233) going through http_proxy

💬 Self Hosted Retool
1

HI! I have self-hosted cluster (in k8s) and try to connect to tmprl.cloud. Also i have https proxy setting in env. My vars:

HTTP_PROXY=http://***
NO_PROXY=***.tmprl.cloud:7233
WORKFLOW_TEMPORAL_CLUSTER_FRONTEND_HOST=***.tmprl.cloud
WORKFLOW_TEMPORAL_CLUSTER_FRONTEND_PORT=7233
WORKFLOW_TEMPORAL_CLUSTER_NAMESPACE="***"
WORKFLOW_TEMPORAL_TLS_ENABLED="true"
WORKFLOW_TEMPORAL_TLS_CRT=xxx
WORKFLOW_TEMPORAL_TLS_KEY=xxx

Also i tried to add

HTTP_PROXY_STRICT=false
GLOBAL_AGENT_BACKEND=true
GLOBAL_AGENT_NO_PROXY=***.tmprl.cloud:7233

But in container log it still

Failed to connect to ***.tmprl.cloud:7233 through proxy *** with status 403

The self-hosted version is 3.334.5-stable.

Please advise what needs to be changed. This address should not go through a proxy.

4

Thanks for reaching out, @Dariya_Romazanova! Apologies for the delay.

I'm pretty sure Retool's Temporal connection doesn't fall back on any of the generic proxy environment variables you've shown here. The SDK opens a gRPC connection that has its own separate proxy configuration.

Our recommended approach is to directly enable outbound traffic on port 7233 from the main backend and worker pods. If you've already done this and the connection is still being forced through a cluster-level proxy, you'll need to configure the bypass at that level instead.

Let me know if that is helpful and if you have any additional questions!