Can we issue more than one cert per site? Iâve seen lets encrypt has a 100 domain per cert limit so if I have more than 100 alternate domain names can I issue a second cert?
We offer whitelabel domains for our agency users so we have 133 subdomains at the moment but thats increasing
Nope! Max one certificate per site on our service. The reason you might have less than one per site is if you follow my advice below.
You can of course create multiple sites with the same codebase! Then you can put a bunch of names on the same codebase. The best workflow for âmany subdomainsâ is of course to use a wildcard certificate to cover them all. If you donât do this all certificate operations (e.g. adding a name) will be QUITE slow since lets encrypt essentially processes them one at a time and each one takes a few seconds, so you might consider less hostnames per site (<=20 is a good benchmark, since that is also a lets encrypt rate limit and since we ask for name1, then name1+name2, then name1+name2+name3+⌠as you add the names in our UI. LE has a limit of 20 requests per week for any name, so you can see that weâll hit that weekly limit at 20 names.
I have a site currently being hosted with Cloudflare pointing at Cloudfront/S3 and I want to switch over to Netlify. Iâve switched my staging environment, but noticed that there is a delay between switching the DNS record on Cloudflare to point to Netlify and disabling the proxying and when a certificate is able to be generated with Letâs Encrypt automatically. Is there a best practices way to do this switch to minimize downtime and user-facing issues?
I provided custom domain for my netlify account and i also provided SSL certifcate . but when it try to visit my website by custom link i provided in some browsers it is showing page is not secure. I would really appreciate if somebody can guide me whats the problem. this is my domain âitshaisam.comâ, and this is netlify link â keen-panini-6e3ea7.netlify.appâ . But when it type full path like https://itshaisam.com then its fine, but in some browser when i simply type itshaisam.com when page is loaded it says page not secure.
ThanksâŚ
Hi, @itshaisam, and welcome to the Netlify community site.
In order to troubleshoot, we need to track down what is happening when your browser makes that request. We need the more information about the request in order to do that.
The simplest way to do this is to send us the x-nf-request-id header which we send with every HTTP response.
There more information about this header here:
If that header isnât available for any reason, please send the information it replaces (or as many of these details as possible). Those details are:
the complete URL requested
the IP address for the system making the request
the IP address for the CDN node that responded
the day of the request
the time of the request
the timezone the time is in
Now, if SSL negotiation is failing, then it is almost certain you wonât receive any headers so the details above are remaining option.
We look forward to researching this in more detail and please free feel to add additional questions anytime.
Hello,
I have been trying to renew a certificate for the last two weeks, the actual one is still valid, but the reason for me to request a renewal is that it expires the day before an event that will have massive traffic on the site and I would like to reduce the risk and have that certificate with a further expiration date. Is there a way to debug the update process and see why itâs not working?
hi there, just to be sure, you tried the ârenew certificateâ button in the netlify UI, right? if not, please do, and if you did, let us know what happened?
Hi, yes I have tried that multiple times over the last two weeks. It just opens the modal and after clicking on ârenew certificateâ disappears, the date remains the same though.
Hi, @mrcportillo. You cannot renew the certificate because our service will only do so if at least one of the two requirements below is met:
The list of domain names the SSL certificate covers does not include all domain names listed on the site.
If the SSL certificate will expire in 30 days or less.
The first requirement is obvious. If you change the domain names configured for a site, the SSL certificate needs to be updated to include the new names.
The second requirement is a Letâs Encrypt recommended best practice. The SSL certificates they issue always expire in 90 days and they recommend renewing them 30 days before they expire.
Looking at this siteâs SSL certificate neither requirement is met. The certificate covers all the domain names on the site and it isnât less than 30 days before it expires.
The SSL certificate will expire on June 12th. This means that the renewal will process on May 13th (which may be the 14th for you depending on your timezone). That renewal will be automatic and you wonât need to click anything.
Also, if the renewal fails, we will email you to let you know. Because we renew 30 days before it expires, we will then still have 30 days to troubleshoot.
If there are other questions about this, please let us know.
Trying to activate SSL/HTTPS on a Netlify hosted website but the process seems to be stuck, nothings happen.
Already waited for more than 48h, and still nothing.
I donât have any ârenew certificatedâ button since I am not using Netlifyâs DNS.
I prefer not using them since my customer is also using e-mails with his domain.
I have the feeling that if I stop the process and restart it, itâs going to work.
Can anybody help me ?
I can give you the URL of the website in private message, it is the latest website I hosted on my account.
Hi @coelmay
Just checked, and now the SSL is working !
Donât know if you did something ? Or if it was my attempts from this morning (deleted DNS zone, and created it again).
Iâm having trouble with the âdoist-typist.netlify.appâ site, the Letâs Encrypt certificate is taking forever to be generated. Clicking âRetry DNS verificationâ returns âDNS verification was successfulâ, so Iâm assuming everything is set up correctly.
Is there anything I can do (or that you can do) to speed things up?
Thanks for this post. In my case for speedlab.ag, both requirements are met as the SSL is expired, but when I click provision certificate on netlify, the window closes and it goes back to âUse letâs encrypt certificateâ no matter how many times I try.
The SSL was previously running fine through Netlify and expired 11 days ago. There were no DNS or domain changes. Could you help me in fixing this?