[Bug]: Google OAuth on a Helm deployment redirects to URL with :8080 as the port, where it shouldn't have a port at all

[sharat87]

Is there an existing issue for this?

• I have searched the existing issues

Description

When Appsmith is deployed on a Kubernetes cluster using Helm charts, and Google OAuth is configured, the redirect URL after authentication adds the :8080 port and so fails to work.

For example, if this Appsmith is accessible on http://myappsmith.com, then Google OAuth redirects to http://myappsmith.com:8080/..., which would obviously fail. The URL actually works fine when the :8080 part is removed.

Steps To Reproduce

Deploy Appsmith with Helm charts on a new cluster, with ingress enabled, configure Google OAuth using the Helm values, and try to login with Google. The redirect URL should have the :8080 in it, when it shouldn't.

Check if this issue is present with GitHub OAuth as well.

Public Sample App

No response

Version

Self Hosted

[pquadri]

I think I found a fix, you need to force the proxy_set_header X-Forwarded-Port 80; in the nginx configuration within the image. Do you want me to submit a PR?

[sum35h]

Hi @pquadri ,thanks for looking into it.
Currently it seems to be working fine when I set it up on aws eks, and I'm not able to re-create the issue. It would be really helpful if you could share the setup details, where the issue occurs.

[pquadri]

I just used the default helm chart and didn't provide any configuration besides changing the ingress, but the issue apparently is the nginx configuration within the image (that is reset on every pod restart, I have to change it by hand). If you want to hop in a discord session or something I could show you

[sharat87]

@pquadri, can you share if you still see this problem? We've tried several times, but are unable to see this. If you see this problem, please feel free to start a conv. on Discord with you configuration to investigate. My username is same on Discord as here. Thanks!

[pquadri]

The issue disappeared when we changed ingress type. Not really sure how.

[sharat87]

I think this problem shows up when Appsmith is running with a Network Load Balancer (NLB). Since that operates at Layer-4, the same problem as in #14290 (comment) manifests here as well. The solution there should help here, but we need to first try to reproduce with an NLB.