Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
Given you did not answer nearly all of the questions on the form I think you should ask your hosting provider for help. If you were a skilled server admin you would know at least some of those answers and perhaps we could give more detailed advice.
You have a very unusual configuration which I guess was done by your hosting service. You have a cloudflare edge server replying to requests but your DNS only has one A record. Normally with a proxied Cloudflare domain you would have at least two and often also have AAAA records (you have none).
Usually Cloudflare is also then your DNS provider but it is not in this case. The HTTPS failure is very unusual for a domain proxied at Cloudflare.
I can easily reproduce a problem with your www domain. It does not look like a Let's Encrypt problem but significant configuration problems with your server and/or DNS.
yes, i am not but I have tried to work with Lovable support to no avail, and then turned to GoDaddy and they changed the the A record showing the www and same IP as the first A record, but that has not helped either. www have been troubleshooting for the past week. when i did a look up on ssl.com that's when i saw the cert assigned from Lets encrypt. so hence why i am reaching out.
that said we had gone back and forth last week for the www between A record and CNAME but neither have worked.
I don't know anything about Lovable and there is little doc to work with.
Have you always used them as your hosting service? I see you have a long history of getting Let's Encrypt certs. Something must have changed to have this problem start recently.
No sir, we just started using them to design sites and of course this was the first one. The Domain is registered with GoDaddy, this is a site similar to Squarespace, so it was just a connection between the two providers.
we had a problem with the www since day one. of connection. i presume my next will be to change the DNS back to the A record for the www and contact Cloudflare, yes?
Well, if you can't get your site working with them and they cannot help you I'd suggest going back to your prior service.
I think that Cloudflare server is just a part of how Lovable sets up their service so would go away once you leave them. You would know if you setup Cloudflare proxy for your domain. And, they would have to be your DNS provider and it isn't.
Your DNS should contain the public IP address(es) for your server. You would update your DNS once you have a new hosting service setup.
thank you for your reply as well. no we are just using GoDaddy as the domain registrant and DNS configurations. We just started using Lovable.dev and when i connected websites using Shopify and Squarespace there is usually a number for DNS settings, but in the case of Lovable.dev, it just put in 2 A records one for the @ and one for the www both using the same IP.
just having an issue connecting to the www, without it it works perfectly.
i a now just trying to figure out who to talk to since lovable is telling me to contact Cloudflare.
ALL Thank you for your time. Apparently the issue was with propagation. we had a glitch happen early on in the release of the site regarding the www.domainname.com, and immediately started troubleshooting. This turned out to be the problem as we apparently started doing this too fast, even though it was.... 48 hrs. later.... hence tried to make all sorts of changes regarding the 1 DNS entry. Well after a week or so trying all sorts of angles, we set it back to what Lovable wanted and ..24 hours later.. we are up and running normally.
thank you to everyone that tried to help Much Appreciated.
Glad you got it working! Yeah github pages behaves the same and sometimes you have to set the custom domain to something else then back again to force it to update everything.
