The SSL certificate for www.bharatelectricpanel.com is currently stuck issuing because the CNAME record is pointing to an outdated target (4as126jl.up.railway.app) instead of the required target (sqg9ge7s.up.railway.app). For bharatelectricpanel.com, the CNAME record is missing entirely and needs to point to isswwvna.up.railway.app. Please update both CNAME records in your Cloudflare DNS settings (with proxy disabled/grey cloud) and the certificates will issue automatically once the records propagate.

Hi, I ensure they have been updated, still it has not being resolved.

The certificate for bharatelectricpanel.com is now valid and working. However, www.bharatelectricpanel.com still shows the CNAME as not pointing to the correct target (sqg9ge7s.up.railway.app), and the public DNS is resolving to Cloudflare IPs, which means the Cloudflare proxy (orange cloud) is enabled. You need to disable the Cloudflare proxy (switch to grey cloud / DNS only) for the www CNAME record so our system can verify the record and issue the certificate.

I have updated to dns only, but the website is still showing not secure status for both bharatelectricpanel.com and www.bharatelectricpanel.com

The www.bharatelectricpanel.com CNAME is now correctly pointing to the right target and the SSL certificate is currently in the process of being issued (finalizing). The certificate for bharatelectricpanel.com is already valid, though the CNAME for the root domain still needs to be updated to point to isswwvna.up.railway.app. Please allow a few minutes for the www certificate to finish issuing, and it should resolve automatically.

SSL has been updated. Thanks, but I still have not secure on the webpage?

Both SSL certificates are now valid on our side. However, both domains are currently resolving to 151.101.2.15, which is not a Railway IP, so traffic is not reaching us. For the root domain, our system still shows the CNAME as needing to point to isswwvna.up.railway.app, and for www, it needs to point to sqg9ge7s.up.railway.app. Please ensure both CNAME records are set correctly in Cloudflare with the proxy disabled (grey cloud), then try loading the site in an incognito window or after clearing your browser cache.