I'm about to embark on creating 12000 vhosts

[Ben Schmidt]

Hi Richard,

we have experience with around 1/4th the vhosts on a single Server, no
Issues at all.
Reloading can take up to a minute but the Hardware isn't what I would call
recent.

The only thing that you'll have to watch out are Letsencrypt rate Limits >
https://letsencrypt.org/docs/rate-limits/
#####
/etc/letsencrypt/renewal $ ls | wc -l
1647
#####
We switched to using SAN Certs whenever possible.

Around 8 years ago I managed a 8000 vHosts Webfarm with a apache. No Issues
ether.

Cheers,
Ben

On Mon, Feb 11, 2019 at 4:16 PM rick_pri <nginx-forum at forum.nginx.org>
wrote:

> Our current setup is pretty simple, we have a regex capture to ensure that
> the incoming request is a valid ascii domain name and we serve all our
> traffic from that.  Great ... for us.
>
> However, our customers, with about 12000 domain names at present have
> started to become quite vocal about having HTTPS on their websites, to
> which
> we provide a custom CMS and website package, which means we're about to
> create a new Nginx layer in front of our current servers to terminate TLS.
> This will require us to set up vhosts for each certificate issued with
> server names which match what's in the certificate's SAN.
>
> To keep this simple we're currently thinking about just having each domain,
> and www subdomain, on its own certificate (LetsEncrypt) and vhost but that
> is going to lead, approximately, to the number of vhosts mentioned in the
> subject line.  As such I wanted to put the feelers out to see if anyone
> else
> had tried to work with large numbers of vhosts and any issues which they
> may
> have come across.
>
> Kind regards,
>
> Richard
>
> Posted at Nginx Forum:
> https://forum.nginx.org/read.php?2,282986,282986#msg-282986
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20190211/1335f6ad/attachment.html>