nextcloud / nextcloud/notify_push
Redis behind a TCP load-balancer not supported
Open
Nobody has claimed this yet.
bug
enhancement
- Dominant language
- Rust
- Stars
- 344
- Forks
- 64
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
If Redi is behind a TCP Load-Balancer, both Nextcloud server and PHP sessions works fine, but not notify_push
- If IP is Redis server (10.1.0.1) everything works fine
- If IP is a Load Balancer/Proxy (10.1.0.2->10.1.0.1, tested with both Nginx and HA Proxy),
notify_pushoutputs:
Failed to setup redis subscription: Error while running redis query
WARN [notify_push] src/lib.rs:418: Redis server disconnected, reconnecting in 1s
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
Start in src/lib.rs around line 418, where the Redis server disconnect and reconnect warning is reported, and trace the subscription setup path. Reproduce the issue using a TCP load balancer or proxy between notify_push and Redis, as described with Nginx and HAProxy. Done means Redis subscriptions work through the proxy without the reported query error or repeated disconnects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redis, rust
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100