You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by Ali Alhaidary <al...@the5stars.org> on 2020/10/18 16:52:04 UTC
incoming packet message processed, error 401: Unauthorized
as the above message is so much frequent in turn log, could the bellow
be the remedy:
https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/issues/1226
Re: incoming packet message processed, error 401: Unauthorized
Posted by Ali Alhaidary <al...@the5stars.org>.
I had the same case, however, after some tweeks and mainly replacing
realm with the static IP and removing user:password parameter, I can
hardly see 401 in turn log and the request gets authenticated directly,
but I can still find just few in hundreds of lines of turn log.
On 10/20/20 5:00 AM, Maxim Solodovnik wrote:
> Correction: just have double checked and there are some 401
>
> This might be the part of SDP
> Initial response is 401, then goes authentication part, and then
> communication
>
> this can be checked with Wireshark
>
> On Tue, 20 Oct 2020 at 08:54, Maxim Solodovnik <solomax666@gmail.com
> <ma...@gmail.com>> wrote:
>
>
>
> On Tue, 20 Oct 2020 at 08:39, seba.wagner@gmail.com
> <ma...@gmail.com> <seba.wagner@gmail.com
> <ma...@gmail.com>> wrote:
>
> I had the same question recently.
>
> I can see the same behaviour in Turn Logs. The first request
> fails with 401, and subsequent requests get handled and
> authenticated.
>
> The connection works, on turn side as well as the media Server
> connection works fine. But every connection attempt logs one
> 401. Even though successfully in the end.
>
> I don't think credentials are wrong. But maybe there is
> something with using the authSecret and the user:password at
> the same time, the first attempt fails with 401.
>
>
> Logs on demo have no 401 errors ...
>
>
> Thanks
> Seb
>
> Sebastian Wagner
> Director Arrakeen Solutions
> http://arrakeen-solutions.co.nz/
> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url><https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>
>
> On Tue, 20 Oct 2020 at 03:51, Ali Alhaidary
> <ali.alhaidary@the5stars.org
> <ma...@the5stars.org>> wrote:
>
> Thank you, I was looking into
> https://mail-archives.apache.org/mod_mbox/openmeetings-user/202010.mbox/browser
> that did not have search :-)
>
> I will try them and return to you.
>
>
> On 10/19/20 5:13 PM, Maxim Solodovnik wrote:
>> I would use search in ML archives directly:
>> https://openmeetings.markmail.org/
>> this I was able to find this
>> https://markmail.org/message/d6ifllraemj6dz6v post :))
>>
>> On Mon, 19 Oct 2020 at 17:23, Ali Alhaidary
>> <ali.alhaidary@the5stars.org
>> <ma...@the5stars.org>> wrote:
>>
>> when googling it, ideas were conflicting, some say
>> that this is a legitimate error, even in the ML, the
>> issue was raided many times, but could not find a
>> conclusive solution. Would you please send me your
>> .conf file.
>>
>> On 10/19/20 11:04 AM, Maxim Solodovnik wrote:
>>> 401 means your TURN parameters most probably are
>>> incorrect
>>> were you able to find and check my config? (should
>>> be searchable at ML archives)
>>>
>>> On Sun, 18 Oct 2020 at 23:52, Ali Alhaidary
>>> <ali.alhaidary@the5stars.org
>>> <ma...@the5stars.org>> wrote:
>>>
>>> as the above message is so much frequent in turn
>>> log, could the bellow
>>> be the remedy:
>>>
>>> https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/issues/1226
>>>
>>>
>>>
>>> --
>>> Best regards,
>>> Maxim
>>
>>
>>
>> --
>> Best regards,
>> Maxim
>
>
>
> --
> Best regards,
> Maxim
>
>
>
> --
> Best regards,
> Maxim
Re: incoming packet message processed, error 401: Unauthorized
Posted by Maxim Solodovnik <so...@gmail.com>.
Correction: just have double checked and there are some 401
This might be the part of SDP
Initial response is 401, then goes authentication part, and then
communication
this can be checked with Wireshark
On Tue, 20 Oct 2020 at 08:54, Maxim Solodovnik <so...@gmail.com> wrote:
>
>
> On Tue, 20 Oct 2020 at 08:39, seba.wagner@gmail.com <se...@gmail.com>
> wrote:
>
>> I had the same question recently.
>>
>> I can see the same behaviour in Turn Logs. The first request fails with
>> 401, and subsequent requests get handled and authenticated.
>>
>> The connection works, on turn side as well as the media Server connection
>> works fine. But every connection attempt logs one 401. Even though
>> successfully in the end.
>>
>> I don't think credentials are wrong. But maybe there is something with
>> using the authSecret and the user:password at the same time, the first
>> attempt fails with 401.
>>
>
> Logs on demo have no 401 errors ...
>
>
>>
>> Thanks
>> Seb
>>
>> Sebastian Wagner
>> Director Arrakeen Solutions
>> http://arrakeen-solutions.co.nz/
>>
>> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
>> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>>
>>
>> On Tue, 20 Oct 2020 at 03:51, Ali Alhaidary <al...@the5stars.org>
>> wrote:
>>
>>> Thank you, I was looking into
>>> https://mail-archives.apache.org/mod_mbox/openmeetings-user/202010.mbox/browser
>>> that did not have search :-)
>>>
>>> I will try them and return to you.
>>>
>>>
>>> On 10/19/20 5:13 PM, Maxim Solodovnik wrote:
>>>
>>> I would use search in ML archives directly:
>>> https://openmeetings.markmail.org/
>>> this I was able to find this
>>> https://markmail.org/message/d6ifllraemj6dz6v post :))
>>>
>>> On Mon, 19 Oct 2020 at 17:23, Ali Alhaidary <al...@the5stars.org>
>>> wrote:
>>>
>>>> when googling it, ideas were conflicting, some say that this is a
>>>> legitimate error, even in the ML, the issue was raided many times, but
>>>> could not find a conclusive solution. Would you please send me your .conf
>>>> file.
>>>> On 10/19/20 11:04 AM, Maxim Solodovnik wrote:
>>>>
>>>> 401 means your TURN parameters most probably are incorrect
>>>> were you able to find and check my config? (should be searchable at ML
>>>> archives)
>>>>
>>>> On Sun, 18 Oct 2020 at 23:52, Ali Alhaidary <
>>>> ali.alhaidary@the5stars.org> wrote:
>>>>
>>>>> as the above message is so much frequent in turn log, could the bellow
>>>>> be the remedy:
>>>>>
>>>>> https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/issues/1226
>>>>>
>>>>>
>>>>
>>>> --
>>>> Best regards,
>>>> Maxim
>>>>
>>>>
>>>
>>> --
>>> Best regards,
>>> Maxim
>>>
>>>
>
> --
> Best regards,
> Maxim
>
--
Best regards,
Maxim
Re: incoming packet message processed, error 401: Unauthorized
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
Which logs?
we especially mean CoTurn Server log.
It looks like this:
1528379: session 000000000000001335: realm <mydomain.xyz> user <>: incoming
packet message processed, error 401: Unauthorized
Thanks
Seb
Sebastian Wagner
Director Arrakeen Solutions
http://arrakeen-solutions.co.nz/
<https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
<https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
On Tue, 20 Oct 2020 at 14:54, Maxim Solodovnik <so...@gmail.com> wrote:
>
>
> On Tue, 20 Oct 2020 at 08:39, seba.wagner@gmail.com <se...@gmail.com>
> wrote:
>
>> I had the same question recently.
>>
>> I can see the same behaviour in Turn Logs. The first request fails with
>> 401, and subsequent requests get handled and authenticated.
>>
>> The connection works, on turn side as well as the media Server connection
>> works fine. But every connection attempt logs one 401. Even though
>> successfully in the end.
>>
>> I don't think credentials are wrong. But maybe there is something with
>> using the authSecret and the user:password at the same time, the first
>> attempt fails with 401.
>>
>
> Logs on demo have no 401 errors ...
>
>
>>
>> Thanks
>> Seb
>>
>> Sebastian Wagner
>> Director Arrakeen Solutions
>> http://arrakeen-solutions.co.nz/
>>
>> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
>> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>>
>>
>> On Tue, 20 Oct 2020 at 03:51, Ali Alhaidary <al...@the5stars.org>
>> wrote:
>>
>>> Thank you, I was looking into
>>> https://mail-archives.apache.org/mod_mbox/openmeetings-user/202010.mbox/browser
>>> that did not have search :-)
>>>
>>> I will try them and return to you.
>>>
>>>
>>> On 10/19/20 5:13 PM, Maxim Solodovnik wrote:
>>>
>>> I would use search in ML archives directly:
>>> https://openmeetings.markmail.org/
>>> this I was able to find this
>>> https://markmail.org/message/d6ifllraemj6dz6v post :))
>>>
>>> On Mon, 19 Oct 2020 at 17:23, Ali Alhaidary <al...@the5stars.org>
>>> wrote:
>>>
>>>> when googling it, ideas were conflicting, some say that this is a
>>>> legitimate error, even in the ML, the issue was raided many times, but
>>>> could not find a conclusive solution. Would you please send me your .conf
>>>> file.
>>>> On 10/19/20 11:04 AM, Maxim Solodovnik wrote:
>>>>
>>>> 401 means your TURN parameters most probably are incorrect
>>>> were you able to find and check my config? (should be searchable at ML
>>>> archives)
>>>>
>>>> On Sun, 18 Oct 2020 at 23:52, Ali Alhaidary <
>>>> ali.alhaidary@the5stars.org> wrote:
>>>>
>>>>> as the above message is so much frequent in turn log, could the bellow
>>>>> be the remedy:
>>>>>
>>>>> https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/issues/1226
>>>>>
>>>>>
>>>>
>>>> --
>>>> Best regards,
>>>> Maxim
>>>>
>>>>
>>>
>>> --
>>> Best regards,
>>> Maxim
>>>
>>>
>
> --
> Best regards,
> Maxim
>
Re: incoming packet message processed, error 401: Unauthorized
Posted by Maxim Solodovnik <so...@gmail.com>.
On Tue, 20 Oct 2020 at 08:39, seba.wagner@gmail.com <se...@gmail.com>
wrote:
> I had the same question recently.
>
> I can see the same behaviour in Turn Logs. The first request fails with
> 401, and subsequent requests get handled and authenticated.
>
> The connection works, on turn side as well as the media Server connection
> works fine. But every connection attempt logs one 401. Even though
> successfully in the end.
>
> I don't think credentials are wrong. But maybe there is something with
> using the authSecret and the user:password at the same time, the first
> attempt fails with 401.
>
Logs on demo have no 401 errors ...
>
> Thanks
> Seb
>
> Sebastian Wagner
> Director Arrakeen Solutions
> http://arrakeen-solutions.co.nz/
>
> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>
>
> On Tue, 20 Oct 2020 at 03:51, Ali Alhaidary <al...@the5stars.org>
> wrote:
>
>> Thank you, I was looking into
>> https://mail-archives.apache.org/mod_mbox/openmeetings-user/202010.mbox/browser
>> that did not have search :-)
>>
>> I will try them and return to you.
>>
>>
>> On 10/19/20 5:13 PM, Maxim Solodovnik wrote:
>>
>> I would use search in ML archives directly:
>> https://openmeetings.markmail.org/
>> this I was able to find this
>> https://markmail.org/message/d6ifllraemj6dz6v post :))
>>
>> On Mon, 19 Oct 2020 at 17:23, Ali Alhaidary <al...@the5stars.org>
>> wrote:
>>
>>> when googling it, ideas were conflicting, some say that this is a
>>> legitimate error, even in the ML, the issue was raided many times, but
>>> could not find a conclusive solution. Would you please send me your .conf
>>> file.
>>> On 10/19/20 11:04 AM, Maxim Solodovnik wrote:
>>>
>>> 401 means your TURN parameters most probably are incorrect
>>> were you able to find and check my config? (should be searchable at ML
>>> archives)
>>>
>>> On Sun, 18 Oct 2020 at 23:52, Ali Alhaidary <al...@the5stars.org>
>>> wrote:
>>>
>>>> as the above message is so much frequent in turn log, could the bellow
>>>> be the remedy:
>>>>
>>>> https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/issues/1226
>>>>
>>>>
>>>
>>> --
>>> Best regards,
>>> Maxim
>>>
>>>
>>
>> --
>> Best regards,
>> Maxim
>>
>>
--
Best regards,
Maxim
Re: incoming packet message processed, error 401: Unauthorized
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
I had the same question recently.
I can see the same behaviour in Turn Logs. The first request fails with
401, and subsequent requests get handled and authenticated.
The connection works, on turn side as well as the media Server connection
works fine. But every connection attempt logs one 401. Even though
successfully in the end.
I don't think credentials are wrong. But maybe there is something with
using the authSecret and the user:password at the same time, the first
attempt fails with 401.
Thanks
Seb
Sebastian Wagner
Director Arrakeen Solutions
http://arrakeen-solutions.co.nz/
<https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
<https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
On Tue, 20 Oct 2020 at 03:51, Ali Alhaidary <al...@the5stars.org>
wrote:
> Thank you, I was looking into
> https://mail-archives.apache.org/mod_mbox/openmeetings-user/202010.mbox/browser
> that did not have search :-)
>
> I will try them and return to you.
>
>
> On 10/19/20 5:13 PM, Maxim Solodovnik wrote:
>
> I would use search in ML archives directly:
> https://openmeetings.markmail.org/
> this I was able to find this https://markmail.org/message/d6ifllraemj6dz6v
> post :))
>
> On Mon, 19 Oct 2020 at 17:23, Ali Alhaidary <al...@the5stars.org>
> wrote:
>
>> when googling it, ideas were conflicting, some say that this is a
>> legitimate error, even in the ML, the issue was raided many times, but
>> could not find a conclusive solution. Would you please send me your .conf
>> file.
>> On 10/19/20 11:04 AM, Maxim Solodovnik wrote:
>>
>> 401 means your TURN parameters most probably are incorrect
>> were you able to find and check my config? (should be searchable at ML
>> archives)
>>
>> On Sun, 18 Oct 2020 at 23:52, Ali Alhaidary <al...@the5stars.org>
>> wrote:
>>
>>> as the above message is so much frequent in turn log, could the bellow
>>> be the remedy:
>>>
>>> https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/issues/1226
>>>
>>>
>>
>> --
>> Best regards,
>> Maxim
>>
>>
>
> --
> Best regards,
> Maxim
>
>
Re: incoming packet message processed, error 401: Unauthorized
Posted by Ali Alhaidary <al...@the5stars.org>.
Thank you, I was looking into
https://mail-archives.apache.org/mod_mbox/openmeetings-user/202010.mbox/browser
that did not have search :-)
I will try them and return to you.
On 10/19/20 5:13 PM, Maxim Solodovnik wrote:
> I would use search in ML archives directly:
> https://openmeetings.markmail.org/
> this I was able to find this
> https://markmail.org/message/d6ifllraemj6dz6v post :))
>
> On Mon, 19 Oct 2020 at 17:23, Ali Alhaidary
> <ali.alhaidary@the5stars.org <ma...@the5stars.org>> wrote:
>
> when googling it, ideas were conflicting, some say that this is a
> legitimate error, even in the ML, the issue was raided many times,
> but could not find a conclusive solution. Would you please send me
> your .conf file.
>
> On 10/19/20 11:04 AM, Maxim Solodovnik wrote:
>> 401 means your TURN parameters most probably are incorrect
>> were you able to find and check my config? (should be searchable
>> at ML archives)
>>
>> On Sun, 18 Oct 2020 at 23:52, Ali Alhaidary
>> <ali.alhaidary@the5stars.org
>> <ma...@the5stars.org>> wrote:
>>
>> as the above message is so much frequent in turn log, could
>> the bellow
>> be the remedy:
>>
>> https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/issues/1226
>>
>>
>>
>> --
>> Best regards,
>> Maxim
>
>
>
> --
> Best regards,
> Maxim
Re: incoming packet message processed, error 401: Unauthorized
Posted by Maxim Solodovnik <so...@gmail.com>.
I would use search in ML archives directly:
https://openmeetings.markmail.org/
this I was able to find this https://markmail.org/message/d6ifllraemj6dz6v
post :))
On Mon, 19 Oct 2020 at 17:23, Ali Alhaidary <al...@the5stars.org>
wrote:
> when googling it, ideas were conflicting, some say that this is a
> legitimate error, even in the ML, the issue was raided many times, but
> could not find a conclusive solution. Would you please send me your .conf
> file.
> On 10/19/20 11:04 AM, Maxim Solodovnik wrote:
>
> 401 means your TURN parameters most probably are incorrect
> were you able to find and check my config? (should be searchable at ML
> archives)
>
> On Sun, 18 Oct 2020 at 23:52, Ali Alhaidary <al...@the5stars.org>
> wrote:
>
>> as the above message is so much frequent in turn log, could the bellow
>> be the remedy:
>>
>> https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/issues/1226
>>
>>
>
> --
> Best regards,
> Maxim
>
>
--
Best regards,
Maxim
Re: incoming packet message processed, error 401: Unauthorized
Posted by Ali Alhaidary <al...@the5stars.org>.
when googling it, ideas were conflicting, some say that this is a
legitimate error, even in the ML, the issue was raided many times, but
could not find a conclusive solution. Would you please send me your
.conf file.
On 10/19/20 11:04 AM, Maxim Solodovnik wrote:
> 401 means your TURN parameters most probably are incorrect
> were you able to find and check my config? (should be searchable at ML
> archives)
>
> On Sun, 18 Oct 2020 at 23:52, Ali Alhaidary
> <ali.alhaidary@the5stars.org <ma...@the5stars.org>> wrote:
>
> as the above message is so much frequent in turn log, could the
> bellow
> be the remedy:
>
> https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/issues/1226
>
>
>
> --
> Best regards,
> Maxim
Re: incoming packet message processed, error 401: Unauthorized
Posted by Maxim Solodovnik <so...@gmail.com>.
401 means your TURN parameters most probably are incorrect
were you able to find and check my config? (should be searchable at ML
archives)
On Sun, 18 Oct 2020 at 23:52, Ali Alhaidary <al...@the5stars.org>
wrote:
> as the above message is so much frequent in turn log, could the bellow
> be the remedy:
>
> https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/issues/1226
>
>
--
Best regards,
Maxim