A software developer and Linux nerd, living in Germany. I’m usually a chill dude but my online persona doesn’t always reflect my true personality. Take what I say with a grain of salt, I usually try to be nice and give good advice, though.

I’m into Free Software, selfhosting, microcontrollers and electronics, freedom, privacy and the usual stuff. And a few select other random things, too.

  • 0 Posts
  • 99 Comments
Joined 5 months ago
cake
Cake day: June 25th, 2024

help-circle



  • hendrik@palaver.p3x.detoSelfhosted@lemmy.worldMatrix coturn issues
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    3 days ago

    Check your indentation. I’m not sure if Lemmy is messing with that, but there seems to be an additional erraneous space before turn_username and password in your config. And the dash should (I guess) be indented two spaces further than the previous line and then one space after the dash. I’m not sure if it’s that.


  • hendrik@palaver.p3x.detoSelfhosted@lemmy.worldMatrix coturn issues
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    3 days ago

    Alright. I believe that means you need to fix your DNS.
    turn.domainexample.com” is pointing to a different server, and not the one running coturn.

    Do you use Cloudflare as a DNS provider? I mean I don’t know how that works, since I’ve never used it… But judging by the following documentation: https://developers.cloudflare.com/dns/manage-dns-records/reference/proxied-dns-records/

    I believe you need a dedicated record for the turn subdomain that’s not “Proxied”, but “DNS only”.

    But(!) there seems to be a caveat. There is a note on that page, saying: “If you have multiple A/AAAA records on the same name and at least one of them is proxied, Cloudflare will treat all A/AAAA records on this name as being proxied.” I believe that means you can’t point one of the subdomains directly at your VPS. At least not with Cloudflare DNS.

    Edit: I’m not sure though, why putting in the IP address doesn’t work… I think that should work. I’m not sure what Dendrite does in the background. Have you added the correct secret or username/password and set the correct transport type (TCP/UDP)? Maybe you could add the port number if it’s non-standard…


  • hendrik@palaver.p3x.detoSelfhosted@lemmy.worldMatrix coturn issues
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    3 days ago

    Once the TURN testing tools I linked, work with the domain name: You should be able to fill out the turn section in config/dendrite.yaml with that. It should be something like turn:turn.domainexample.com?transport=udp.

    Maybe your DNS isn’t pointing to the correct IP? You could try pinging it, or use the command dig A turn.domainexample.com and see if it returns the correct IP for the VPS.

    (Edited)


  • hendrik@palaver.p3x.detoSelfhosted@lemmy.worldMatrix coturn issues
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    3 days ago

    Concerning your Edit:

    You might now want to try putting in the correct address into config/dendrite.yaml. That has a “turn” section. You could try and add an URL with the IP address (instead of a domain name) in “turn_uris”.

    I mean I’m probably the wrong person to ask. I don’t use Cloudflare. And I also skipped Dendrite and went for the Conduit server… What’s your reasoning to use Cloudflare in the first place? Maybe you want to get rid of it? Or add another supdomain to your DNS that directly points at your server, and have the turn_uri be that, so you don’t have to put IP numbers into that section…


  • I am getting feedback but i am unsure if it is saying it can connect

    It does connect if you get a line with “srflx” or “relay”. Otherwise it does not connect. And your whole coturn server might not be reachable at all.

    I am using cloudflare to setup dns record for coturn on my purchased domain. Is that still an issue?

    Well, that depends on how you set it up. What domain name are you using for coturn? (The one you put in the tester.) Where does it point to? To your cloudflare tunnel? To your real IP? And if it’s pointing at cloudflare’s endpoint: Do you have a paid subscription and set up Spectrum to forward the packets?



  • You can always ask the student body. If they’re doing a good job, they’re networked and know people and procedures. Sometimes the IT helpdesk people are knowledgeable and know who makes those kinds of decisions.

    And I think server hosting and paying for that might work differently than in normal life. A university has quite some IT infrastructure. Maybe they have a free VPS to spare for things like that. Maybe it has to be super secure, intergrated into the single sign-on… It’s more a political decision. Could be anywhere from free, to you need to pay half a person’s salary to moderate and maintain the instance to their (high) standards.






  • Well if you want a proper upgrade, 40TB plus redundancy and space for a GPU, I’d say you don’t want a mimi PC but a full-blown one. I built my server myself from components. It’s hard to find good numbers on power consumption and that was one of my main concerns. I had a look at some PC magazines and what kind of mainboards they recommend for a home server. Figured I wanted 6 SATA ports and I started from that. Unfortunately said magazine doesn’t have a good article right now, so I don’t know what to recommend. Another way is to look for refurbished PCs. If they’re some brand like Lenovo or Dell, you’ll find the specs online. With a N100 mini pc, I’m not so sure if that’s a big step up from your current setup… I don’t think they have more internal harddrive ports or slots for GPUs than your current laptop.


  • Very good answer. I’ve also spent some time analyzing some red herrings when it was something else like a bad cable or connector. And by the way, you can use the same keys in journalctl as in the usual pager (less(?)) so hit / and search for ‘unmount’, ‘disconnect’, etc. And then scroll through the log and find out what led to the situation.