Great it is resolved :)
I would recommend to generate password from time to time (for ex. with
`apg` utility )
On Sun, 3 Jan 2021 at 14:35, Robert Savickas wrote:
> Maxim,
>
> Just an update. It all works very well now. As always, thank you for your
> tips.
>
> Turns out that the long password i
Maxim,
Just an update. It all works very well now. As always, thank you for your
tips.
Turns out that the long password in file turnserver.conf for the variable
"static-auth-secret" had a trailing tab at the end of the password. That
tab was not visible with a naked eye. But when I scrolled to t
Maxim,
Merry Orthodox Christmas to you!
I think all my settings are as you describe. But I will check again.
I start all the servers as a superuser. May be that is the problem
(although I did this way previously, too)
Thank you.
Enjoy the holiday!
Robert
On Sat, Jan 2, 2021, 22:31 Maxim Sol
On Sun, 3 Jan 2021 at 10:03, Robert Savickas wrote:
> I also tried to put the line "user=nobody:a_new_password" in
> the /etc/turnserver.conf file, as per the OM 5.0.1 instructions. But
>
I don't have this line in my config
> that did not make a difference, either...
>
> Thank you.
>
> On Sat,
I also tried to put the line "user=nobody:a_new_password" in
the /etc/turnserver.conf file, as per the OM 5.0.1 instructions. But that
did not make a difference, either...
Thank you.
On Sat, Jan 2, 2021 at 6:18 PM Robert Savickas
wrote:
> Dear Friends,
>
> Up until now, I was running OM 5.0.0 a
Dear Friends,
Up until now, I was running OM 5.0.0 and it ran fine.
Today, I installed OM 5.1.0 on a new server. As usual, I followed Alvaro's
excellent guides to the letter.
And, now, I am experiencing a familiar Coturn problem. Specifically, when I
connect to the OM service from computers on t
