Почему TURN-сервер не принимает соединения?

Question

[nihi1ist]

Имеется TURN-сервер на CentOS 7, решили его обновить до РЕД ОС 8. Версия Coturn одна и та же. Но на РЕД ОС TURN-сервер не хочет принимать соединения с тем же конфигом.

Пример конфига

external-ip={external-ip}/{local-ip}
verbose
fingerprint
use-auth-secret
static-auth-secret={secret_key}
realm=turn
log-file=/var/log/coturn/turnserver.log
simple-log
no-stun
web-admin
web-admin-ip={local-ip}
web-admin-port=9088

Пробовал искать по ключевым словам из логов, решений не нашёл.

Логи при попытке подключения

99: : session 000000000000000001: realm user <1726770662:0fdba89a-86c4-4332-83ad-306f257a9192>: incoming packet BINDING processed, success
100: : session 098000000000000001: realm user <1726770662:0fdba89a-86c4-4332-83ad-306f257a9192>: incoming packet BINDING processed, success
101: : session 039000000000000001: realm user <>: incoming packet BINDING processed, success
101: : session 039000000000000001: realm user <>: incoming packet message processed, error 401: Unauthorized
109: : session 000000000000000001: realm user <1726770662:0fdba89a-86c4-4332-83ad-306f257a9192>: incoming packet BINDING processed, success
109: : session 053000000000000001: usage: realm=, username=<1726770599:c373b101-c092-4c18-94fd-39ecccf82542>, rp=10, rb=880, sp=4, sb=416
109: : session 053000000000000001: peer usage: realm=, username=<1726770599:c373b101-c092-4c18-94fd-39ecccf82542>, rp=0, rb=0, sp=0, sb=0
109: : session 053000000000000001: closed (2nd stage), user <1726770599:c373b101-c092-4c18-94fd-39ecccf82542> realm origin <>, local 10.220.24.11:3478, remote 95.82.126.15:35867, reason: allocation watchdog determined stale session state
110: : session 098000000000000001: realm user <1726770662:0fdba89a-86c4-4332-83ad-306f257a9192>: incoming packet BINDING processed, success
111: : session 039000000000000001: realm user <1726770662:0fdba89a-86c4-4332-83ad-306f257a9192>: incoming packet BINDING processed, success
113: : session 001000000000000002: realm user <>: incoming packet BINDING processed, success
113: : session 001000000000000002: realm user <>: incoming packet message processed, error 401: Unauthorized
119: : session 000000000000000001: realm user <1726770662:0fdba89a-86c4-4332-83ad-306f257a9192>: incoming packet BINDING processed, success
120: : session 112000000000000001: usage: realm=, username=<1726770599:c373b101-c092-4c18-94fd-39ecccf82542>, rp=9, rb=860, sp=3, sb=312
120: : session 112000000000000001: peer usage: realm=, username=<1726770599:c373b101-c092-4c18-94fd-39ecccf82542>, rp=0, rb=0, sp=0, sb=0
120: : session 112000000000000001: closed (2nd stage), user <1726770599:c373b101-c092-4c18-94fd-39ecccf82542> realm origin <>, local 10.220.24.11:3478, remote 95.82.126.15:32058, reason: allocation watchdog determined stale session state
120: : session 098000000000000001: realm user <1726770662:0fdba89a-86c4-4332-83ad-306f257a9192>: incoming packet BINDING processed, success
121: : session 039000000000000001: realm user <1726770662:0fdba89a-86c4-4332-83ad-306f257a9192>: incoming packet BINDING processed, success
123: : session 001000000000000002: realm user <1726770662:0fdba89a-86c4-4332-83ad-306f257a9192>: incoming packet BINDING processed, success
124: : session 097000000000000001: realm user <>: incoming packet BINDING processed, success
124: : session 097000000000000001: realm user <>: incoming packet message processed, error 401: Unauthorized
129: : session 000000000000000001: realm user <1726770662:0fdba89a-86c4-4332-83ad-306f257a9192>: incoming packet BINDING processed, success
130: : session 098000000000000001: realm user <1726770662:0fdba89a-86c4-4332-83ad-306f257a9192>: incoming packet BINDING processed, success
131: : session 039000000000000001: realm user <1726770662:0fdba89a-86c4-4332-83ad-306f257a9192>: incoming packet BINDING processed, success
133: : session 001000000000000002: realm user <1726770662:0fdba89a-86c4-4332-83ad-306f257a9192>: incoming packet BINDING processed, success
134: : session 097000000000000001: realm user <1726770662:0fdba89a-86c4-4332-83ad-306f257a9192>: incoming packet BINDING processed, success
138: : session 000000000000000001: usage: realm=, username=<1726770662:0fdba89a-86c4-4332-83ad-306f257a9192>, rp=13, rb=940, sp=7, sb=728
138: : session 000000000000000001: peer usage: realm=, username=<1726770662:0fdba89a-86c4-4332-83ad-306f257a9192>, rp=0, rb=0, sp=0, sb=0
138: : session 000000000000000001: closed (2nd stage), user <1726770662:0fdba89a-86c4-4332-83ad-306f257a9192> realm origin <>, local {local-ip}:3478, remote {client-ip}:29241, reason: allocation watchdog determined stale session state

Подскажите, как решить?