Icecast - Apr 2019 - Question about replacing the web interface with an audio stream

What’s wrong with reverse proxying icecast through apache?
In my case, it’s just a measure to allow a secondary point of access to a stream
from public wifi that only allows ports 80 and 443.
Is it just a potential resource usage implication?

> On Apr 7, 2019, at 6:12 PM, Humberto Rodriguez <sub at
hrfinancial.com> wrote:
> 
> Why not reproduce the stream using the <audio> element of HTML in a
regular webpage?  You could turn autoplay on and the strean would sound
automatically on most browsers, not so on Google’s.
>  
> Humberto
>  
>  
>  
> From: Icecast <icecast-bounces at xiph.org> On Behalf Of John Molane
> Sent: Sunday, April 7, 2019 12:44 PM
> To: icecast at xiph.org
> Subject: [Icecast] Question about replacing the web interface with an audio
stream
>  
> Hello,
>  
> I was wondering if someone here could help me out.
>  
> I have a domain that I'm using for Icecast, let's use
"domain.com" as an example. Icecast is running on port 80. The problem
is that when I go to "domain.com" in my web browser, it brings up the
web interface.
> I want to configure it so that instead of showing the status page, it
immediately goes to one of my mountpoints. This would make it so people
don't have to remember the full path to the mountpoint.
>  
> Is this possible? I apologize if I'm overlooking something simple. This
doesn't seem to be a very common way of using Icecast.
>  
>  
> Thanks.
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20190408/97fa4c0a/attachment.html>

Just bind icecast to port 80...
Its not uncommon to use a subdomain for a stream..

בתאריך יום ב׳, 8 באפר׳ 2019, 22:28, מאת Jordan Verner ‏<jordan at
caturria.ca>:
> What’s wrong with reverse proxying icecast through apache?
> In my case, it’s just a measure to allow a secondary point of access to a
> stream from public wifi that only allows ports 80 and 443.
> Is it just a potential resource usage implication?
>
>
> On Apr 7, 2019, at 6:12 PM, Humberto Rodriguez <sub at
hrfinancial.com>
> wrote:
>
> Why not reproduce the stream using the <audio> element of HTML in a
> regular webpage?  You could turn autoplay on and the strean would sound
> automatically on most browsers, not so on Google’s.
>
> Humberto
>
>
>
> *From:* Icecast <icecast-bounces at xiph.org> *On Behalf Of *John
Molane
> *Sent:* Sunday, April 7, 2019 12:44 PM
> *To:* icecast at xiph.org
> *Subject:* [Icecast] Question about replacing the web interface with an
> audio stream
>
> Hello,
>
> I was wondering if someone here could help me out.
>
> I have a domain that I'm using for Icecast, let's use
"domain.com" as an
> example. Icecast is running on port 80. The problem is that when I go to
"
> domain.com" in my web browser, it brings up the web interface.
> I want to configure it so that instead of showing the status page, it
> immediately goes to one of my mountpoints. This would make it so people
> don't have to remember the full path to the mountpoint.
>
> Is this possible? I apologize if I'm overlooking something simple. This
> doesn't seem to be a very common way of using Icecast.
>
>
> Thanks.
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20190408/8c5d65aa/attachment.html>

Okay, but you’d have to be able/willing to employ a dedicated IP to that, plus
run Icecast as root.
What are the negative technical implications of running icecast on port 8000
(suitable for most users) and then running a reverse proxy to accommodate public
wifi with port restrictions?

> On Apr 8, 2019, at 3:31 PM, Yahav Shasha <yahav.shasha at gmail.com>
wrote:
> 
> Just bind icecast to port 80...
> Its not uncommon to use a subdomain for a stream..
> 
> בתאריך יום ב׳, 8 באפר׳ 2019, 22:28, מאת Jordan Verner ‏<jordan at
caturria.ca <mailto:jordan at caturria.ca>>:
> What’s wrong with reverse proxying icecast through apache?
> In my case, it’s just a measure to allow a secondary point of access to a
stream from public wifi that only allows ports 80 and 443.
> Is it just a potential resource usage implication?
> 
> 
>> On Apr 7, 2019, at 6:12 PM, Humberto Rodriguez <sub at
hrfinancial.com <mailto:sub at hrfinancial.com>> wrote:
>> 
>> Why not reproduce the stream using the <audio> element of HTML in
a regular webpage?  You could turn autoplay on and the strean would sound
automatically on most browsers, not so on Google’s.
>>  
>> Humberto
>>  
>>  
>>  
>> From: Icecast <icecast-bounces at xiph.org
<mailto:icecast-bounces at xiph.org>> On Behalf Of John Molane
>> Sent: Sunday, April 7, 2019 12:44 PM
>> To: icecast at xiph.org <mailto:icecast at xiph.org>
>> Subject: [Icecast] Question about replacing the web interface with an
audio stream
>>  
>> Hello,
>>  
>> I was wondering if someone here could help me out.
>>  
>> I have a domain that I'm using for Icecast, let's use
"domain.com <http://domain.com/>" as an example. Icecast is
running on port 80. The problem is that when I go to "domain.com
<http://domain.com/>" in my web browser, it brings up the web
interface.
>> I want to configure it so that instead of showing the status page, it
immediately goes to one of my mountpoints. This would make it so people
don't have to remember the full path to the mountpoint.
>>  
>> Is this possible? I apologize if I'm overlooking something simple.
This doesn't seem to be a very common way of using Icecast.
>>  
>>  
>> Thanks.
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org <mailto:Icecast at xiph.org>
>> http://lists.xiph.org/mailman/listinfo/icecast
<http://lists.xiph.org/mailman/listinfo/icecast>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org <mailto:Icecast at xiph.org>
> http://lists.xiph.org/mailman/listinfo/icecast
<http://lists.xiph.org/mailman/listinfo/icecast>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20190408/c221cfc2/attachment.html>