config reverse proxy nginx to apache2

[Anoop Alias]

Is this apache behind nginx or nginx behing apache?.

Whichever be the case - The rule is that the frontend (or the server
terminating 443 ) need to have the cert configured as the web browsers need
to talk to it with ssl .So in short if nginx is the frontend it must have
the SSL eventhough apache(if the proxy backend) also has ssl on it.

All your individual vhost need individual ssl entries.  If 2 vhost use the
same cert all you have as an advantage is you can use the same filenames .



On Sat, Jan 2, 2016 at 3:27 PM, Thierry <lenaigst at maelenn.org> wrote:

> Bonjour,
>
>          I  have  made  some  modification on my  nginx reverse proxy
>          server.
>
>          I have add these lines:
>
>          listen 445;
>          server_name *.domain.org;
>          ssl on;
>          ssl_certificate /etc/ssl/certs/file.crt; (same as apache)
>          ssl_certificate_key   /etc/ssl/private/file.key;  (same  as
>          apache)
>          ssl_protocols  TLSv1 TLSv1.1 TLSv1.2;
>
>         I  have  access to my web server from outside, but I do not
> understand how
> the ssl certificate is managed.
>
>         Why  do  I  need  to add on nginx those certificates ? This is
>         already handled by my apache server through his vhosts.
>
>         How  to  deal  when  I have three vhosts, 2 have the same ssl
>         certificate but the third one his using a different one.
>
>         Thx
>
>
>
> --
> Cordialement,
>  Thierry                          e-mail : lenaigst at maelenn.org
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>



-- 
*Anoop P Alias*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20160102/0e9d67cf/attachment.html>