Selfhosted
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!
view the rest of the comments
Have you checked your coturn server works correctly? And answers requests in the first place?
See if you get some lines with type "srflx" or "relay".
(And I believe coturn needs to bypass cloudflare. Unless you have an enterprise subscription, it doesn't do raw TCP/UDP connections. So TURN can't work through a free cloudflare tunnel. You need ports 3478, ... and port-min to port-max open on your VPS. And DNS (at least for coturn's subdomain) point to the correct IP of your VPS.)
So I checked and I do not think it can connect.
I have a cloudflare domain I am using and I am only using cloudflare tunnels for the matrix dendrite server not the coturn vps server. I am using cloudflare to setup dns record for coturn on my purchased domain. Is that still an issue?
EDIT:
so i just tried it with the regular vps ip address instead of the domain I set in the dns records and the test tools you linked say it is working that way.
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.