HTTPS certificate error

[liule]

Bug description

I deployed a new postog in AWS and prompted success through helm chart, but the HTTPS certificate was wrong in the end. The certificate prompt was "kubernetes progress controller fake certificate"

If helm install or upgrade failed include your values.yaml (without sensitive data) and output from kubectl describe nodes.

values.yaml

cloud: "aws"
ingress:
hostname: posthog...*
nginx:
enabled: true
letsencrypt:
enabled: true
certManager:
enabled: true

clickhouseOperator:
storage: 100Gi

postgresql:
persistence:
size: 50Gi

kafka:
persistence:
size: 20Gi
logRetentionBytes: _8_000_000_000

web:
replicacount: 3

worker:
replicacount: 3

plugins:
replicacount: 3

How to reproduce

Environment

• helm-chart & EKS

Additional context

Thank you for your bug report – we love squashing them!

[tiina303]

Could you check in /preflight & see if SSL/TLS certificate has a green checkmark or not? If yes, then I'd trust that, you can also try visiting from incognito or someone else from a different location. Browsers sometimes see recent changes as suspicious, which is great for web safe usage normally, but can throw us off here.

[liule]

Sorry, I didn't see the green checkmark

[tiina303]

If you click on either just experimenting or live implementation - you'll see what's up/what's not.

[liule]

SSL/TLS certificate has a green checkmark, but After entering, the certificate is still wrong

[tiina303]

Then we're likely all good. Did you try incognito or a different browser? Are others also seeing it be invalid? Can you give me the link to your instance?

It can take time for the certificate to become valid + as I mentioned before

Browsers sometimes see recent changes as suspicious, which is great for web safe usage normally, but can throw us off here.

[liule]

https://posthog.m.umu.co/

[tiina303]

That link doesn't look like PostHog to me, I see the "Welcome to OpenResty!" page & no certificate errors

[liule]

13.113.132.190 posthog.m.umu.co

[liule]

Sorry, You need to add a host record. I haven't mapped DNS yet

[tiina303]

I can't access that IP either.

[liule]

[fuziontech]

👋 Hey @liule. You need to setup your DNS before the cert will be issued via lets_encrypt
https://cert-manager.io/docs/configuration/acme/

Currently the URL you provided is going to some OpenResty service (and not PostHog). Once you have your DNS records setup correctly to point to the NGINX ingress controller on your Kubernetes cluster cert-manager should grab a new cert from let's encrypt and you'll be good to go!