Multiplayer Beta Not Working - No Avatars and Version Mismatch Errors on Self-Hosted

  1. My goal: Enable real-time collaboration using Retool's multiplayer beta feature so multiple engineers can edit applications simultaneously

  2. Issue: Multiplayer feature appears broken - we don't see avatar/cursor movements when multiple users are in edit mode, and making changes triggers "Failed to save" errors for other users with message: "Your editor is behind the latest version of this app. The current edit you made and any future edits you make will be lost. Please refresh the page."

I'm seeing a lot of the same errors that users were reporting in this topic: Can We Still Disable Multiplayer Editing? External Workflow (VS Code) Now Frustrating - #10 by Erin_Masatsugu

  1. Retool version & hosting setup (Docker, K8s, cloud provider, etc.): Version 3.223.0 (edge), self-hosted

  2. Error message(s) or screenshots: [See attached screenshot showing "Failed to save" error dialog]

  3. What I've tried so far:

  • Enabled multiplayer in Settings > Beta
  • Attended office hours but couldn't get resolution
  • Multiple engineers tested simultaneously editing same app
  • Refreshing page (temporarily works but error returns)

Wondering if there's a specific feature flag or additional configuration needed for self-hosted multiplayer functionality?

Hi @micriver ,

Thanks for reaching out. There are some additional considerations when configuring multiplayer for self-hosted environments.

Can you share more details about what your multiplayer infrastructure looks like, as well as what Retool version you're on?

Best,
Erin

Thanks for the quick reply!

Version 3.223.0 (edge), self-hosted

And then our underlying infra is running on terraform AWS Fargate and ECS. I work with our sysops team to upgrade and manage our instance so I could be mislabeling the infra above

Oops I'm sorry I didn't realize you already shared some of that info in the original post!

Do you know if you have multiple multiplayer pods running or just 1?

Also, is this your first time setting up multiplayer in this instance or is this a regression from prior behavior?

No worries at all!

I'm not sure what multiplayer pods are, and I think we're just running one for now because I've only just flipped the switch in the settings under beta. I couldn't find anything about pods in the docs. Or in the blog post.

And this is the first time setting up multiplayer in this instance.

Multiplayer requires some infra changes for self-hosted deployments, specifically spinning up a dedicated multiplayer process and making sure any ingress supports forwarding WebSocket upgrade requests to that process. Happy to jump on a call with you / whoever would have more context on your infra layer!

Yes we'd love that, how can we coordinate?

Can you DM me your email address?