[Icecast] Send admin kill request to server

Tue Feb 14 23:51:49 UTC 2023

Good afternoon,

On Tue, 2023-02-14 at 19:24 +0100, HGAlt wrote:
> Good afternoon Philipp and everyone,
> 
> I am a little bit confused!
> 
> http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21
> 
> This is an example of the Icecast documentation for kill a client.
> And this is a HTTP GET, which is send to the Icecast server.
> You also wrote, that there are no user and pass for an API.

I wrote that there are no such form parameters.

> What I have to know, what does the Icecast server expect?
> If there is no user and pass, how the server knows, that is a valid
> request.

There are credentials as per standard HTTP auth. See e.g. here:
https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#HTTP_authentication

> I also figured out, that I got a network error, if I address the
> server with his full URL, like  https://www.server.xy, when I use
> localhost or the local IP like 10.0.0.x, I got a normal error without
> any addition description.

That sounds more like a problem with your firewall and/or port
forwardings (if any).

> So I believe, that I first have to understand, what I have to send to
> the server and how the Icecast server understand, that it has to
> execute this API!
> As long it is not clear to me, I don't know what to do.
> The software is written by myself and therefore I can control it.

Please see above.

With best regards,

PS: It would be very kind of you if you would avoid TOFU (
https://en.wikipedia.org/wiki/Top-posting). It makes mails much harder
to read.

> -----Ursprüngliche Nachricht-----
> Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Philipp
> Schafft
> Gesendet: Dienstag, 14. Februar 2023 17:25
> An: Icecast streaming server user discussions
> Betreff: Re: [Icecast] Send admin kill request to server
> 
> Good morning,
> 
> On Tue, 2023-02-14 at 12:47 +0100, HGAlt wrote:
> > Good morning Philipp,
> > 
> > in the log files I couldn't find anything, but the level is only
> > set
> > to 3. I set it now to 4, but a restart is require first.
> 
> the access log should always have an entry. If it doesn't something
> is wrong.
> 
> In the good case the first request is rejected (with a 401), and then
> the client will do all other requests authed (mostly 2xx status
> codes).
> 
> 
> > How can I set the credentials?
> 
> That depends on the client you use. Without knowing that nobody can
> answer that. It should be in the documentation of the software you
> use to make the request.
> 
> 
> > If I use <bind-address> is the server than only listen to this IP?
> > Can I have 2 bind-addresses for one port?
> 
> This has nothing to do with the listen sockets.
> 
> 
> > Where can I find additional information about setting the
> > credentials?
> 
> In the documentation of the software you use to make the API request.
> 
> 
> > Can I provide you my configuration directly?
> 
> I don't think this is in any way related to Icecast's config at this
> point.
> 

> 
> > -----Ursprüngliche Nachricht-----
> > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von
> > Philipp
> > Schafft
> > Gesendet: Dienstag, 14. Februar 2023 00:15
> > An: Icecast streaming server user discussions
> > Betreff: Re: [Icecast] Send admin kill request to server
> > 
> > Good afternoon,
> > 
> > On Mon, 2023-02-13 at 19:29 +0100, HGAlt wrote:
> > > Hi Philipp,
> > > 
> > > I have tested it. But I still get the message back
> > > “Authentication
> > > Required".
> > > As I mentioned before, send this request from the same server,
> > > where
> > > Icecast is running.
> > > But the audio is provided from another server.
> > > Could be that a problem?
> > 
> > No, not really. This strongly sounds like the credentials are in
> > fact
> > not provided. both access.log and error.log might have details.
> > Also
> > you could have a look at the actual traffic flow.
> > 
> > At this point I don't think there is much to add without knowing
> > your
> > config and the code you use to access the API. I still strongly
> > guess
> > that you just don't provide the credentials in a way they are
> > actually
> > used. Which is most likely a problem with your code, not the API or
> > Icecast.
> > 
> > With best regards,
> > 
> > 
> > 
> > > -----Ursprüngliche Nachricht-----
> > > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von
> > > Philipp Schafft
> > > Gesendet: Montag, 13. Februar 2023 15:12
> > > An: Icecast streaming server user discussions
> > > Betreff: Re: [Icecast] Send admin kill request to server
> > > 
> > > [...]
> > > I just confirmed here with current devel build, the following
> > > works
> > > fine for me:
> > > 
> > > wget -SO /dev/null --user=admin --password=hackme --post-
> > > data='mount=/example1.ogg&id=44'
> > > http://localhost:8000/admin/killclient
> 

-- 
Philipp Schafft (CEO/Geschäftsführer) 
Telephone:           +49.3535 490 17 92
Website:             https://www.loewenfelsen.net/
Follow us:           https://www.linkedin.com/company/loewenfelsen/
Geschäftsführer/CEO: Philipp Schafft

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: 228 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20230214/65f396c1/attachment.sig>