Nextcloud with Coturn and Nginx Reverse Proxy

[AlbiRadtke]

My configuration is pretty similar to the problem here #702. Unfortunately, the solution does not work for me for some inexplicable reason

I have Nginx as a reverse proxy on web server A, the Coturn server on web server B
Via stream I also manage the forwarding to the coturn server, so that Nextcloud confirms the connection. But no telephony or video telephony traffic arrives at the coturn server.

Config Nginx:

stream {
        server {
                listen 5720 ssl;

                ssl_certificate             /etc/letsencrypt/live/turn.url/fullchain.pem;
                ssl_certificate_key         /etc/letsencrypt/live/turn.ulr/privkey.pem;
                ssl_dhparam                 /etc/letsencrypt/ssl-dhparams.pem;

                ssl_protocols               TLSv1.2 TLSv1.3;
                ssl_prefer_server_ciphers   on;

                ssl_session_timeout         4h;
                ssl_session_tickets         on;

                proxy_ssl                   off;
                proxy_pass                  192.168.xxx.xxx:3478;
        }
}

Config turnserver.conf

realm=turn.url
server-name=turnserver
fingerprint
total-quota=100
bps-capacity=0
stale-nonce=600
no-multicast-peers
listening-ip=0.0.0.0
external-ip=192.168.xxx.xxx
syslog
verbose
use-auth-secret
static-auth-secret=my_secret
cli-password=myclipw

# SSL certificates
cert=/etc/letsencrypt/live/turn.url/cert.pem
pkey=/etc/letsencrypt/live/turn.url/privkey.pem

# for TURN over TLS, which can bypass firewalls
#tls-listening-port=5720
listening-port=3478
min-port=39500
max-port=39700

Fritzbox ports to/from reverseproxy:
HTTP: 80
HTTPS: 443
HTTPS: 5720
(39500-39700 UDP) Tested, no success

Fritzbox ports to/from turnserver:
39500-39700 UDP Tested, no success

I hope one of you can help me?
Many thanks in advance! :)

[AlbiRadtke]

Does anyone has an idea? Thank you very much! :)

[AlbiRadtke]

@tyranron or @eakraly:
Do any of you have any ideas or know someone I can turn to?

Many thanks in advance! :)

[jonesmz]

have you asked nginx support? if the traffic doesn't reach the coturn process, then there's not much coturn devs can do to help out unless they're also nginx experts.

[eakraly]

Hi @AlbiRadtke
Using nginx in front of coturn adds a lot of complexity if not making it impossible (UDP for example)

As @jonesmz suggested you will need help from nginx experts - what you are missing is proxy (see --tcp-proxy-port option for turnserver). I think that can address your problem (though it works for TCP only)