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. And ingress yaml would be helpful.

apiVersion: <http://networking.k8s.io/v1|networking.k8s.io/v1>

kind: Ingress metadata: name: signoz namespace: signoz uid: 90aa4219-f536-40b5-8792-653e63b1de67 resourceVersion: '5303969' generation: 20 creationTimestamp: '2025-05-04T075456Z' labels: app.kubernetes.io/component: signoz app.kubernetes.io/instance: signoz app.kubernetes.io/managed-by: Helm app.kubernetes.io/name: signoz app.kubernetes.io/version: v0.81.0 helm.sh/chart: signoz-0.79.0 annotations: cert-manager.io/cluster-issuer: letsencrypt-prod external-dns.alpha.kubernetes.io/hostname: signoz.test.com meta.helm.sh/release-name: signoz meta.helm.sh/release-namespace: signoz service.beta.kubernetes.io/aws-load-balancer-internal: 'true' service.beta.kubernetes.io/aws-load-balancer-type: nlb service.beta.kubernetes.io/aws-load-balancer-ssl-ports: "https" service.beta.kubernetes.io/aws-load-balancer-backend-protocol: "http" selfLink: /apis/networking.k8s.io/v1/namespaces/signoz/ingresses/signoz status: loadBalancer: ingress: - hostname: >- test-96d934eeb4d910c6.elb.ap-south-1.amazonaws.com spec: ingressClassName: nginx tls: - hosts: - signoz.test.com secretName: signoz rules: - host: signoz.test.com http: paths: - path: / pathType: Prefix backend: service: name: signoz port: number: 8080

Hey @Nagarajan, Just for the sake of the community here, • we cannot run more than 1 replica of SigNoz • use

signoz/signoz

registry for easy upgrade to enterprise if that choice is taken.