coracle/flotilla
1
6
Fork 24
Code Issues 42 Pull Requests 2 Actions Packages Projects 5 Releases Wiki Activity

Voice calls timing out #174

New Issue
Closed
opened 2026-04-08 17:11:26 +00:00 by hodlbod · 7 comments
hodlbod commented 2026-04-08 17:11:26 +00:00
Owner
Copy Link
Copy Source

When I try to join a voice call I get "Connection timed out. Please check your network and try again." I also noticed that the message passed to whenTimeout is never used, which would be worth cleaning up.

When I try to join a voice call I get "Connection timed out. Please check your network and try again." I also noticed that the message passed to whenTimeout is never used, which would be worth cleaning up.
hodlbod added this to the Current milestone 2026-04-08 17:11:26 +00:00
hodlbod added the prioritydev labels 2026-04-08 17:11:26 +00:00
mplorentz was assigned by hodlbod 2026-04-08 17:11:26 +00:00
mplorentz commented 2026-04-08 21:03:09 +00:00
Collaborator
Copy Link
Copy Source

@hodlbod I am only able to reproduce this in Firefox when using localhost from pnpm run dev. That's a known issue, Firefox doesn't support WebRTC on localhost for some reason. Is that where you are seeing the error? It works for me on Chromium and Safari and Firefox at https://shipwreck.scuttle.works (where I have deployed the video call branch).

@hodlbod I am only able to reproduce this in Firefox when using `localhost` from `pnpm run dev`. That's a known issue, Firefox doesn't support WebRTC on localhost for some reason. Is that where you are seeing the error? It works for me on Chromium and Safari and Firefox at https://shipwreck.scuttle.works (where I have deployed the video call branch).
mplorentz commented 2026-04-09 19:36:10 +00:00
Collaborator
Copy Link
Copy Source

For posterity Jon is seeing this in Zen browser. I will try to reproduce with that.

For posterity Jon is seeing this in Zen browser. I will try to reproduce with that.
mplorentz commented 2026-04-13 18:50:48 +00:00
Collaborator
Copy Link
Copy Source

@hodlbod I am pretty sure the issue with Zen is the same as the issue with Firefox, given that Zen is a fork of Firefox. I tested in Zen and can reproduce the connection error when flotilla is running on localhost, but not when it's running at shipwreck.scuttle.works. Can you take the video calls for a spin at https://shipwreck.scuttle.works and confirm that you see the same?

We can leave this ticket open to handle the whenTimeout error.

@hodlbod I am pretty sure the issue with Zen is the same as the issue with Firefox, given that Zen is a fork of Firefox. I tested in Zen and can reproduce the connection error when flotilla is running on `localhost`, but not when it's running at `shipwreck.scuttle.works`. Can you take the video calls for a spin at https://shipwreck.scuttle.works and confirm that you see the same? We can leave this ticket open to handle the whenTimeout error.
hodlbod commented 2026-04-13 21:10:56 +00:00
Author
Owner
Copy Link
Copy Source

I was able to replicate it once on your deployment on first load, but then it worked twice. So it does seem to be a genuine race condition; maybe a cold start issue. Raising the timeout would probably do the trick.

I was able to replicate it once on your deployment on first load, but then it worked twice. So it does seem to be a genuine race condition; maybe a cold start issue. Raising the timeout would probably do the trick.
Khushvendra commented 2026-04-14 19:15:06 +00:00
Contributor
Copy Link
Copy Source

@hodlbod Is this issue being worked upon? (I dont mind taking this up :) )

@hodlbod Is this issue being worked upon? (I dont mind taking this up :) )
Khushvendra was assigned by hodlbod 2026-04-14 19:32:22 +00:00
hodlbod commented 2026-04-14 19:32:35 +00:00
Author
Owner
Copy Link
Copy Source

Sure, feel free to take a look.

Sure, feel free to take a look.
Khushvendra commented 2026-04-14 20:47:20 +00:00
Contributor
Copy Link
Copy Source

@hodlbod I am defaulting to 15s timeout as opposed to the current 5s timeout (to match livekit's default and as anything in 5s to 10s range seems too agressive)

@hodlbod I am defaulting to 15s timeout as opposed to the current 5s timeout (to match livekit's default and as anything in 5s to 10s range seems too agressive)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
design
For issues related to design work. Development should be done in another issue and refer back to this one.
 dev
Issues related to development work
 easy
Issues that can be executed on by new contributors
 idea
For issues that aren't yet actionable
 priority
For issues related to high priority features and bugs
 usability
Issues that have to be validated with real live human beings.
No Label dev priority
Milestone
No items
No Milestone Current
Projects
Clear projects
No project
Assignees
Clear assignees
hodlbod (hodlbod) mplorentz (Matt Lorentz) sakshamjain (Saksham Jain) sondreb triesap userAdityaa (Aditya Chaudhary)
No Assignees mplorentz Khushvendra
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coracle/flotilla#174
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?