this post was submitted on 18 Dec 2024
20 points (91.7% liked)

Selfhosted

60644 readers
404 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I decided to bite the bullet and switch from dendrite to conduit as many of you have suggested. The only problem is I cannot get my calls to connect. It just says "call connecting..." But never does. I figured it was a turn server issue but if I type in the secret key wrong in my config file calls don't pop up at all. So it is connecting to it to some extent.

I have no idea why dendrite just works with the coturn config setup yet when I apply the exact same methodology with the conduit config file it doesn't connect calls at all but seems to still connect to the turn server.

For my turn server I am using a debian digital ocean droplet. It was working perfectly for dendrite yet does not want to function with conduit.

Any help is appreciated!

EDIT: I am using a combo of element and element x. On element x android (grapheneos) there is no notification for a call. No pop up or anything. On Element android (grapheneos) there is a popup but the call will not connect.

EDIT 2: I am starting to believe it is coturn. I just don't know how I am supposed to configure it any different than dendrite. I was starting to believe maybe conduit isn't reading the config at all. However, it configured the registration key properly. if the secret key is wrong element won't receive notifications either. I have tried altering my coturn.conf on my vps but to no avail.

EDIT 3: so it seems I can join the call on element x. Even though their is no popup indicating I am recieving a call I can go into the chat and click the call button. Once I do I can connect and talk no problem. Maybe the turn server is working after all. (One phone on mobile the other on my home wifi). I judt don't know why regular element won't connect.

EDIT 4: the notification bug in element x seems to be coming from an error with ntfy. I did a notification test in the app and it came up with an error on: "test push gateway" and "test push loop back"

The error for both is:

Http 500

EDIT 5: I think the error has something to do with my conduit server not trusting my ntfy server but I don't know how to fix that.

EDIT 6: Is Conduit just not compatible with the original element client?

EDIT 7: the original element client gets no errors when troubleshooting notifications. It passes all the checks with flying colors. Element x fails the two checks mentioned above.

you are viewing a single comment's thread
view the rest of the comments
[–] ludicolo@lemmy.ml 1 points 2 years ago* (last edited 2 years ago) (1 children)

No I was deploying regular conduit. Now I am trying conduwuit and when I try and connect it says it doesn't support sliding sync. I cannot seems to find it referenced in the config file either.

EDIT: nvm I just read it is not implemented yet on conduwuit. 🥲 kind of a dealbreaker because I am trying to get element x working for group calling.