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.
My domain is: balasolu.com
I ran this command: migrated from azure to vercel
It produced this output: migrated from azure to vercel
My web server is (include version): vercel nextjs
The operating system my web server runs on is (include version): vercel nextjs
My hosting provider, if applicable, is: vercel
I can login to a root shell on my machine (yes or no, or I don't know): yes on my machine
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
no, i am using git
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot):
i dont access this stuff
i used to self host my content on some boxes but i recently decided to move to serverless to save some serious $$$.
anyways, i set up letsencrypt on all of my domains and never had an issue.
since the migration, the certbots have been deactivated and the old certs do not exist. all of that is shut down.
i am experiencing a huge spam of 404 trying to challenge the old certs but of course they do not exist.
here's an example of what i am experiencing. 18MB and over 5000 unique requests...
my current cert is entirely different and works properly already.
how do i stop letsencrypt from spamming my domain attempting to challenge an uncliented cert that doesn't exist?