auto-ssl / auto-ssl/lua-resty-auto-ssl
Error generating new certificates
- Dominant language
- Lua
- Stars
- 2k
- Forks
- 184
- PR merge metrics
- No merged PRs in 30d
Description
Hi.. just notice today that it started to give errors on generating/renewing certificates..
upgraded openresty and the luarocks dependencies. however is still gives errors:
2019/12/06 11:23:46 [error] 6634#6634: *337 [lua] lets_encrypt.lua:51: issue_cert(): auto-ssl: error fetching certificate from storage for : closed, context: ssl_certificate_by_lua*, client: , server: 0.0.0.0:443
2019/12/06 11:23:46 [error] 6634#6634: *337 [lua] lets_encrypt.lua:77: issue_cert(): auto-ssl: dehydrated manual hook.sh failed: env HOOK_SECRET=371ac024d834862be24sd79bd1dd941fcsa0c4f191037692493f156sdffa3f4c28 HOOK_SERVER_PORT=8999 /usr/local/openresty/luajit/bin/resty-auto-ssl/letsencrypt_hooks deploy_cert c.led.ad /etc/resty-auto-ssl/letsencrypt/certs/c.led.ad/privkey.pem /etc/resty-auto-ssl/letsencrypt/certs/c.led.ad/cert.pem /etc/resty-auto-ssl/letsencrypt/certs/c.led.ad/fullchain.pem /etc/resty-auto-ssl/letsencrypt/certs/c.led.ad/chain.pem 1575631426 status: 256 out: deploy_cert
failed to get the expiry date
did i miss the need for some new conf?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the logged failures in lets_encrypt.lua at lines 51 and 77, then inspect the dehydrated manual hook.sh deploy_cert invocation and its “failed to get the expiry date” output. Reproduce certificate generation or renewal with the shown command and determine whether the current certificate paths and hook configuration are valid; done means the expiry date is read and certificate generation succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, nginx
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100