Hi everyone raised hands we have deployed the

Question

Hi everyone raised hands we have deployed the everything s okay but we have problems with running workflow remotely The following error is shown ```flytesnacks git master pyflyte run remote examples basics basics hello world py hello world wf Failed with Exception Code SYSTEM Unknown RPC Failed with Status StatusCode UNAVAILABLE details failed to connect to all addresses last error INTERNAL ipv4 10 1 64 90 443 Trying to connect an http1 x server Debug string UNKNOWN failed to connect to all addresses last error INTERNAL ipv4 10 1 64 90 443 Trying to connect an http1 x server grpc status 14 created time 2023 09 21T20 46 30 828791+02 00 ``` We can access the console UI with the our DNS but the GRPC we do not have access to Our flyte config is ```admin For GRPC endpoints you might want to use dns flyte myexample com endpoint dns lt our dns gt authType Pkce insecureSkipVerify true only required if using a self signed cert Caution not to be used in production insecure true only required when using insecure ingress Secure ingress may cause an unavailable desc error to true option logger show source true level 6``` Any idea what is happening Thank you heart

Marti Jorda Roca · Answer

We have this configuration for our aws load balancer ``` ingress albSSLRedirect true separateGrpcIngress true annotations aws load balancer controller v2 1 or higher is required For EKS if using ALB these annotations are set alb service instance=production internal $CLUSTER SG $CLUSTER CUSTOM SG $CLUSTER SUBNETS ip This is the certificate arn of the cert imported in AWS certificate manager Values userSettings certificateArn HTTP 80 HTTPS 443 Type redirect RedirectConfig Protocol HTTPS Port 443 StatusCode HTTP 301 Instruct ALB Controller to not create multiple load balancers and hence maintain a single endpoint for both GRPC and Http flyte separateGrpcIngressAnnotations GRPC```

Marti Jorda Roca · Answer

Also the our ingress seams okay ```Name flyte core grpc Labels Namespace flyte Address lt our aws load balancer gt Ingress Class lt none gt Default backend lt default gt Rules Host Path Backends flyteidl service SignalService flyteadmin 81 10 1 52 244 8089 10 1 56 226 8089 flyteidl service SignalService flyteadmin 81 10 1 52 244 8089 10 1 56 226 8089 flyteidl service AdminService flyteadmin 81 10 1 52 244 8089 10 1 56 226 8089 flyteidl service AdminService flyteadmin 81 10 1 52 244 8089 10 1 56 226 8089 flyteidl service DataProxyService flyteadmin 81 10 1 52 244 8089 10 1 56 226 8089 flyteidl service DataProxyService flyteadmin 81 10 1 52 244 8089 10 1 56 226 8089 flyteidl service AuthMetadataService flyteadmin 81 10 1 52 244 8089 10 1 56 226 8089 flyteidl service AuthMetadataService flyteadmin 81 10 1 52 244 8089 10 1 56 226 8089 flyteidl service IdentityService flyteadmin 81 10 1 52 244 8089 10 1 56 226 8089 flyteidl service IdentityService flyteadmin 81 10 1 52 244 8089 10 1 56 226 8089 grpc health v1 Health flyteadmin 81 10 1 52 244 8089 10 1 56 226 8089 grpc health v1 Health flyteadmin 81 10 1 52 244 8089 10 1 56 226 8089 Annotations Type redirect RedirectConfig Protocol HTTPS Port 443 StatusCode HTTP 301 GRPC lt our cert arn gt flyte HTTP 80 HTTPS 443 internal lt our cluster sg gt lt our cluster subnets gt service instance=production ip alb flyte flyte console GRPC Events lt none gt ```

Marti Jorda Roca · Answer

We are deploying it in private subnets and internal load balancer to only have access with the VPN

David Espejo (he/him) · Answer

considering that you re using a certificate try using `insecure false` in your `config` file

Marti Jorda Roca · Answer

yesss that was it heart partyparrot como siempre muchas gracias david