feat: add coturn TURN support - #53
Open
nslsrv wants to merge 1 commit into
Open
Conversation
nslsrv
marked this pull request as ready for review
February 3, 2026 21:33
Contributor
Author
|
Hi, @adamshiervani, just checking in on this PR. I believe this kind of functionality could beneficial for JetKVM users. Could you please find some time to review this PR? Is there something I can do to help move this forward? Thank you. |
|
@nslsrv, does this really work? I also plan on using coturn. |
Contributor
Author
@pietheinstrengholt Yes, it works, I use it to stay independent from Cloudflare. Using my fork currently, which includes this patch, but I'd be happy to merge it to upstream eventually and drop the fork. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Coturn support allows to use own TURN service in self-hosted deployments.
As with Cloudflare, it's used only on client side (client side is responsible for managing relay).
Current cloud-api interface supports only one credentials set, so it's either Cloudflare or coturn, and Cloudflare configuration takes precedence.