Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure TURN server is correctly configured #3478

Open
abe-njama opened this issue Mar 21, 2024 · 6 comments
Open

Ensure TURN server is correctly configured #3478

abe-njama opened this issue Mar 21, 2024 · 6 comments
Assignees
Labels
automation Continuous integration issues and other automation improvements help wanted Extra attention is needed question Further information is requested

Comments

@abe-njama
Copy link
Collaborator

Ensure TURN server is correctly configured (e.g. enough files/ports, trying to negotiate STUN first, sensible timeouts to drop connections, cli accessible for diagnostics, etc.) Maybe make an easy nix-shell image or docker container of a properly configured server for easy/experimental replication.

@steveej
Copy link
Member

steveej commented Apr 16, 2024

closing in favor of holochain/sbd#20

@steveej steveej closed this as completed Apr 16, 2024
@steveej steveej reopened this Apr 25, 2024
@steveej
Copy link
Member

steveej commented Apr 25, 2024

reopened becasue we need to maintain the TURN infrastructure for a while longer than initially expected when SBD started emerging.

@steveej steveej added the automation Continuous integration issues and other automation improvements label Apr 25, 2024
@steveej
Copy link
Member

steveej commented May 24, 2024

@neonphog do you think there's anything for us to do here? my preference is to let the TURN infrastructure be as is until it can be phased out, and close this issue.

@neonphog
Copy link
Contributor

neonphog commented May 24, 2024

@steveej - We should weigh the risks of running the patched version that can have smaller timeouts on the sessions. If we set them to 20 seconds instead of 10 minutes, that gives our servers 30X the capacity given the majority of the connections are not used.

If we are not comfortable with taking on that risk, then, yes, this story should be considered complete.

@steveej
Copy link
Member

steveej commented May 27, 2024

personally i'd rather not take that risk, because of the discouragement on parts of the coturn maintainers.

@steveej steveej added help wanted Extra attention is needed question Further information is requested labels Jun 13, 2024
@steveej
Copy link
Member

steveej commented Jun 25, 2024

@abe-njama let's finalize this in our meeting tomorrow please.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation Continuous integration issues and other automation improvements help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants