Support intro
Sorry to hear youâre facing problems
help.nextcloud.com is for home/non-enterprise users. If youâre running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.
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:
example
Or for longer, use three backticks above and below the code snippet:
longer
example
here
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: /index.php/index.php/settings/admin/talk#signaling_server
Information about TURN server: /index.php/settings/admin/talk#turn_server
Information about STUN server: /index.php/settings/admin/talk#stun_server
Nextcloud version (eg, 24.0.1): 25.0.7
Talk Server version (eg, 14.0.2): 15.0.6
Custom Signaling server configured: no
Custom TURN server configured: yes/no
Custom STUN server configured: http://stun.nextcloud.com:443
In case the web version of Nextcloud Talk is involved:
Operating system (eg, Windows/Ubuntu/âŚ): Windows 10
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): not tested
Talk Android version (eg, 14.0.2): 16.0.1
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): yes
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 /var/log/____
:
PASTE HERE
Your browser log if relevant (javascript console log, network log, etc.):
PASTE HERE