Let's Encrypt certificate not being set up correctly for a newly added domain
I have a dokploy server serving up a website app on a subdomain to preview the new site before I tried to shift the DNS record to the new site. I'm using version v0.18.3.
I mistakenly added the domain before setting up the A/AAAA records in DNS, which caused the certificate to fail to load and is now presenting as the default Traefik cert. I've tried deleting the domain and adding it again after verifying that the DNS records were reachable, but I still get the default cert.
I also noticed that if I try reloading Traefik through the Web Server page, I get an error, but the management page stays up, and the page still loads with the incorrect certificate.
What can I try to attempt to obtain the correct certificate?
1 Reply
actually, looks like the problem with the cert has just resolved, the browser is now showing the valid cert, but chrome still shows the broken lock icon.
thanks for rubberducking!