#Icecast server software#
#Icecast server code#
#Icecast server password#

If your stream is HTTP S, your website is HTTP SВ and your IcecastВ page is HTTP,В you generally cannot display titles withoutВ using the proxy.

In this case, you can try the proxy (make sure your web server allows it) and/or eventually ask to your streaming provider to enable the CORS policies on the server (thish is how it should be) To check this, open the browser javascript console, and check if you see any error mentioning a CORS block preventing the access.

#Icecast server code#

This means that your Icecast server is missing a little line of code that allows your website to read the song titles. If the protocol is ok, and you see the json data, but still no title appears, your provider may be blocking the access because of wrong Cross Origin Resource Sharing policies (CORS).If your websiteВ is HTTPSВ and your stream is HTTP, you generally cannotВ display titles, nor listen to the music.В In this case you may want to put the site in http or change streaming provider.Open it in the browser, and make sure you can see the Json data (see screenshots above) If you canвЂ™t see the titles, the first thing to do is to verify the status-json.xsl page.You can set the numeric channel ID of the right song titles in your channel settings. In this example, there is no mountpoint required, but there are multiple channels. To know the correct settings, you can open the stats file, copy the json output and paste it on jsonviewer This is an example of a multi-channel icecast page There is no fixed standard for this, as itвЂ™s up to the system administrator, so you may need to check the structure of your feed to find the right settings. Some Icecast formats use different moutpoint URLs for the data, some others use always the same URL, containing the song titles of every channel. So, if you donвЂ™t know the exact stats URL of your Icecast channel, only your provider can give you this information. If you donвЂ™t knowВ the correct Icecast status json URL, you need to ask to your streaming providerВ (your broadcasting provider), as the address can be anything, like /white-unicorn-flying.xsl The standard endpoint for the Icecast stats page is /stats-json.xsl, but some can use:ДЄs any streaming provider can use a custom URL. Icecast mountpoint:В not required Alternative endpoints You should take some screenshots and contact your streaming provider, asking themВ to fix it.

#Icecast server software#

It means that your JSON formatting is broken, and this is usually caused by a software error on your streaming server. ДЄfter pasting it, click вЂњViewerвЂќ and you should see the formatted content, like this example of a multi-channel Icecast server: You can copy the content of the page and paste it in the website to verify if itвЂ™s correct. You should add the Endpoint (copy it from above) and attach it to the end of your Icecast url, you should be able to see the json data. IcecastВ can have anyВ custom URL, but the default STATS endpoint is /status-json.xsl Step 3:В Now you need to enter your STATS URL. Step 2: make sure there is no Metadata checked and there is NO shoutcast host set and you should hear whatever is coming through your soundcard.Step 1:В In your WordPress Admin, edit or create your Radio Channel If you do this, when you test the stream open xmms and enter into the 'open location' field (see section above) the following URL: Then use any mount point you like, for example /firststream will work just fine.

#Icecast server password#

However if it is running then all you need to know is the default password is hackme.ДЇor the purposes of running MuSE with the Icecast server that you have just set up, use the following (all of which can be altered by editing the 'icecast.xml' file): If you find that there is an error then see the next section of configuring Iceast2. the '-c' parameter here means 'config', so it is a way of telling the icecast command to use the config file 'icecast.xml' I will use the cp command because then I leave a copy of the original just in case. So let's say I am in the Icecast2 source directory and the '' file is on the 'conf' directory, well maybe it would be easier if I moved it up to the directory I am working in and changed the name to 'icecast.xml'. If its not there then run updatedb and then do a locate or slocate to try and find the file. If you installed from source then you will find the file in the Icecast2 source directory within the conf directory. The trick is to find your 'icecast.xml' file. So to start Icecast the basic command is: This is very handy if you need to run it on a remote server which is very often the case. In Linux, Icecast is controlled completely from the command line. Icecast: StartingLinux Starting Icecast in Linux