Issues with using AWS application load balancer
Hi i've installed the zitadel helm chart and i've been trying to expose it over AWS ALB but without much luck. I have a next.js frontend which redirects to zitadel for login and then my backend Go performs token introspection and grpc calls to zitadel. With following configuration, login works but the grpc calls don't (which i guess is expected).
Forcing the backend fixes the backend calls made to zitadel but next.js stops working (presumably because next-auth force HTTP1.1).
In both cases, i get 464 which is ALB's error so I don't think this is primarily a zitadel concern but just wanted to ask in here in case anyone has bumped into this before. Thanks!
Forcing the backend fixes the backend calls made to zitadel but next.js stops working (presumably because next-auth force HTTP1.1).
In both cases, i get 464 which is ALB's error so I don't think this is primarily a zitadel concern but just wanted to ask in here in case anyone has bumped into this before. Thanks!
