Scalable LiveQuery server - Unable to get message from subscription

[BanalitoRaulito]

New Issue Checklist

• [x] I am not disclosing a vulnerability.
• [x] I am not just asking a question.
• [x] I have searched through existing issues.
• [x] I can reproduce the issue with the latest version of Parse Server.

Issue Description

Unable to get message from subscription (client/utils/initialize.js line: 22)

Steps to reproduce

1. clone git https://github.com/BanalitoRaulito/Scalable-Parse-LiveQuery-Server
2. follow README (docker-compose up --build)
3. navigate to localhost:3000
4. type something to input and click "Add todo"

Actual Outcome

I don't get console log after adding new item (from client/utils/initialize.js line: 22)

Expected Outcome

I expected to get console log after adding new item (from client/utils/initialize.js line: 22)

Environment

Server

• Parse Server version: 3.3.0
• Operating system: macOS Big Sur
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Localhost

Database

• System (MongoDB or Postgres): Mongo AND Redis
• Database version: Mongo 5.0.2 AND Redis 6.2.5
• Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): Localhost

Client

• SDK (iOS, Android, JavaScript, PHP, Unity, etc): React
• SDK version: 17.0.2

Logs

LiveQuery server: "info: Create new client: 19f08667-e7a1-456a-a138-5fe5ec9bc9e9"

[parse-github-assistant[bot]]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[mtrezza]

Could you describe the steps based on the original repository? We don't know which customizations you my have in your fork. Probably the easiest way to demo the issue would be to create a PR with a failing test.

[uzaysan]

I've faced this issue before. When you run multiple parse-server behind the load balancer, you need to specify a redis server in order to parse servers to communicate with each other.

ParseServer.createLiveQueryServer(httpServer,{
  redisURL: 'redis://username:password@server-adress'
});

[mtrezza]

I'm closing this as it does not seem to be a Parse Server issue.

• For help with Parse Platform we recommend our community forum.
• For basic coding questions we recommend Stack Overflow using the parse-platform tag.
• For network and server questions we recommend ServerFault using the parse-server tag

Feel free to comment if you have any questions and we can re-open this issue.