Issue with STUN/TURN #672
Labels
No Label
administration
Akkoma
Android
Bare metal
bug
Communication
Community
Cryptpad
Discussion
Documentation
duplicate
enhancement
etherpad
Feature request
Feedback
finances
Fixed
forgejo
fun_project
Goal 2024
help wanted
Howto
🤔️ Investigate
ios
jitsi
lacre
Lacre Test
ldap
Lemmy
LibreTranslate
low prio
Lufi
macos
Mail
Merch
monitoring
movim
needs_refine
New Auth
Nextcloud
nice to have
on hold
proposal
question
Ready
refined
Roundcube
searX
spam-protection
Staging Server
Themes
TOR
Urgent!
Website
windows
wontfix
xmpp
Yearly Report
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Disroot/Disroot-Project#672
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Message from an user: Ever since the move to the new server, almost all xmpp audio/video calls fail for me: either I'm not audible/visible to the other end, or it's the other way around, no matter who initiated the call. Both accounts on Disroot, both on the same app and the same version (Blabber 3.1.4) that worked perfectly fine before the server switch some time ago. It keeps saying "connecting". Is this a problem with STUN/TURN again? I recall the same thing some years ago with Disroot
Meaz: could that be the same issue than what we have on jitsi?
Yes it's for sure that. I am on it.
I think it's fixed now but need to double check
@numnum which service are you refering to? I still need to add something but looks like I broke the setup and will need to wait with it for cemplete server reboot scheduled for tomorrow morning.
I did manage to have a stable audio/video call over nextcloud and jitsi with about 5 clients. Unless I manage to fix things before, this will need to wait until tomorrow.
@numnum I havent tested xmpp. I will do the needed adjustements tomorrow after the server reboot. I think it should work as before. In worse case scenario I will deploy turn server in the same way I did before the migration though I would prefer not to.
@numnum Nice and sorry for the issues along the way. We can't waste such opportunity though (I have not convince any of my family members to use disroot). I have add some settings please check if it's working now for you.
Strange indeed. I just tested 1on1 call with xmpp (client one on 5G client two on wifi local network behind nat) and worked without issue. I will test dino with multiple users as well as jitsi and nextcloud talk to see if things are working as expected. If so then I could confirm turn server running as it should and problem being something else which we should dig deeper to find.
@numnum can you check if it works for you now?
Great to hear. I tested it as well on xmpp and on nextcloud and seems to be working fine. Great stuff i learned something new in the process too :D
The issue was pretty trivial. In previous setup coturn was running on directly on the baremetal server. This time after the move I decided to deploy it as a container. I havent spent much time on it, just transfered the config from the old one and thought it should work as most of my 1on1 calls were running fine. After we tried to have an internal team metting (normally we use mumble so no issues there) and your report I knew probably need to fix some of the config as of course the current setup is behind NAT and so just forwarding wont work. I quickly found the solution (using external-ip config setting to map public ip's to internal ones) and was sure it should work good. Didnt know what could be wrong. Today I woke up with one thought it my head "You are using wrong IP address you morron". And so checked the config and indeed. one of the two ip's was wrong. Fixed it and tested. So yeah could have been already fixed last week when you reported it but due to that mistake it took longer to realize it.
@numnum yeah easy fixes are usually hardest to find.
Ok. I will close this one for now. Please feel free to create new issue if the problem accurs again.
@meaz fyi I'm making a role for this one just to keep track of things properly. It's half done so in few days it should be done (making templates is so tiring :P )
Quite certain it was fixed back then, but I had some issues recently when using jitsi myself so made issue to re-test properly all services, check edge cases so we know whether the issue is software related (upstream) or limitation of the software, or setup related. In that way we will have a clear view on this for all services providing both audio and video call. #740
@numnum if you have any feedback please share it there. It will help out getting the full picture on that matter.