openresty / openresty/lua-resty-redis
lua tcp socket read timed out, context: ssl_certificate_by_lua*, client: 172.69.58.204, server: 0.0.0.0:443
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 2k
- Forks
- 447
- Avg merge
- 2h 24m
- Merged PRs (30d)
- 3
Description
In my nginx.conf for openresty i am using two Redis one is for storing SSL certificate in AWS cloud and another Redis is in the same server of openresty for cache purposes not sure why I am getting this issue, due to this issue I am getting 500 internal server error in my production.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported nginx.conf setup and the ssl_certificate_by_lua* context, then inspect how the two Redis endpoints are configured when the TCP read timeout occurs. Done would require identifying a reproducible cause for the 500 error and documenting or implementing a scoped fix, but the issue does not name repository files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, lua, nginx, redis
- Domain
- backend, databases, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100