The service status at top says “Starting” while the pods say running. Why would this happen?
Similar behavior here as well. The service status shows error while the current status shows running for 8 days
Hey @0xbitmonk,
Would you mind shing your Qovery console URL for those services so I can have a look?
On the first example where service is starting, did you trigger a deployent on an already running service?
Cheers
and
Hey @0xbitmonk,
Still digging but issue seems linked to custom domain being wrongly configured, can you confirm you’ve set the CNAME generated by Qovery to your DNS provider?
Cheers
Yes, we have this setup correctly. The service is working fine for us otherwise. It’s just that on the Qovery console it shows this status which has been bothering us for something. But nothing is impacted.
And what about the staging one? Because cert-manager is not able to issue the certificate for it.
Also, checking with dig, none of your domain appears as having the CNAME configured, are you sure changes are properly propagated? Which DNS provider are you using?
For staging also, it is configured and works just fine. We have had this issue for months but today only decided to share it with your team.
We are using Cloudflare. We have proxy enabled.
Would you mind updating CNAMES on cloudflare side with the full value provided by Qovery, I am not sure if you redacted data on your screen shot, but CNAME value for staging (alpha-api.***.**z) should be the one having this redacted value: zf4e9e073-***-gtw.***.**ers.sh.
Can you confirm it’s the actual value set on CF side for this domain?
This topic was automatically closed after 2 days. New replies are no longer allowed.