auto-ssl / auto-ssl/lua-resty-auto-ssl
Failed to create ssl certificate
- Dominant language
- Lua
- Stars
- 2k
- Forks
- 184
- PR merge metrics
- No merged PRs in 30d
Description
lua auto-ssl failed to create ssl for some of the domains.
Here is the nginx configuration
########################
lua_shared_dict auto_ssl 1m;
lua_shared_dict auto_ssl_settings 64k;
resolver 8.8.8.8;
init_by_lua_block {
auto_ssl = (require "resty.auto-ssl").new()
auto_ssl:set("allow_domain", function(domain)
return true
end)
auto_ssl:init()
}
init_worker_by_lua_block {
auto_ssl:init_worker()
}
Internal server running on port 8999 for handling certificate tasks.
#################################################
server {
listen 127.0.0.1:8999;
client_body_buffer_size 128k;
client_max_body_size 128k;
location / {
content_by_lua_block {
auto_ssl:hook_server()
}
}
}
Its not working for some of the domains like below
https://meet.webfootprint.co.za
It is creating domain folder in /etc/lua-auto-ssl/ but failed serving for some reason. Pointing to fallback certificate which is default imo. That is failing at browser side.
tried to see error logs. But no luck nothing to see there. Did i missed anything here ? How do we debug on this where went wrong?
Error ssl ref:
https://i.snipboard.io/pyIEDJ.jpg
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the provided OpenResty/nginx configuration, especially the auto_ssl initialization, the internal server on 127.0.0.1:8999, and auto_ssl:hook_server(). Inspect certificate issuance and serving behavior for meet.webfootprint.co.za, along with the relevant error logs and the linked error screenshot. Done means the domain receives its intended certificate instead of the fallback certificate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, nginx
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100