We are experiencing issues accessing the SigNoz login and registration pages when accessing the application via an NGINX Ingress setup. The UI loads partially or fails during login/register attempts. However, when accessing SigNoz via

kubectl port-forward

directly to the service, all functionality—including login and registration—works as expected. Environment Details: • Ingress Controller: NGINX • Load Balancer: AWS NLB (with TLS via cert-manager and external-dns) • Service Type: ClusterIP • SigNoz Version: v0.81.0 • Access Method That Works:

kubectl port-forward

• Access Method That Fails: Public URL via Ingress (e.g., https://signoz.test.com) Observed Logs: • Successful 200 responses for

/api/v1/hosts/list

,

/api/v1/loginPrecheck

• 501 error for

/api/v3/licenses/active

(

"not implemented"

) • 500 error for

/api/v1/user/{id}

(

"user not found"

) via Ingress This behavior suggests an issue with Ingress forwarding or session handling. Request: Could you please help identify what might be misconfigured in our Ingress setup or suggest changes needed to ensure login/register works correctly through NGINX Ingress? Happy to provide Ingress and service YAMLs if needed.

Try clearing your browser local storage and try again.