Hello
I have a certificate issue when deploying my helm chart with a custom domain.
Maybe I have omitted something. Usually I don’t have any problems with Qovery nginx ingress and custom domain.
Thanks for your help
Hello
I have a certificate issue when deploying my helm chart with a custom domain.
Maybe I have omitted something. Usually I don’t have any problems with Qovery nginx ingress and custom domain.
Thanks for your help
Hi,
It looks like your DNS record are not correct.
Please go into the Domain section and update them:
Thanks
I do not understand what’s going wrong with my DNS?
If I copy/paste the value of my CNAME it’s working fine. It’s not working when I try to pass by my custom DNS
If you go into your domain registrar and look at the record set, you will see it doesn’t match what Qovery domain configuration asks for.
Please double check the CNAME records you’ve set. Then if you want to validate you can try with dig command (it can take a few minutes after updating your DNS records):
dig CNAME doxxxxx.yourdomain.com
Maybe I’m completely lost , but I see exactly in the dig output the same CNAME created into my service Domain
I just checked, and it looks like you’ve correctly set the first domain ! However, you’ve added a new one containing an error as well.
IMPORTANT: If you have a single issue within the list of your custom domain, you won’t have a valid certificate!
After updating this last record, you should be good
Nope.
Always same problem site Not Secure.
I think you forgot to add the 2nd record name, where the wildcard is present. It doesn’t look to resolve anything.
Why would I need *.subdomain.domain.sh CNAME if I only use subdomain.domain.sh?
It’s working
Good news !!! As soon as you’re using more than one port, we need the wildcard
Ok
Thanks a lot for your patience and time
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.