Sonarqube helm with nginx returns a 404

[bheemreddy181 (Bheem)]

nginx:
  enabled: true

service:
  type: ClusterIP
  externalPort: 9000
  internalPort: 9000
  labels:
  annotations: {}
  # May be used in example for internal load balancing in GCP:
  # cloud.google.com/load-balancer-type: Internal
  # loadBalancerSourceRanges:
  #   - 0.0.0.0/0
  # loadBalancerIP: 1.2.3.4
  # You can set the port to be exposed when type is NodePort or LoadBalancer.
  # nodePort: 30000
ingress:
  enabled: true
  # Used to create an Ingress record.
  hosts:
    - name: sonar.curo.com
      # Different clouds or configurations might need /* as the default path
      path: /*
      # Only for API version "networking.k8s.io/v1"
      # https://kubernetes.io/docs/concepts/services-networking/ingress/#path-types
      # pathType: Prefix
      # For additional control over serviceName and servicePort
      # serviceName: someService
      # servicePort: somePort
  annotations:
    kubernetes.io/ingress.class: nginx
    kubernetes.io/ingress.allow-http: "false"
  # kubernetes.io/tls-acme: "true"
  # This property allows for reports up to a certain size to be uploaded to SonarQube
    nginx.ingress.kubernetes.io/proxy-body-size: "8m"
    ingressClassName: nginx

the above configuration on my value yml upgrades successfully but the application is not working on the external ip

[leo.geoffroy]

Hi @bheemreddy181
It’s difficult to spot what could be wrong with the configuration as it also depends on the cloud provider.
Have you tried making it work first on HTTP?
Does it also fail with path: / instead of path: /* ?