search for: killclient

...Icecast config: <client-timeout>30</client-timeout> Here is the output from the "List Clients" page of Icecast2 Admin *IP* *Seconds Connected* *User Agent* *Action* 68.7.238.55 406 WinampMPEG/5.62, Ultravox/2.1 Kick <http://www.airprogressive.org:8000/admin/killclient.xsl?mount=/stream&id=2690> 74.82.68.16 6 Mozilla/4.8 [en] (Windows NT 5.0; U) Kick <http://www.airprogressive.org:8000/admin/killclient.xsl?mount=/stream&id=2704> 74.82.68.16 4 Mozilla/4.8 [en] (Windows NT 5.0; U) Kick <http://www.airprogressive.org:8000/admin/killcl...

On Feb 14, 2023, at 13:24, HGAlt <hgalt at gmx.net> wrote: > I am a little bit confused! > > http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21 <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 a...

...von Fred Gleason Gesendet: Mittwoch, 15. Februar 2023 16:57 An: Icecast streaming server user discussions Betreff: Re: [Icecast] Send admin kill request to server On Feb 14, 2023, at 13:24, HGAlt <hgalt at gmx.net> wrote: I am a little bit confused! <http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21> 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. Wha...

...von Fred Gleason Gesendet: Mittwoch, 15. Februar 2023 16:57 An: Icecast streaming server user discussions Betreff: Re: [Icecast] Send admin kill request to server On Feb 14, 2023, at 13:24, HGAlt <hgalt at gmx.net> wrote: I am a little bit confused! <http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21> 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. Wha...

Hi, I have a strange problem, which I don't understand! I create a URL like: https:// .:8000/admin/killclient.xsl?user=admin&pass=password&mount=/mount.mpeg&id=12 3456 If I send this URL via a browser to the Icecast server, it works fine! But if I send the same URL via JQUERY AJAX, it failed, because "Authentication Required". But the user and the password is included. The brow...

...ebruar 2023 16:57 > An: Icecast streaming server user discussions > Betreff: Re: [Icecast] Send admin kill request to server > > On Feb 14, 2023, at 13:24, HGAlt <hgalt at gmx.net> wrote: > > > 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. > > > > What I have to know,...

...r 2023 16:57 > An: Icecast streaming server user discussions > Betreff: Re: [Icecast] Send admin kill request to server > > On Feb 14, 2023, at 13:24, HGAlt <hgalt at gmx.net> wrote: > > > 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. > > > > What I have to know...

...eaming server user discussions > > Betreff: Re: [Icecast] Send admin kill request to server > > > > On Feb 14, 2023, at 13:24, HGAlt <hgalt at gmx.net> wrote: > > > > > 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. >...

...t; Betreff: Re: [Icecast] Send admin kill request to server > > Good morning, > > On Mon, 2023-02-13 at 14:53 +0100, HGAlt wrote: > > Hi, > > > > I have a strange problem, which I don?t understand! > > I create a URL like: > > > > https://?:8000/admin/killclient.xsl?user=admin&pass=password&mount=/ > > mo > > unt.mpeg&id=123456 > > This doesn't look like a valid API endpoint and parameters. > > endpoints under /admin that end with ".xsl" are for users only, not > for machine made requests. Remove the &qu...

...streaming server user discussions > > Betreff: Re: [Icecast] Send admin kill request to server > > > > On Feb 14, 2023, at 13:24, HGAlt <hgalt at gmx.net> wrote: > > > > > I am a little bit confused! > > > > > > http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=2 > > > 1 > > > > > > 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. >...

...ieof debug1: channel 0: non-open channel 0: istate 8 != open channel 0: ostate 64 != open XIO: fatal IO error 32 (Broken pipe) on X server "localhost:11.0" after 0 requests (0 known processed) with 0 events remaining. The connection was probably broken by a server shutdown or KillClient. -- Hubertus A. Haniel Unix Engineering Deutsche Bank AG London

...k of what is needed to emit a remove event.) Revoking permissions is yet another concept. You can already do that perfectly fine with current Icecast2: part of the POSTed parameters in the URL Auth request is a parameter 'client'. That value can be used to kick the listener using an /admin/killclient*?mount=$MOUNT&id=$CLIENTID (since at least Icecast2 2.3.x) request at any time. This way you can remove a client the moment the permission is revoked with virtually no delay. > > Would a update for 2.5.x help you? > > This would definitely help, yes, and I would appreciate if yo...

On 05/13/2017 03:12 PM, Philipp Schafft wrote: > Basically the client structure would need to keep track of which sources > the client was attached to in form of a stack. This is important as > there can be fallbacks of fallbacks (and there are valid reasons to > build something like that). A pure 'original mount' thing may result in > unexpected behavior. That being even

I had been running a system on Centos 5.1 at INIT 3. I did the upgrade to Centos 5.2 with the aid of the powernowk8 patch. Previously I would VNC into the unit when I needed to do admin stuff with a GUI. Well I noticed that I was NOT getting GNOME via VNC since the upgrade (worked before just fine with 5.1). So I tried an INIT 5 from the command line (always worked before), but the system