Redis with Digital Ocean SSL_VERIFY_NONE
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 17.6k
- Forks
- 2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 40
Description
Issue
Can't use Digital Ocean Redis instance with SSL_VERIFY_NONE. When client does request to redis instance, this request doesn't respond few minutes without error.
If you know how it can be correctly done, please describe.
Environment
- Node.js Version:
10.19.0
- Redis Version:
6.0.9
- Platform:
Digital Ocean (for Redis), Ubuntu 20.04 (for Node.js app)
Contributor guide
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
No source file or test is named. Start by reproducing the connection against a Digital Ocean Redis 6.0.9 instance from the reported Node.js environment with SSL_VERIFY_NONE, then trace the node-redis TLS connection path; done means the request responds without hanging or the supported configuration and limitation are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, redis, typescript
- Domain
- backend, databases, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100