similar to: New Icecast Alternative: Rocket Streaming Audio Server

@Mikel You could use Centova's port 80 proxy meanwhile couldn't you? Also. Centova Cast doesn't have an SSL setting for the servers unless you're manually overwriting the server config files.. or is it? On Sat, Feb 29, 2020 at 6:13 PM Mikel Sanz | 20 Comunicación < mikel at 20comunicacion.com> wrote: > For example, in my case, we use several servers with Centovacast,

For example, in my case, we use several servers with Centovacast, with several Icecast2 services. Version 2.5 of Icecast2, allows to respond to http and https connections from the same port, but takes years in beta. Centovacast does not update its panel, waiting for the final version of Icecast 2.5 to be released. Chrome has been warning for months that this would happen in February, but no one

Hi all, Can you explain the use case here a bit more? I think I'm missing something in my understanding. If you enable TLS/HTTPS, you should enable it on a different port (eg. 443) and keep your existing HTTP port for Icecast so that your stations will continue to work in external players (Winamp, playlists, VLC, etc.). However, you should update all embedded links to your stream on your

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Today we became aware of a bug in the Icecast code handling source client URL-authentication and are releasing a security fix. The bug was discovered by Juliane Holzt, who we'd like to thank for bringing this to our attention and providing us with further details. Affected Icecast versions: 2.3.3(first release with stream_auth) 2.4.0 2.4.1 Fix

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Today we became aware of a bug in the Icecast code handling source client URL-authentication and are releasing a security fix. The bug was discovered by Juliane Holzt, who we'd like to thank for bringing this to our attention and providing us with further details. Affected Icecast versions: 2.3.3(first release with stream_auth) 2.4.0 2.4.1 Fix

Hi Ian, Today i fired up an old VM with a bittorrent client, trying to download some torrents. I seem to be hitting the unlikely case of "xennet: skb rides the rocket: xx slots" and this results in some dropped packets in domU, I don''t see any warnings in dom0. I have added some extra info, but i don''t have enough knowledge if this could/should be prevented from

Which Icecast Version are you using? This sounds like a bug that was fixed in recent versions. 2.4 is not exact enough, we need to know the full version number, please :) On 2 Nov 2016, at 10:52, unosonic wrote: > > hello, > > this is a bit special I guess... > Icercast 2.4 > > I have several mounts of type=normal, with staticly defined > user/password > as well as

Just starting a new thread so that it''s easy to follow. I just submitted a patch at trac to add a new class method called "set_default_values" ( not a great name I think ), which lets you do all kinds of crazy stuff with setting default values. This ticket is at http://dev.rubyonrails.org/ticket/9093 and example pastie is at http://pastie.caboo.se/81925 It also lets you make

Good morning, On Tue, 2020-06-16 at 13:25 +0000, Christian Stoller wrote: > Hi, > > we are using Icecast with url authentication for some days now. This > generally works quite well. But our web service that provides the > authentication check sometimes gets requests with the following > parameters: > > { > "action":"stream_auth", >

Hi Philipp, Thanks for your reply. It really helped. Did I understand you correctly that we should respond to those requests sent by Icecast without username and password with HTTP status code 200 and the header "Icecast-Auth-Message: No username provided"? Best regards, Christian > Good morning, > > On Tue, 2020-06-16 at 13:25 +0000, Christian Stoller wrote: >> Hi,

> On Wed, Nov 8, 2017 at 4:22 PM, Amye Scavarda <amye at redhat.com <mailto:amye at redhat.com>> wrote: > From today's community meeting, we had an item from the issue queue: > https://github.com/gluster/community/issues/13 <https://github.com/gluster/community/issues/13> > > Should we have a Gluster Community slack team? I'm interested in >

Hi All, I am cross posting this to the Asterisk Users, Biz, and Dev lists at the suggestion of David Duffet, so sorry if you see it multiple times. As this year Astricon is in Orlando, and most of us are tech geeks in on form or another, we are trying to organize a road trip to see NASA's Kennedy Space Center. I have been in touch with their group sales office and was told that there is a

Hi, we are using Icecast with url authentication for some days now. This generally works quite well. But our web service that provides the authentication check sometimes gets requests with the following parameters: { "action":"stream_auth", "mount":"/stream", "ip":"xxxxx", "server":"xxxx.yyyy.de",

Sorry, apparently I forgot that we are looking at the Monday before Devcon for this trip. > ------------------------------ > > Message: 4 > Date: Wed, 24 Jun 2015 11:59:29 +0300 > From: Eric Klein <eric.klein at greenfieldtech.net> > To: asterisk-users at lists.digium.com > Subject: [asterisk-users] Organizing a Pre Astricon road trip > Message-ID: >

Hi, I've been using icecast-2.3.1 for some time now and it is really working well for me, solid as a rock (no crashes) and running 100's of streams and 1000's of listeners, but in order to support authentication and have easier configuration I want to start using the url authentication (esp. the stream_auth) and mount-name wildcards that are supported by icecast-2.3.2-kh17.

Not all browsers support the ICY HTTP Streaming Protocol. For AAC, it requires ADTS support, which contrary to popular belief, IS NOT RAW. It is AAC frames in an audio transport stream, not video TS. To play this requires specific support, and it also needs to know about the embedded metadata, which once again, contrary to popular belief, ICY metadata IS NOT ID3vX. ICY MP3 streaming is similar,

On 20 Jul 2020, at 13:02, Damian wrote: >> >> On 20 Jul 2020, at 1:12, Damian wrote: >> >>> I solved the issue by adding my own m3u files to >>> /usr/share/icecast/web but I am not sure if this is icecast >>> best-practice. This also raises a few other issues as well… http >>> stream links don’t appear on the icecast stream directory and

Hello- You guys have done an excellent job with the Icecast2 server. I probably don't need to tell you that, but I did anyway. We are Coding Technologies licensees and have recently developed a streaming audio encoder supporting AAC/HE-AAC/aacPlus using RTSP/RTP, SHOUTcast HTTP/ICY, and Icecast2 HTTP/ICY, Orban Opticodec-PC. More information here:

System: Icecast 2.4.1 and 2.4.2, OS: CentOS 6.6 x64 Tried to install icecast using following two different methods described in these links: (1) http://www.ukhost4u.co.uk/blog/538/install-icecast-2-centos-6-server/ (2) https://www.servint.net/university/article/taking-the-chill-out-of-installing-icecast/ Both of these resulted in working and stable icecast, but without the possibility of url

Hi Phil, > I've been watching this presentation from a 2014 LLVM dev meeting Thanks for your sharing! I am reviewing: * The chapter 10 (Instruction Level Parallelism) and chapter 11 (Optimizing for Parallelism and Locality) of Compiler Principle[1] * Adding and Optimizing a Subtarget for MIScheduler[2] by Dave Estes * Scheduler for in-order processors - what's present and