Sorry to hear you’re facing problems
In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:
Or for longer, use three backticks above and below the code snippet:
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can
Some useful links to gather information about your Nextcloud Talk installation:
Information about Signaling server:
Information about TURN server:
Information about STUN server:
Nextcloud version (eg, 24.0.1):
Talk Server version (eg, 14.0.2):
Custom Signaling server configured:
Custom TURN server configured:
Custom STUN server configured:
In case the web version of Nextcloud Talk is involved:
Operating system (eg, Windows/Ubuntu/…):
Browser name and version (eg, Chrome v101):
Edge Version 113.0.1774.50 (Official build) (64-bit)
In case mobile Nextcloud Talk apps are involved:
Talk iOS version (eg, 14.0.2):
Talk Android version (eg, 14.0.2):
The issue you are facing:
So I have Nextcloud, Nextcloud Talk & coturn all running on the same Windows 10 Hyper-V VM (running Ubuntu 20.04.6 LTS) in my home network. My home network is simple - one single subnet (192.168.1.0/24) with the Nextcloud/coturn server coexisting with the Nextcloud Talk clients. This config is working to the point where I can see coturn being used successfully to facilitate Internet/Intranet communication. That is to say a client on the internet used Nextcloud/coturn to call a client on my lan. The problem is the device on my Intranet is somehow finding the internal network IP address of my coturn server and communicating directly with it (when establishing a call with an outside caller). I don’t know how this is happening, but it prevents me from properly securing my coturn server using denied-peer-ip for my local lan addresses. Within the Nextcloud Talk admin settings I have configured it to use the externally valid DNS name for my Nextcloud & coturn install. This seems to happen with both the Android and Web (via Edge) versions of Nextcloud Talk.
Is this the first time you’ve seen this error? (Y/N):
Steps to replicate it:
- Install Nextcloud on Ubuntu on single subnet home network. Install coturn on same server (although I doubt it matters).
- Initiate a call with one person on the Internet and one person on the same LAN as the Nextcloud/coturn server.
The output of your Nextcloud log in Admin > Logging or errors in nextcloud.log in /var/www/:
There are no errors - the call is successful using the local lan IP address of the coturn server that the lan client shouldn't know or use.
The output of your Apache/nginx/system log in