From land at uni-leipzig.de  Wed Nov 23 14:44:11 2022
From: land at uni-leipzig.de (Joerg Land)
Date: Wed, 23 Nov 2022 15:44:11 +0100
Subject: [Icecast] Config mountpoints Icecast 2.4.4
Message-ID: <20221123154411.Horde.vu7FHIq3MRrA_RLmGjDJa61@mail.uni-leipzig.de>

Hello,

I just want to change the name of mountpoint and the content of the  
variables of "stream url" "stream description" etc.

In former versions there was a gui to enter all of the changes.

But since Icecast 2.4.4 I don't know where und how to do this.

I opened all of the program directories, xml + xls without success.

It would be nice to get a hint. Sorry for this trivial thing.

Regards, Joerg




**************************************
Universitaet Leipzig
Zentrum fuer Medienproduktion (ZMP)
Dipl.-Ing. (FH) Joerg Land
04109 Leipzig, Nikolaistrasse 27-29
Tel.:  0341-97-35759
FAX:   0341-97-31135759
Email: land at uni-leipzig.de
**************************************



From s at jws.co.il  Thu Nov 24 02:33:14 2022
From: s at jws.co.il (=?UTF-8?Q?=D7=A9=D7=9E=D7=A2=D7=95=D7=9F_=D7=A7=D7=95=D7=A4=D7=A4?= =?UTF-8?Q?=D7=A8=D7=9E=D7=9F?=)
Date: Thu, 24 Nov 2022 04:33:14 +0200
Subject: [Icecast] Config mountpoints Icecast 2.4.4
In-Reply-To: <20221123154411.Horde.vu7FHIq3MRrA_RLmGjDJa61@mail.uni-leipzig.de>
References: <20221123154411.Horde.vu7FHIq3MRrA_RLmGjDJa61@mail.uni-leipzig.de>
Message-ID: <2fd80a517a3f0e83ced5d04ef22bbd9a@jws.co.il>



Hello dear Joerg,

 From your question it can be understood that you are less familiar with 
the configuration file of the software ("icecast.xml").

Basically, the answer to your questions is very simple. You won't find 
what you're looking for inside the software, because it's not there. By 
default the data you were looking for does not appear in the 
configuration file.

But, it's very easy to add them, and get the result you're looking for.
I myself always define these things directly in the configuration file, 
to overcome wrong information that will be inserted inside the encoders.

I will write to you below an example of the code that should be added to 
the software's configuration file, you should of course change the words 
to whatever suits you, but I would like to point out that as of the 
current version, some things do not have an effect as they should have 
(in my view, this is a problem with the software and not with the 
settings - the settings that I will indicate to you comes directly from 
the software's official documentation).

It is important to remember that the Icecast server must be Restart 
after each change in the software configuration file, in order for it to 
take effect. Although it is possible to settle for a Reload instead of a 
full Restart, but in my opinion, it is almost always advisable to 
Restart.

Before the code, I'll give you a brief concise explanation:

For each anchor point, you create its own customized code. If I'm not 
mistaken, there doesn't appear to be an efficient way to define those 
details so that they appear automatically in all the anchor points.
On my server, I created another anchor (which always runs), the purpose 
of which was to prevent disconnection of listeners from the stream, if 
there was a problem in the studio, and the broadcast from the studio was 
disconnected.

The code of the anchor defines which anchor point it refers to.

Let's say your anchor point is called "Live":

<mount>
     <mount-name>/live</mount-name>
     <stream-name>My Radio Name</stream-name>
     <stream-description>My Radio Description</stream-description>
     <stream-url>https://radio.example.com/</stream-url>
     <genre>Pop</genre>
</mount>

With a few other things I usually use on me:

<mount>
     <mount-name>/live</mount-name>
     <stream-name>My Radio Name</stream-name>
     <stream-description>My Radio Description</stream-description>
     <stream-url>https://radio.example.com/</stream-url>
     <genre>Pop</genre>
     <fallback-mount>/backup</fallback-mount>
     <fallback-override>1</fallback-override>
     <hidden>0</hidden>
     <public>0</public>
</mount>

Now with an explanation:

<mount> = The tag indicating the start of setting anchor details
     <mount-name>/live</mount-name>
     <stream-name>My Radio Name</stream-name> = The tag indicating the 
name of the station
     <stream-description>My Radio Description</stream-description> = The 
tag indicating the station description
     <stream-url>https://radio.example.com/</stream-url> = The tag 
indicating the link to the station website
     <genre>Pop</genre> = The tag indicating the genre of the station's 
content
     <fallback-mount>/backup</fallback-mount> = The tag indicating the 
anchor used for backup when disconnecting the anchor from the studio
     <fallback-override>1</fallback-override> = The tag that indicates 
that you must return to the source, when renewing the connection to the 
studio
     <hidden>0</hidden> = The tag indicating whether the anchor will be 
hidden from the software information page
     <public>0</public> = The tag indicating whether the anchor will be 
visible to radio station websites indexes (if your broadcast is not 
private, then you should change to 1)
</mount> = The tag indicating the end of setting anchor details

Of course there are other details that can be set, such as a different 
username and password, but I wrote mainly what you needed.

On Linux servers, the configuration file is usually located in this path 
(I edit the configuration file with a text editor, and I access it via 
SFTP, for reasons of simplicity and convenience for me):

/etc/icecast2

And the Restart command is like this:

/etc/init.d/icecast2 restart

I use a Caddy server to provide support for streaming encrypted traffic 
(fully automatically), so that browsers don't block the stream.
If this interests you, I'd be happy to show you how.
But I don't think it's right to explain everything here.

Please pay attention:
I am not a programmer or a software expert, but I have been using it for 
many years and may already know how to help you.
In any case, I would ask that you feel comfortable contacting me 
directly by email if that seems more appropriate for you.
I may be able to help you with more difficulties on the subject.
I have a little difficulty thinking about everything at once, so I may 
have forgotten some things, but I don't want to flood messages here, so 
that's why I also offered to contact me directly (if it's allowed in the 
rules here - I didn't check).

My Email is: s at jws.co.il

Good luck!!

:??? Joerg Land, 23/11/2022 16:44 ??????

> Hello,
> 
> I just want to change the name of mountpoint and the content of the  
> variables of "stream url" "stream description" etc.
> 
> In former versions there was a gui to enter all of the changes.
> 
> But since Icecast 2.4.4 I don't know where und how to do this.
> 
> I opened all of the program directories, xml + xls without success.
> 
> It would be nice to get a hint. Sorry for this trivial thing.
> 
> Regards, Joerg
> 
> **************************************
> Universitaet Leipzig
> Zentrum fuer Medienproduktion (ZMP)
> Dipl.-Ing. (FH) Joerg Land
> 04109 Leipzig, Nikolaistrasse 27-29
> Tel.:  0341-97-35759
> FAX:   0341-97-31135759
> Email: land at uni-leipzig.de
> **************************************
> 
> _______________________________________________
> 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/20221124/07bcabcf/attachment.htm>

From jordan at subj.am  Thu Nov 24 03:35:49 2022
From: jordan at subj.am (Jordan Erickson)
Date: Wed, 23 Nov 2022 19:35:49 -0800
Subject: [Icecast] Config mountpoints Icecast 2.4.4
In-Reply-To: <2fd80a517a3f0e83ced5d04ef22bbd9a@jws.co.il>
References: <20221123154411.Horde.vu7FHIq3MRrA_RLmGjDJa61@mail.uni-leipzig.de>
 <2fd80a517a3f0e83ced5d04ef22bbd9a@jws.co.il>
Message-ID: <9e47f7ff-c7f9-35e3-3e2f-b7cec5f7bf8e@subj.am>

Just a quick sidenote: though it's not technically necessary, it's 
advisable to create an extension of the codec type for the mountpoint 
configured, such as:

<mount-name>/live.opus</mount-name>

This allows a wider range of listener clients to understand how to 
handle the incoming stream.


Sincerely,
Jordan Erickson


On 11/23/22 18:33, ????? ??????? wrote:
>
> Hello dear Joerg,
>
> From your question it can be understood that you are less familiar 
> with the configuration file of the software ("icecast.xml").
>
> Basically, the answer to your questions is very simple. You won't find 
> what you're looking for inside the software, because it's not there. 
> By default the data you were looking for does not appear in the 
> configuration file.
>
> But, it's very easy to add them, and get the result you're looking for.
> I myself always define these things directly in the configuration 
> file, to overcome wrong information that will be inserted inside the 
> encoders.
>
> I will write to you below an example of the code that should be added 
> to the software's configuration file, you should of course change the 
> words to whatever suits you, but I would like to point out that as of 
> the current version, some things do not have an effect as they should 
> have (in my view, this is a problem with the software and not with the 
> settings - the settings that I will indicate to you comes directly 
> from the software's official documentation).
>
> It is important to remember that the Icecast server must be Restart 
> after each change in the software configuration file, in order for it 
> to take effect. Although it is possible to settle for a Reload instead 
> of a full Restart, but in my opinion, it is almost always advisable to 
> Restart.
>
> Before the code, I'll give you a brief concise explanation:
>
> For each anchor point, you create its own customized code. If I'm not 
> mistaken, there doesn't appear to be an efficient way to define those 
> details so that they appear automatically in all the anchor points.
> On my server, I created another anchor (which always runs), the 
> purpose of which was to prevent disconnection of listeners from the 
> stream, if there was a problem in the studio, and the broadcast from 
> the studio was disconnected.
>
> The code of the anchor defines which anchor point it refers to.
>
> Let's say your anchor point is called "Live":
>
> <mount>
> ? ? <mount-name>/live</mount-name>
> ? ? <stream-name>My Radio Name</stream-name>
> ? ? <stream-description>My Radio Description</stream-description>
> <stream-url>https://radio.example.com/</stream-url>
> ? ? <genre>Pop</genre>
> </mount>
>
> With a few other things I usually use on me:
>
> <mount>
> ? ? <mount-name>/live</mount-name>
> ? ? <stream-name>My Radio Name</stream-name>
> ? ? <stream-description>My Radio Description</stream-description>
> <stream-url>https://radio.example.com/</stream-url>
> ? ? <genre>Pop</genre>
> ? ? <fallback-mount>/backup</fallback-mount>
> ? ? <fallback-override>1</fallback-override>
> ? ? <hidden>0</hidden>
> ? ? <public>0</public>
> </mount>
>
> Now with an explanation:
>
> <mount> = The tag indicating the start of setting anchor details
> ? ? <mount-name>/live</mount-name>
> ? ? <stream-name>My Radio Name</stream-name> = The tag indicating the 
> name of the station
> ? ? <stream-description>My Radio Description</stream-description> = 
> The tag indicating the station description
> <stream-url>https://radio.example.com/</stream-url> = The tag 
> indicating the link to the station website
> ? ? <genre>Pop</genre> = The tag indicating the genre of the station's 
> content
> ? ? <fallback-mount>/backup</fallback-mount> = The tag indicating the 
> anchor used for backup when disconnecting the anchor from the studio
> ? ? <fallback-override>1</fallback-override> = The tag that indicates 
> that you must return to the source, when renewing the connection to 
> the studio
> ? ? <hidden>0</hidden> = The tag indicating whether the anchor will be 
> hidden from the software information page
> ? ? <public>0</public> = The tag indicating whether the anchor will be 
> visible to radio station websites indexes (if your broadcast is not 
> private, then you should change to 1)
> </mount> = The tag indicating the end of setting anchor details
>
> Of course there are other details that can be set, such as a different 
> username and password, but I wrote mainly what you needed.
>
> On Linux servers, the configuration file is usually located in this 
> path (I edit the configuration file with a text editor, and I access 
> it via SFTP, for reasons of simplicity and convenience for me):
>
> /etc/icecast2
>
> And the Restart command is like this:
>
> /etc/init.d/icecast2 restart
>
> I use a Caddy server to provide support for streaming encrypted 
> traffic (fully automatically), so that browsers don't block the stream.
> If this interests you, I'd be happy to show you how.
> But I don't think it's right to explain everything here.
>
> Please pay attention:
> I am not a programmer or a software expert, but I have been using it 
> for many years and may already know how to help you.
> In any case, I would ask that you feel comfortable contacting me 
> directly by email if that seems more appropriate for you.
> I may be able to help you with more difficulties on the subject.
> I have a little difficulty thinking about everything at once, so I may 
> have forgotten some things, but I don't want to flood messages here, 
> so that's why I also offered to contact me directly (if it's allowed 
> in the rules here - I didn't check).
>
> My Email is: s at jws.co.il
>
> Good luck!!
>
> :??? Joerg Land, 23/11/2022 16:44 ??????
>
>     Hello,
>
>     I just want to change the name of mountpoint and the content of
>     the ?variables of "stream url" "stream description" etc.
>
>     In?former?versions?there?was?a?gui?to?enter?all?of?the?changes.
>
>     But?since?Icecast?2.4.4?I?don't?know?where?und?how?to?do?this.
>
>     I?opened?all?of?the?program?directories,?xml?+?xls?without?success.
>
>     It?would?be?nice?to?get?a?hint.?Sorry?for?this?trivial?thing.
>
>     Regards,?Joerg
>
>
>
>
>     **************************************
>     Universitaet?Leipzig
>     Zentrum?fuer?Medienproduktion?(ZMP)
>     Dipl.-Ing.?(FH)?Joerg?Land
>     04109?Leipzig,?Nikolaistrasse?27-29
>     Tel.:??0341-97-35759
>     FAX:???0341-97-31135759
>     Email: land at uni-leipzig.de
>     **************************************
>
>     _______________________________________________
>     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

-- 
Jordan Erickson
SubJam, SPC -https://subj.am/
+1 360.209.2057
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20221123/e848ed79/attachment.htm>

From tyctor at post.cz  Thu Nov 24 23:07:58 2022
From: tyctor at post.cz (tyctor)
Date: Fri, 25 Nov 2022 00:07:58 +0100
Subject: [Icecast] random Login failed from icecast2
Message-ID: <c607ecdd9492c75296e22d17f501b659a7d60f3f.camel@post.cz>

hi

i upgraded our VPS from Ubuntu 18.04 to Ubuntu 22.04
and weird things started to happen

we are using ezstream 1.0.2 as source player for our comunity radio
and icecast 2.4.4 with SSL from ubuntu repositories

what is happening is that ezstream is getting randomly Login failed

ezstream[560009]: stream: default: connect: [77.93.223.221]:8000: error
-3: Login failed
ezstream[560009]: initial server connection failed


on old system this never happend
but we not used ubuntu version because (due to not compiled SSL
support) but version from
http://download.opensuse.org/repositories/multimedia:/xiph/xUbuntu_18.04/


has somebody similar experience with ubuntu 22.04 and its icecast
2.4.4?

is there xiph version for ubuntu 22.04? i can find only for ubuntu
19.10


thank for any reply
viktor


From tyctor at post.cz  Fri Nov 25 21:45:58 2022
From: tyctor at post.cz (tyctor)
Date: Fri, 25 Nov 2022 22:45:58 +0100
Subject: [Icecast] random Login failed from icecast2
In-Reply-To: <c607ecdd9492c75296e22d17f501b659a7d60f3f.camel@post.cz>
References: <c607ecdd9492c75296e22d17f501b659a7d60f3f.camel@post.cz>
Message-ID: <e228488b23c7c2deabb6bd4ed4211a949a3837bd.camel@post.cz>

ok, solved, 

i added another mount, but sources was limited so thats why i was
getting Login failed...

so i increased sources and it is working like a charm again

:o)

v.


On Fri, 2022-11-25 at 00:07 +0100, tyctor wrote:
> hi
> 
> i upgraded our VPS from Ubuntu 18.04 to Ubuntu 22.04
> and weird things started to happen
> 
> we are using ezstream 1.0.2 as source player for our comunity radio
> and icecast 2.4.4 with SSL from ubuntu repositories
> 
> what is happening is that ezstream is getting randomly Login failed
> 
> ezstream[560009]: stream: default: connect: [77.93.223.221]:8000:
> error
> -3: Login failed
> ezstream[560009]: initial server connection failed
> 
> 
> on old system this never happend
> but we not used ubuntu version because (due to not compiled SSL
> support) but version from
> http://download.opensuse.org/repositories/multimedia:/xiph/xUbuntu_18.04/
> 
> 
> has somebody similar experience with ubuntu 22.04 and its icecast
> 2.4.4?
> 
> is there xiph version for ubuntu 22.04? i can find only for ubuntu
> 19.10
> 
> 
> thank for any reply
> viktor