Audio/Video Call Issues with STUN/TURN behind Reverse Proxy (nextcloud-aio-talk) #4592
-
|
Hi, I'm currently testing Nextcloud AIO, and the setup has been smooth so far. Since I have a reverse proxy in my network, I opted to use the SSL certificate from there instead of creating a new one on the Nextcloud instance. This worked well. However, I'm experiencing issues with Nextcloud Talk. While the app works fine for texting, I can't get audio and video calls to work. I suspect the problem is related to DNS resolution. When I use cloud.example.com, it resolves to my HAProxy instead of directly to Nextcloud AIO, where the STUN and TURN container is located. I tried setting up talk.example.com to go directly to Nextcloud AIO, but that didn't work either. Here's the output from https://webrtc.github.io/. I got some private IPs and ports as results: Would it be best to create a separate STUN/TALK container and manually configure it? If not, any suggestions on how to fix this issue? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
You can manually overwrite the stun and turn server in the talk admin settings. E.g. adding a second subdomain and pointing that via cname at the public ip without overwriting it locally should probably make it work. |
Beta Was this translation helpful? Give feedback.
-
|
Worked like a charm. I did try before posting here, but for some reason it didn't work right away. Maybe I had to clear the cache of my browser or my phone used the old entry STUN/TURN entry. It works now! |
Beta Was this translation helpful? Give feedback.
-
|
you can also port forward the stun port to the nextcloud aio server in your firewall. that also works. this however break the split dns scenario |
Beta Was this translation helpful? Give feedback.
-
|
the main issue as far as i can tell is that the reverse proxy needs to forward udp traffic; nginx is capable of from a certain version but i am unsure how the configuration would look like |
Beta Was this translation helpful? Give feedback.
You can manually overwrite the stun and turn server in the talk admin settings. E.g. adding a second subdomain and pointing that via cname at the public ip without overwriting it locally should probably make it work.