similar to: Server URL vs. Listen URL

I'm running a TLS secured Icecast 2.4.4 on Windows server. It streams across the Internet fine. My config XML has: <hostname>stream.myserver.org</hostname> <listen-socket> <port>443</port> <bind-address>192.168.1.35</bind-address> <ssl>1</ssl> </listen-socket> <listen-socket>

Hello, I didn't want to have to choose between Icecast running on port 80 and all my Apache virtual hosts, running also on port 80, on my sole external IP address. I didn't want either to open port 8000 on my firewall because I wanted all users being able to reach Icecast even the ones behind enterprise firewalls. So I managed to run Apache 2.2 listening on port 80 and Icecast 2.3.2

No, this is a relay of a Shoutcast server. Everything is configured in https on IceCast ( https://relay2.dgnet.be/ ) , except this value listenurl ( in Admin / Mountpoint) which in cannot change apparently. So the .m3u file is created with an http:// link ( instead of https:// ) But the stream is available and working in https://relay2.dgnet.be:443/different.ogg Danny From: Icecast

I have successfully installed IceCast with SSL support : https://relay2.dgnet.be/ Stream is working fine with this URL : https://relay2.dgnet.be:443/different.ogg Nevertheless the listen URL still points to http://relay2.dgnet.be:443/different.ogg ( without https then ) So the links provided/generated by IceCast are wrong . What did I miss ? Is it possible to force the listenurl value in the

Hi Justin, >Are you talking about the listen URL in the Icecast status page? I think it is currently not able show the link as httpS. Maybe one of the Icecast experts can confirm that. Yes I was talking about this value. The workaround was to put my own m3u file ( with the correct link ) in the icecast web folder > Is this truly an OGG audio file? Why does the server response give a

On Wed, Jun 25, 2003 at 03:33:25PM +1000, Michael Smith wrote: > > Is the metadata relayed to connecting clients. i.e. take a client that > supports shoutcast-style metadata, like winamp (and probably most others). > Connect as a listener to the relay. Do you get metadata? You should. If you > don't, the metadata relaying could have been broken (I think this is >

On Wed, Jun 25, 2003 at 11:34:07AM +1000, Michael Smith wrote: > > > 2) Should relay icy/x-audiocast stream metadata when connecting to > > icecast1/shoutcast/etc so that this information is available to YP > > Eh? It does. I even tested that with someone's shoutcast stream. It works. > Just add >

Hi Prince Run ps -ef|grep icecast and make sure that you are looking at the correct config file. In my example it is /etc/icecast/icecast.xml I pulled my hair out once on something simple as that. Hope it helps Sent from Mail for Windows 10 From: Prince Naryk Sent: Thursday, March 28, 2019 10:13 AM To: Icecast streaming server user discussions Subject: Re: [Icecast] YP Directory Listing

Hi I am running the icecast ver 2.3.1. I am trying to get the video working but everytime I try to view the video and audio ( http://localhost:8000/different.ogg) , I can only get the audio no matter how I try to access the stream ( quicktime,VLC, cortado java applet ) the only thing I get is audio. I am running the server in a Red Hat Linux enterprise 4. Any help will be appreciated ezstream

Hi, I am having problems with sending a video stream to Icecast server. On the icecast management platform my stream is being considered as an audio stream?? and I am unable to play it I am with no ideas on how to solve this. Am I doing something wrong? Please take a look on the code bellow Thanks in advance genre various listener_peak 0 listeners 0 listenurl http://192.168.11.61:8000/gcs.ogg

Hi, On 3/28/19 7:25 AM, Prince Naryk wrote: > i understand, but why does my listenurl in the admin panel, still > says, example.com:port/stream > the hostname is still example.com <http://example.com> though i > already changed my hostname in the config file Such changes take effect only after restarting the server. Cheers, Thomas > > On Thu, Mar 28, 2019 at 3:03 PM

On Wednesday 25 June 2003 15:55, Arc wrote: > On Wed, Jun 25, 2003 at 03:33:25PM +1000, Michael Smith wrote: > > Is the metadata relayed to connecting clients. i.e. take a client that > > supports shoutcast-style metadata, like winamp (and probably most > > others). Connect as a listener to the relay. Do you get metadata? You > > should. If you don't, the metadata

I run two streams from ezstream via Icecast2 - one over http and one over https. In the ezstream config file I have defined two servers (http and https) and the two streams point to the different servers (by their names). But, if I go to the following two url's, Icecast report same (http-) 'streaming url' for both: https://radio.horsens-garage.rocks:8443/

Hello, I've been running three mp3 streams off icecast2 and ices0 on a FreeBSD 5.4 box for a while. I've been getting some flakiness for a few weeks, where the stream would stop and i'd have to restart the server. After the last update to icecast2 now whenever i try to connect to the streams using say winamp latest for windows i keep getting error 404's. My software versions

Hi Martin, Yes, I am using ffmpeg icecast protocol Marvin Scholz <epirat07 at gmail.com> escreveu em qui, 11/07/2019 às 20:53 : > On 11 Jul 2019, at 20:50, Pedro Constantino wrote: > > > Hi, > > > > I am having problems with sending a video stream to Icecast server. On > > the > > icecast management platform my stream is being considered as an audio

After reading this posting in the icecast archives (http://www.xiph.org/archives/icecast/3483.html) about setting the stream url in the metadata with ices2, I couldn't see that it actually was possible to set the ice-url anywhere. Please let me know if the attached patch is any use, and if I'm sending it to the right place! (Unix linefeeds). I use it with Peercast. It means you can add

I have been trying to get my station listed in the icecast directory. I would appreciate someone reviewing this to see what is wrong. I've studied the documentation and I think I am doing what is required, but my station is not showing up in the icecast yp directory. I'm using icecast 2.3.2 I have the directory entry in the icecast.xml config file: <directory>

I can’t see your Icecast server from here, so it appears to be a port forwarding issue to me. From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Prince Naryk Sent: Thursday, 4 April 2019 12:44 a.m. To: Icecast streaming server user discussions Subject: Re: [Icecast] YP Directory Listing Concern Hi there! yes, i tried to change to localhost/127.0.0.1 when listening in my OWN network

Most likely because your router will not forward your public IP address on your LAN. You will need to substitute the IP with 127.0.0.1 when listening internally. From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Prince Naryk Sent: Wednesday, 3 April 2019 12:35 a.m. To: Icecast streaming server user discussions Subject: Re: [Icecast] YP Directory Listing Concern hi there I just

Hello fellow mailing list readers, My question relates to multiple / duplicate connections to the ice cast server from the same IP address. I am well aware that this is an issue that lies with the music player (listener agent) used by the listener. When a listener connects to the stream, sometimes it appears as two connections to the stream from the same IP address. This may last only a few