Certificate request seems stuck after storing new private key – Nginx

I’ve been trying to roll out our an environment on Kubernetes using LetsEncrypt with CertManager to provision certificates.

However, it seems that the certificate, for whatever reason, can’t be provided.
I’ve been going through the steps over at
https://cert-manager.io/docs/faq/troubleshooting/ but I get stuck on ‘Stored new private key in temporary Secret Resource "xxx"’, and I cannot find any troubleshooting steps to solve this.

The events list from my past few attempts to reset the certificate

My ingress.yaml looks as follows:

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: myname-ingress
  annotations:
    kubernetes.io/ingress.class: nginx
    cert-manager.io/cluster-issuer: letsencrypt-prod
    nginx.ingress.kubernetes.io/rewrite-target: /$2
spec:
  tls:
  - hosts:
    - app.mydomain.io
    secretName: tls-secret
  rules:
  - host: app.mydomain.io
    http:
      paths:
      - backend:
          serviceName: mydomain-identity-v1
          servicePort: 80
        path: /login(/|$)(.*)
      - backend:
          serviceName: mydomain-account-v1
          servicePort: 80
        path: /account(/|$)(.*)

With the following cluster-issuer:

apiVersion: cert-manager.io/v1alpha2
kind: ClusterIssuer
metadata:
  name: letsencrypt-prod
spec:
  acme:
    server: https://acme-v02.api.letsencrypt.org/directory
    email: ***
    privateKeySecretRef:
      name: letsencrypt-prod
    solvers:
    - http01:
        ingress:
          class: nginx

I have followed the following guide to get everything installed:
https://learn.microsoft.com/en-us/azure/aks/ingress-static-ip#create-a-ca-cluster-issuer

It is working on our development environment just fine, however for this new environment it seems to not want to issue an actual CertificateRequest. The ClusterIssuer resource is showing as ready

Has anyone encountered this before, or know what to do? My searches so far have yielded nothing.