coturn crash on ubuntu, help me.

[hakicode]

ubuntu server 18.04.x
coturn is already the newest version (4.5.0.7-1ubuntu2.18.04.3)

ERROR: apport (pid 3768) Tue Apr 6 08:41:27 2021: called for pid 2433, signal 11, core limit 0, dump mode 2
ERROR: apport (pid 3768) Tue Apr 6 08:41:27 2021: not creating core for pid with dump mode of 2
ERROR: apport (pid 3768) Tue Apr 6 08:41:27 2021: executable: /usr/bin/turnserver (command line "/usr/bin/turnserver -c /etc/turnserver.co$
ERROR: apport (pid 3768) Tue Apr 6 08:41:27 2021: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 3768) Tue Apr 6 08:41:27 2021: apport: report /var/crash/_usr_bin_turnserver.0.crash already exists and unseen, doing n$

[hakicode]

coturn automatically turns off after half a day, I check there is a log at /var/log/coturn.log
This has been happening frequently recently, and I have to restart it almost every day.

Can someone tell me what's going on and what should I do to fix it.

[misi]

Try to upgrade to newer ubuntu server version with the latest coturn package and if it will not fix the issue send a more detailed debug back trace from the core file..

[MeinhartEsrohr]

worked for several months without problems, now I restart the server every night at 3 o'clock and still the service fails around noon ( the required ports are then no longer open : netstat -tulpn
)
yesterday i updated my Server:
Apt-get update
apt-get dist-upgrade

but the same problem today

[misi]

@MeinhartEsrohr wihich version do you run?

[misi]

Please dist upgrade to ubuntu 20.04 LTS or use 4.5.2 backported package..

[luebke-dev]

we had the same problem on ubuntu 18 and upgrading fixed it.

[MeinhartEsrohr]

Hello Sebastian, upgrading to 20.04 LTS fixed it ?

[luebke-dev]

Yes we upgraded to 20.04.Runs flawless now

[MeinhartEsrohr]

Great, then I will also upgrade, I have never done it this way:
New release '20.04.2 LTS' available.
Run 'do-release-upgrade' to upgrade to it.

Hope everything goes through, thanks for your answer

[MeinhartEsrohr]

Hello, I just can not get it to work with Ubuntu version 20.04.2 LTS , the 443 port just does not come up, I have tried everything written in the forum, it just will not work, I have changed any config and also adjusted all permissions. How can it be that there are such massive problems with a new server version ?

how can I install the 4.5.2 backported package on my current server (which actually works) ?

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic

apt list coturn
Listing... Done
coturn/bionic-updates,bionic-security,now 4.5.0.7-1ubuntu2.18.04.3 amd64 [installed]
N: There is 1 additional version. Please use the '-a' switch to see it

[luebke-dev]

did you check the permissions of the SSL certificate? Am 03.05.2021 23:53 schrieb MeinhartEsrohr ***@***.***>: Hello, I just can not get it to work with Ubuntu version 20.04.2 LTS , the 443 port just does not come up, I have tried everything written in the forum, it just will not work, I have changed any config and also adjusted all permissions. How can it be that there are such massive problems with a new server version ? how can I install the 4.5.2 backported package on my current server (which actually works) ? —You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe.

[MeinhartEsrohr]

Hey sebastian, yes sure 👍
this is my current working config (NAT)under 18.02:

listening-port=3478

tls-listening-port=443

external-ip=195.165.215.100/10.10.10.13

fingerprint

colt-cred-mech

use-auth-secret
static-auth-secret=12345678abc

realm=turn.gh-immo.de

cert=/home/matrix/turn_gh-immo_de_crt.pem

pkey=/home/matrix/turn_gh-immo_de.pem

cipher-list="ECDH+AESGCM:ECDH+CHACHA20:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:RSA+AESGCM:RSA+AES:!aNULL:!MD5:!DSS"

dh2066

log-file=/var/log/coturn.log

simple-log

no-tlsv1
no-tlsv1_1

---

i tried everything from this post:
#421
nothing worked

---

at the end i had this config under 20.04 (not worked):

listening-port=3478

tls-listening-port=443

external-ip=195.165.215.100/10.10.10.13

min-port=32769
max-port=65535
verbose
fingerprint
lt-cred-mech
use-auth-secret
static-auth-secret=12345678abc
realm=turn.gh-immo.de

cert=/home/matrix/turn_gh-immo_de_crt.pem
pkey=/home/matrix/turn_gh-immo_de.pem

cipher-list="ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384"
dh-file=/etc/turnserver/dhp.pem
keep-address-family
no-cli
no-tlsv1
no-tlsv1_1

no-loopback-peers
no-multicast-peers

---

Permission SSL certificate
chmod 644 /home/matrix/turn_gh-immo_de_crt.pem
chmod 644 /home/matrix/turn_gh-immo_de.pem

[misi]

@MeinhartEsrohr the no-tls caused the issue and it has been resolved in the latest master.