You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
One the fly 0 downtime/0 connection drop SSL cert generation.
Describe the solution you'd like
Actually it is not possible to generate on the fly certs so it makes the system depends of periodics or external url triggering.
You may be aware of lua's version ssl_certificate_by_lua that works on the fly.
I know one of the limitation is coming from njs that does not allow usage of async functions in js_set, blocking on the fly generation in acme.js_cert and acme.js_key, but have you discuss this situation with nginx/njs project to be able to provide something alike ssl_certificate_by_lua (basically a js_set with async allowed) ?
Describe alternatives you've considered
ssl_certificate_by_lua but I would prefer to stick on NJS as I already have usage of it and not of lua's mod.
Thanks for your work!
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
One the fly 0 downtime/0 connection drop SSL cert generation.
Describe the solution you'd like
Actually it is not possible to generate on the fly certs so it makes the system depends of periodics or external url triggering.
You may be aware of lua's version
ssl_certificate_by_lua
that works on the fly.I know one of the limitation is coming from njs that does not allow usage of async functions in
js_set
, blocking on the fly generation inacme.js_cert
andacme.js_key
, but have you discuss this situation with nginx/njs project to be able to provide something alikessl_certificate_by_lua
(basically ajs_set
with async allowed) ?Describe alternatives you've considered
ssl_certificate_by_lua
but I would prefer to stick on NJS as I already have usage of it and not of lua's mod.Thanks for your work!
The text was updated successfully, but these errors were encountered: