Thank you very much... So simple solution !
On 1/13/19 2:20 PM, Anoop Alias wrote:
You can reload instead of restart and nginx would continue working on
old config if the new one is invalid
On Sun, Jan 13, 2019 at 2:31 PM Pierre Couderc <[email protected]
<mailto:[email protected]>> wrote:
In case of bad certificate (certificate file missing for exemple),
nginx
fails to restart.
Is there a way to avoid that ?
There may be an error on one site without stopping all other
correct sites.
This occurs particularly in case we remove an old site, and make an
error in configuration files : a few months later, let's encrypt
tries
to renew the certificate in the night and fails, then restarts nginx
which fails because missing a no more used certificate, and the full
site is stoped....
Thanks.
PC
_______________________________________________
nginx mailing list
[email protected] <mailto:[email protected]>
http://mailman.nginx.org/mailman/listinfo/nginx
--
*Anoop P Alias*
_______________________________________________
nginx mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________
nginx mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx
