Generating a separate server block for every certificate is the solution.
Since you are probably not managing the configuration by hand at this
scale, use your favourite configuration management tool with a well-cooked
template to generate nginx' configuration.
---
*B. R.*
On Sat, Dec 19, 2015 at
On Tue, Dec 15, 2015 at 01:01:15PM +0300, Maxim Konovalov wrote:
> On 12/15/15 12:53 PM, Valentin V. Bartenev wrote:
> > On Tuesday 15 December 2015 09:44:45 Aleksey Portnov wrote:
> >> Hello!
> >>
> >> Is it possible and correct something like:
> >>
> >> server {
> >> listen 1.1.1.1:443 ssl;
>
>From what you provided, I do not see anything unexpected...
Enabling threads usage with thread_pool and aio threads enables
asynchronous file reading/writing.
The connections_writing stat indicates... the number of connections to
which the server is writing a response.
Since you are working asyn
This doesn't seem to be an nginx issue. The presence of the "X-Powered-By:
HHVM/3.11.0" in your response means your backend is the one issuing the 302
redirect, so you should investigate that instead of nginx.
On Sat, Dec 19, 2015 at 5:11 PM, Xavier Cardil Coll
wrote:
> On this setup, there is a
smtp_auth set + xclient on
smtp_auth none + xclient off
?
---
*B. R.*
On Fri, Dec 18, 2015 at 8:08 PM, Cugar15 wrote:
> Hello,
>
> I'd like to build a smtp Proxy with nginx (v1.8.0) and postfix (v2.9.6)
> on
> Debian7.
>
> Somehow I'm stuck with the following problem:
>
> 1) Configuration1:
>
On this setup, there is a server directive listening to port 80 that
returns www to non www and returns 80 to 443.
The second server is Nginx as SSL terminator, so it's an SSL virtual host,
that proxies the request to Varnish, and the last server is the last host
on the chain, that processes and s
