Nextcloud Talk Call Fails — Complete Guide

In this tutorial, you'll learn about Nextcloud Talk Call Fails. We cover key concepts, practical examples, and best practices.

Hook

You start a Nextcloud Talk call with a colleague. They accept, but you see "Connecting..." and then "Call failed." No audio, no video. Your internet is fine, your microphone works in other apps, but Talk refuses to connect.

The Wrong Way

Disabling the STUN and TURN server settings in Talk's admin config makes the app rely entirely on peer-to-peer connections, which fail if both users are behind NAT.

# BAD: Removing STUN/TURN config
sudo -u www-data php occ config:app:delete spreed stun_servers
sudo -u www-data php occ config:app:delete spreed turn_servers

Call fails: "Could not establish connection"
STUN/TURN servers removed — no relay available

Without a TURN server, peer-to-peer NAT traversal fails, and calls drop.

The Right Way

Configure a STUN server (for NAT detection) and a TURN server (for media relay).

# 1. Add a public STUN server (Google's is free)
sudo -u www-data php occ talk:stun:add stun.nextcloud.com:443

# 2. Set up a TURN server (coturn package)
sudo apt install coturn

# 3. Configure coturn
sudo nano /etc/turnserver.conf

listening-port=3478
fingerprint
lt-cred-mech
user=talkuser:password
realm=yourdomain.com
total-quota=100

# 4. Add TURN server to Nextcloud
sudo -u www-data php occ talk:turn:add udp:yourdomain.com:3478 --secret=password --protocols=udp,tcp

# 5. Test the call
# Open Talk in two browser tabs on different networks

Call connected — audio working, video working
TURN relay active for NAT traversal

Prevention

• Configure a TURN server before rolling out Talk to your team.
• Use a domain with a valid SSL certificate for TURN (TLS on port 443).
• Monitor TURN usage with coturn logs.
• Set Allowed server urls for STUN and TURN servers to your domain in Talk settings.
• Test calls between different networks (not just the same LAN).

Advanced Troubleshooting

Check the Logs

Most TOOL errors are logged to stdout or a dedicated log file. Check your logs first:

# Check system logs
journalctl -u tool --since "1 hour ago"

# Or check the application log
tail -50 ~/.tool/logs/error.log

Test with a Minimal Example

Create the simplest possible tool configuration to verify the base setup works:

tool --version
tool --help

If the minimal test passes, add configuration options one at a time until you find the breaking change.

Common Configuration Mistakes

• Using the wrong file path or URL in configuration
• Forgetting to restart TOOL after changing config files
• Mixing tabs and spaces in YAML configuration files
• Setting incorrect permissions on configuration directories

When to Reinstall

If none of the above resolves the issue, consider a clean reinstall:

# Backup your configuration
cp -r ~/.tool ~/.tool.bak

# Remove and reinstall
# Follow the official TOOL installation guide

This ensures you start from a known good state and can isolate the issue.

Common Mistakes with talk call

1. Mixing let bindings with <- bindings in do notation, producing type errors
2. Overlapping type class instances that cause GHC to reject the program with ambiguous dispatch errors
3. Non-exhaustive pattern matches that compile with warnings then crash at runtime

These mistakes appear frequently in real-world NEXTCLOUD code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

DodaTech — take your calls, no dropouts.