similar to: admin console

2020-01-08 09:59, Marvin Scholz wrote: > >> On Mon, 2020-01-06 at 10:24 +0000, user wrote: > > > > I'm consider to put icecast behind reverse proxy. It is not so easy as I > > think before. Does anyone have experience with it? > > In general putting Icecast behind a reverse proxy is not the best idea as > some webservers are not really made out of the box

> On Thu, 2020-02-13 at 14:59 +0000, user wrote: > > Philipp Schafft, who allow you to publish my private message? > > I could also ask who allowed you to send me unwanted private messages? At this point any message from Philipp Schafft to me becomes absolutely unwanted. > In fact I did not notice it was sent privately until after my reply. It Notice can be found on third

2020-01-06 17:50, Philipp Schafft wrote: > Good evening, > > On Mon, 2020-01-06 at 10:24 +0000, user wrote: > > Hello. > > Is it possible to bind admin console on different port? > > > > icecast 2.4.4 > > No, this is not possible with Icecast 2.4.x. Doing that would even break > some kinds of clients. > > Please note that it would not add to

Philipp Schafft, who allow you to publish my private message? > Remove > > -Pete > > > On Feb 13, 2020, at 8:46 AM, Philipp Schafft <lion at lion.leolix.org> wrote: > > > > ???Good afternoon, > > > > please have a look into your MUA setup. You keep breaking threading for > > this thread (In-Reply-To header is set incorrectly). > >

January 7, 2020 10:56 AM, "user" <5f787a at i2pmail.org> wrote: > 2020-01-06 17:50, Philipp Schafft wrote: ... ... > > I'm consider to put icecast behind reverse proxy. It is not so easy as I > think before. Does anyone have experience with it? I run it behind a reverse proxy on apache, and everything works bar one thing - the links in the status and admin

<div dir="auto">No I think you misunderstood me. The m3u file contains the URL with the port number in it, since as far as icecast knows that's is the URL. It doesn't (and can't) know that I want a different URL. It has http://foo.bar:8000/mountpoint but I want http://foo.bar/mountpoint<div><br></div><div>It's the wrong URL from my

On Tue, Jan 07, 2020 at 08:38:41PM +0000, jake at jakebriggs.com wrote: > January 7, 2020 10:56 AM, "user" <5f787a at i2pmail.org> wrote: > > 2020-01-06 17:50, Philipp Schafft wrote: > > > > I'm consider to put icecast behind reverse proxy. It is not so easy as I > > think before. Does anyone have experience with it? > > I run it behind a

Hi Jake http://foo.bar/mountpoint is going to be interpreted as port 80 by the player You want to do http://foo.bar:8000/mountpoint > http://foo.bar/mountpoint I think you are going to have to do some port shifting from 8000 > someothernumber like 12345 on the router. regards Robert On 8/01/20 7:07 pm, jake at jakebriggs.com wrote: > No I think you misunderstood me. The m3u file

Apologies, one more question. With the edited icecast configuration I provided in my previous reply, netstat now shows the IPV6 binds but not the IPV4 binds. To your knowledge, does this seem correct? The Icecast server seems to be working properly and is accepting listener connections with IPV4 addresses. Just trying to understand why I don?t see 0.0.0.0:8000 for instance. -------------- next

Good afternoon, please have a look into your MUA setup. You keep breaking threading for this thread (In-Reply-To header is set incorrectly). On Tue, 2020-02-11 at 13:40 +0000, user wrote: > > On Thu, 2020-02-06 at 19:20 +0000, user wrote: > > > 2020-01-08 09:59, Marvin Scholz wrote: > > > Expectation on malicious activity force me to put icecast behind reverse > >

Thanks for the response. I can confirm that the recommended settings worked and now IPV6 is working as it should. If anyone is interested, these are the <listen-socket> settings I am using. <!-- You may have multiple <listen-socket> elements?> <listen-socket> <port>8000</port> <bind-address>0.0.0.0</bind-address> </listen-socket>

Good morning, On Thu, 2023-01-19 at 13:19 +0100, Marvin Scholz wrote: > On 18 Jan 2023, at 22:56, Damian wrote: > > > Another question: I see in the icecast config it states that "If a > > bind-address is not specified for a particular listen-socket, then > > the socket will be bound to all interfaces (including IPv6 if > > available). ? > > > >

Thanks bubba, but I am referring to the meaning of the line: "... INFO connection/get_ssl_certificate No SSL capability" El vie, 11-08-2017 a las 13:37 -0500, bubba watson escribi?: > It is a server message indicator. It is used to distinguish server > messages. > > Sent from my iPhone > > > On Aug 11, 2017, at 13:28, Jos? Luis Artuch <artuch at

Same... ---------- Forwarded message --------- From: Abel <romeroperezabel at gmail.com> Date: Fri, Mar 15, 2019, 2:38 PM Subject: Re: [Icecast-dev] Full HTTPS support To: Philipp Schafft <phschafft at de.loewenfelsen.net> Good afternoon, can you send audio as source over HTTPS? Also, can you use Icecast to generate .m3u, etc files with the https URL? And finally nice to see you

Hi ! Still fighting here :) /var/log/icecast2/error.log ... [2017-08-08??03:05:34] INFO main/main Icecast 2.4.2 server started [2017-08-08??03:05:34] INFO connection/get_ssl_certificate No SSL capability *** [2017-08-08??03:05:34] INFO yp/yp_update_thread YP update thread started ... What exactly does *** mean ?. Thanks ! Jos? Luis El vie, 21-07-2017 a las 19:44 +0200, Marvin Scholz escribi?:

On 1 Jun 2015, at 17:39, Jack Elliott 541 848 7021 wrote: > Marvin, > > Ah, thank you for clarifying where "webroot" is. > > The application here will be a non-public stream with one listener > client. Icecast is hosted on a computer at our radio station. It will > receive a stream from a stream client at a remote live music event. > There will be one listener: a

I'm running squid 2.6.11 on FreeBSD with a parent cache that requires authentication in order to access any web sites. It's been suggested to us by the department that runs the upstream cache that we can make some sites accessible without the client having to authenticate by getting our local squid to supply the username & password to the upstream cache for those sites. It users the

Thank you. In this case, the source client is the fallback mount, which is an mp3 file. I think I found my issue. The code in icecast.xml looks like this: <mount type="normal"> <mount-name>/stream</mount-name> <max-listeners>6</max-listeners> <burst-size>65536</burst-size>

Is this the HTTP call for injecting the “song” metadata? This is a capture (using RawCap in conjunction with Wireshark) of my AAC+ stream metadata input to IceCast that works fine. GET /admin/metadata?mode=updinfo&mount=%2FFVHradio_AAC&song=Fox%20Valley%20Hit%20radio%20-%20Hits%20from%20the%20Valley HTTP/1.0 User-Agent: RadioBOSS Authorization: Basic The same input to IceCast capture

Can you please unsubscribe me from your emails. John Dohnt support at psrfm.org.au -----Original Message----- From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of icecast-request at xiph.org Sent: Monday, 20 March 2017 10:42 AM To: icecast at xiph.org Subject: Icecast Digest, Vol 153, Issue 3 Send Icecast mailing list submissions to icecast at xiph.org To subscribe or unsubscribe