Let's Encrypt Conflict with a CNAME
Hi, just a quick recap of an issue I ran into about ten days ago—it might be helpful to others. A content creator client wanted a subdomain for his media kit, hosted on an external service; he just wanted it to point to it properly... Well, I created the CNAME without giving it much thought, and it worked fine in terms of DNS resolution. Except that myVesta, on my personal server at OVH, kept trying to generate a local Let’s Encrypt certificate for that subdomain every time the renewal cron job ran, and it crashed every time because the certificate was already being managed by the external SaaS provider—resulting in an ACME challenge conflict. I spent a little under two hours on it before realizing that I had to completely exclude the subdomain from the list of domains managed by myVesta for SSL—basically, remove it entirely from the certificate settings panel (while keeping the DNS active elsewhere, with the direct registrar). Once that was done, there were no more conflicts; the external certificate does its job without a hitch, and myVesta stops interfering. That’s it. Does anyone have a cleaner way to manage this kind of external subdomain directly in myVesta, without having to manually exclude it every time?
