11
Matrix coturn issues
(lemmy.ml)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Nov 2024
11 points (100.0% liked)
Selfhosted
40296 readers
169 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Make sure cloudflare proxy is disabled on that DNS record.
Just barely fixed that! Thanks! I have another issue thst I fommented about though:
Progress has been made!
So I got it working with the domain name. The turn testing tools now respond with relay and pin point the vps server! Nice!
However when I put the info into the matrix dendrite.yaml it still crashes. The logs say
"Invalid config file: yaml: line 210: did not find expected key"
"Invalid config file: yaml: line 206: did not find expected " - " indicator"
Line 210 and 206 refer to the turn section which is formatted:
turn: turn_user_lifetime: "5m" turn_uris: - turn:turn.exampledomain.com?transport=udp - turn:turn.exampledomain.com?transport=tcp
Throw the whole thing into a YAML linter: https://www.yamllint.com/ and see what it says. Likely a spacing/indent format error or something like that.