openresty / openresty/lua-resty-websocket

can not use resty redis

Open
#61 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lua
Stars
523
Forks
112
Avg merge
1d 16m
Merged PRs (30d)
2

Description

when i try to connect to the ws server(ws://ip:8081/ws), it raise error

2021/03/25 00:20:34 [info] 16392#16392: *1 client 113.92.35.59 closed keepalive connection
my nginx.conf content
worker_processes 2;
user root;

events {
    worker_connections 1024;
}

error_log logs/error.log debug;

http {
    server {
        listen 8081 reuseport;
        location /ws {
                        access_by_lua_block {
                                local ngx = ngx
                                local redis = require("resty.redis")
                                ngx.log(ngx.INFO, "access stage")
                                local red = redis:new()
                                local ok, err = red:connect("127.0.0.1", 6379)
                                if not ok then
                                ngx.exit(ngx.HTTP_UNAUTHORIZED)
                                end
                        }
        }

    }
}

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the /ws location and its access_by_lua_block in the supplied nginx.conf, then reproduce the request while checking the shown Nginx error output and the resty.redis connection result. Done means the WebSocket request and Redis connection work together without the reported connection failure, with the cause identified from the available logs.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua, redis
Domain
backend, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.