Icecast - Apr 2019 - Bad or missing password on mount modification admin request

Hi,

I am currently running Icecast 2.4.4 on Debian stretch and am using the info
from the status-json.xsl to display some stats on my radio webpage. This works
well.

On the same website, I have also managed to display listener stats. I looks like
this https://systrum.net/listeners.png
 
To get this data, my developer created a php script containing the icecast admin
credentials so that I can use the listeners’ IP and agent info to display their
location and duration the are connected for. It works as it should, but I do see
occasional messages in the icecast error log like the one below.

INFO admin/admin_handle_request Bad or missing password on mount modification
admin request (command: listclients.xsl)
EROR connection/_handle_connection Wrong request type from client

Icecast doesn’t seem to be affected by this but I would like a second opinion or
any pointers on the best action to take to rectify this issue. Any help would be
appreciated.

D

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20190423/70823823/attachment.html>

Good afternoon,

On Tue, 2019-04-23 at 22:45 +1000, Damian wrote:
> Hi,
> 
> I am currently running Icecast 2.4.4 on Debian stretch and am using
> the info from the status-json.xsl to display some stats on my radio
> webpage. This works well. 
> 
> On the same website, I have also managed to display listener stats. I
> looks like this https://systrum.net/listeners.png
>  
> To get this data, my developer created a php script containing the
> icecast admin credentials so that I can use the listeners’ IP and
> agent info to display their location and duration the are connected
> for. It works as it should, but I do see occasional messages in the
> icecast error log like the one below.
Ok.

> INFO admin/admin_handle_request Bad or missing password on mount
> modification admin request (command: listclients.xsl)
This (very likely) just means that your script does correct requests
with the first request being without credentials and the second one
with. This is perfectly normal and nothing to worry about.

> EROR connection/_handle_connection Wrong request type from client
This is a bit strange. It means that a client tries methods not
understood by Icecast. However that is likely OPTIONS requests by
browsers or maybe also by your script. Icecast 2.4.4 does not support
OPTIONS (Icecast 2.5.x does). So this is also expected.

Maybe you can have look at your access.log and see if there is any
client matching that time. The log should indicate which method the
client is using.

> Icecast doesn’t seem to be affected by this but I would like a second
> opinion or any pointers on the best action to take to rectify this
> issue. Any help would be appreciated.

As said above it is likely not an issue but what is actually to expect.
So no need to worry about it. :)

With best regards,


-- 
Philipp Schafft (CEO/Geschäftsführer) 
Telephon: +49.3535 490 17 92

Löwenfelsen UG (haftungsbeschränkt)     Registration number:
Bickinger Straße 21                     HRB 12308 CB
04916 Herzberg (Elster)                 VATIN/USt-ID:
Germany                                 DE305133015
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20190423/355a53b2/attachment.sig>