From rhailman at trentradio.ca Thu Feb 2 22:53:20 2023 From: rhailman at trentradio.ca (Rob Hailman) Date: Thu, 2 Feb 2023 17:53:20 -0500 Subject: [Icecast] "Ghost" connections causing connection limit to be reached Message-ID: Hello, I've been having an issue periodically where our Icecast server (which is set to a max 200 connections) will reach that limit and start rejecting all connections, but most of the connections don't seem to be real active listeners. We are running icecast 2.4.4, installed via apt on Ubuntu 22.04.1 LTS. We have four streams - two mp3 and two ogg. It seems like what is happening is that connections to the ogg streams are never getting released - so the number of clients will go up and up until all 200 connections are taken up. An excerpt from error.log, showing the mp3 stream count fluctuating but the .ogg count only increasing: [2023-01-29 10:25:46] INFO source/source_main listener count on /hi-fi now 6 [2023-01-29 10:25:47] INFO source/source_main listener count on /hi-fi now 5 [2023-01-29 10:25:47] INFO source/source_main listener count on /hi-fi.ogg now 124 [2023-01-29 10:25:51] INFO source/source_main listener count on /hi-fi now 4 [2023-01-29 10:26:17] INFO source/source_main listener count on /hi-fi.ogg now 125 [2023-01-29 10:26:47] INFO source/source_main listener count on /hi-fi.ogg now 126 When I restart icecast, the logs will show all 200 connections being released - and in access.log, most of the .ogg connections will be for very long durations with very small amounts of data transferred - for example: 77.88.9.3 - - [02/Feb/2023:21:40:29 +0000] "GET /hi-fi.ogg HTTP/1.1" 200 422 "-" "Mozilla/5.0 (compatible; YandexBot/3.0; +http://yandex.com/bots)" 2694965 If I'm reading that correctly, the connection was open for 31 days with 422 bytes transferred. Many (but not all) of these connections seem to be bots. Would be happy to provide the full log files but didn't want to send >1MB files to the whole list. Is this a possible configuration issue, an Icecast bug, or something else? Any help or suggestions would be greatly appreciated! Thanks, Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: From uktony at radiocompany.net Fri Feb 3 09:50:16 2023 From: uktony at radiocompany.net (Tony Harding) Date: Fri, 3 Feb 2023 17:50:16 +0800 Subject: [Icecast] "Ghost" connections causing connection limit to be reached In-Reply-To: Message-ID: <20230203095743.494A28139A@smtp1.osuosl.org> Bots are a Web Crawler problem. They check a web page and follow all the links. One is to your stream. They wait for the ?Page? to finish loading, but as this is a stream, it never finishes loading. They just see data coming and do not check if it is audio or HTML. ? Not that I am advocating for Shoutcast, but it does have two features that would be useful, A ban list, and a maximum duration setting. No one listens for more than 24 hours. ? Tony ? _____ From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Rob Hailman Sent: Friday, February 3, 2023 6:53 AM To: icecast at xiph.org Subject: [Icecast] "Ghost" connections causing connection limit to be reached ? Hello, ? I've been having an issue periodically where our Icecast server (which is set to a max 200 connections) will reach that limit and start rejecting all connections, but most of the connections don't seem to be real active listeners. ? We are running icecast 2.4.4, installed via apt on Ubuntu 22.04.1 LTS. ? We have four streams - two mp3 and two ogg. It seems like what is happening is that connections to the ogg streams are never getting released - so the number of clients will go up and up until all 200 connections are taken up. An excerpt from error.log, showing the mp3 stream count fluctuating but the .ogg count only increasing: ? [2023-01-29 ?10:25:46] INFO source/source_main listener count on /hi-fi now 6 [2023-01-29 ?10:25:47] INFO source/source_main listener count on /hi-fi now 5 [2023-01-29 ?10:25:47] INFO source/source_main listener count on /hi-fi.ogg now 124 [2023-01-29 ?10:25:51] INFO source/source_main listener count on /hi-fi now 4 [2023-01-29 ?10:26:17] INFO source/source_main listener count on /hi-fi.ogg now 125 [2023-01-29 ?10:26:47] INFO source/source_main listener count on /hi-fi.ogg now 126 ? When I restart icecast, the logs will show all 200 connections being released - and in access.log, most of the .ogg connections will be for very long durations with very small amounts of data transferred - for example: 77.88.9.3 - - [02/Feb/2023:21:40:29 +0000] "GET /hi-fi.ogg HTTP/1.1" 200 422 "-" "Mozilla/5.0 (compatible; YandexBot/3.0; +http://yandex.com/bots)" 2694965 ? If I'm reading that correctly, the connection was open for ?31 days with 422 bytes transferred. Many (but not all) of these connections seem to be bots. ? Would be happy to provide the full log files but didn't want to send >1MB files to the whole list. ? Is this a possible configuration issue, an Icecast bug, or something else? Any help or suggestions would be greatly appreciated! ? Thanks, Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: From sm at noisynotes.com Fri Feb 3 11:46:54 2023 From: sm at noisynotes.com (Steve Matzura) Date: Fri, 3 Feb 2023 06:46:54 -0500 Subject: [Icecast] Still struggling with secure connection to server Message-ID: I have made some progress though. According to the documentation for SSL-secured connections: ssl-certificate If specified, this points to the location of a file that contains both the X.509 private and public key. This is required for HTTPS support to be enabled. I created the required file by concatenating our public and private keys. However, when I connect to the port using a browser, I get the PR_END_OF_FILE_ERROR code, and the message: ? The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. ? Please contact the website owners to inform them of this problem. The keys are valid. If they weren't, everyone visiting our Web page would get other errors, and that's not what's happening. Anything else I can show or tell, glad to. This is becoming more and more important as our services are expanding and everybody wants a secure connection because they're all listening with browsers. From fredg at paravelsystems.com Fri Feb 3 14:51:45 2023 From: fredg at paravelsystems.com (Fred Gleason) Date: Fri, 3 Feb 2023 09:51:45 -0500 Subject: [Icecast] "Ghost" connections causing connection limit to be reached In-Reply-To: <20230203095743.494A28139A@smtp1.osuosl.org> References: <20230203095743.494A28139A@smtp1.osuosl.org> Message-ID: <881A4129-42D8-4283-A449-7B6C92AB553D@paravelsystems.com> On Feb 3, 2023, at 04:50, Tony Harding wrote: > Not that I am advocating for Shoutcast, but it does have two features that would be useful, A ban list, and a maximum duration setting. No one listens for more than 24 hours. Human beings certainly don?t, but the use cases for Icecast are much wider than merely streaming to individual listeners. E.g. broadcast studio-to-transmitter links, where multiple-month long session durations are absolutely typical. Cheers! |---------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |---------------------------------------------------------------------| | "You see, wire telegraph is a kind of very, very long cat. You | | pull his tail in New York and his head is meowing in Los Angeles. | | Do you understand this? And radio operates exactly the same way: | | you send signals here, they receive them there. The only difference | | is that there is no cat." | | | | -- Albert Einstein, upon being asked to describe radio | |---------------------------------------------------------------------| -------------- next part -------------- An HTML attachment was scrubbed... URL: From uktony at radiocompany.net Fri Feb 3 18:52:49 2023 From: uktony at radiocompany.net (Tony Harding) Date: Sat, 4 Feb 2023 02:52:49 +0800 Subject: [Icecast] "Ghost" connections causing connection limit to be reached In-Reply-To: <881A4129-42D8-4283-A449-7B6C92AB553D@paravelsystems.com> Message-ID: <20230203185258.60FB961306@smtp3.osuosl.org> True but you can set to Zero ? _____ From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Fred Gleason Sent: Friday, February 3, 2023 10:52 PM To: Icecast streaming server user discussions Subject: Re: [Icecast] "Ghost" connections causing connection limit to be reached ? On Feb 3, 2023, at 04:50, Tony Harding wrote: ? Not that I am advocating for Shoutcast, but it does have two features that would be useful, A ban list, and a maximum duration setting. No one listens for more than 24 hours. ? Human beings certainly don?t, but the use cases for Icecast are much wider than merely streaming to individual listeners. E.g. broadcast studio-to-transmitter links, where multiple-month long session durations are absolutely typical. ? Cheers! ? ? |---------------------------------------------------------------------| | Frederick F. Gleason, Jr. | ? ? ? ? ? ? Chief Developer ? ? ? ? ? ? | | ? ? ? ? ? ? ? ? ? ? ? ? ? | ? ? ? ? ? ? Paravel Systems ? ? ? ? ? ? | |---------------------------------------------------------------------| | "You see, wire telegraph is a kind of very, very long cat. You ? ? ? | | pull his tail in New York and his head is meowing in Los Angeles. ? | | Do you understand this? And radio operates exactly the same way: ? ? | | you send signals here, they receive them there. The only difference | | is that there is no cat." ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? | | ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? | | ? ? ? ? ? ? -- Albert Einstein, upon being asked to describe radio ? | |---------------------------------------------------------------------| -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhailman at trentradio.ca Fri Feb 3 20:20:24 2023 From: rhailman at trentradio.ca (Rob Hailman) Date: Fri, 3 Feb 2023 15:20:24 -0500 Subject: [Icecast] "Ghost" connections causing connection limit to be reached In-Reply-To: <20230203095743.494A28139A@smtp1.osuosl.org> References: <20230203095743.494A28139A@smtp1.osuosl.org> Message-ID: Interesting, thanks Tony. There are some entries that don't have bot UAs but those of course could be spoofed. It's curious that this is only affecting the ogg streams - bots seemingly are connecting to the mp3 streams but don't get "stuck" like this. Perhaps the bot is "moving on" in a way that Icecast doesn't notice? In the logs I periodically see "Client XXXX ([IP address]) has fallen too far behind, removing" but seemingly only for the mp3 stream - the ogg streams just accumulate bots until the connection limit is reached. It does look like Icecast has both those features - with the and configuration keys. It seems like setting a max duration (even a very generous one like 24 hours) will solve our issue. Thanks, Rob On Fri, Feb 3, 2023 at 4:57 AM Tony Harding wrote: > Bots are a Web Crawler problem. They check a web page and follow all the > links. One is to your stream. They wait for the ?Page? to finish loading, > but as this is a stream, it never finishes loading. They just see data > coming and do not check if it is audio or HTML. > > > > Not that I am advocating for Shoutcast, but it does have two features that > would be useful, A ban list, and a maximum duration setting. No one listens > for more than 24 hours. > > > > Tony > > > ------------------------------ > > *From:* Icecast [mailto:icecast-bounces at xiph.org] *On Behalf Of *Rob > Hailman > *Sent:* Friday, February 3, 2023 6:53 AM > *To:* icecast at xiph.org > *Subject:* [Icecast] "Ghost" connections causing connection limit to be > reached > > > > Hello, > > > > I've been having an issue periodically where our Icecast server (which is > set to a max 200 connections) will reach that limit and start rejecting all > connections, but most of the connections don't seem to be real active > listeners. > > > > We are running icecast 2.4.4, installed via apt on Ubuntu 22.04.1 LTS. > > > > We have four streams - two mp3 and two ogg. It seems like what is > happening is that connections to the ogg streams are never getting released > - so the number of clients will go up and up until all 200 connections are > taken up. An excerpt from error.log, showing the mp3 stream count > fluctuating but the .ogg count only increasing: > > > > [2023-01-29 10:25:46] INFO source/source_main listener count on /hi-fi > now 6 > [2023-01-29 10:25:47] INFO source/source_main listener count on /hi-fi > now 5 > [2023-01-29 10:25:47] INFO source/source_main listener count on > /hi-fi.ogg now 124 > [2023-01-29 10:25:51] INFO source/source_main listener count on /hi-fi > now 4 > [2023-01-29 10:26:17] INFO source/source_main listener count on > /hi-fi.ogg now 125 > [2023-01-29 10:26:47] INFO source/source_main listener count on > /hi-fi.ogg now 126 > > > > When I restart icecast, the logs will show all 200 connections being > released - and in access.log, most of the .ogg connections will be for very > long durations with very small amounts of data transferred - for example: > > > > 77.88.9.3 - - [02/Feb/2023:21:40:29 +0000] "GET /hi-fi.ogg HTTP/1.1" 200 > 422 "-" "Mozilla/5.0 (compatible; YandexBot/3.0; +http://yandex.com/bots)" > 2694965 > > > > If I'm reading that correctly, the connection was open for 31 days with > 422 bytes transferred. > > > > Many (but not all) of these connections seem to be bots. > > > > Would be happy to provide the full log files but didn't want to send >1MB > files to the whole list. > > > > Is this a possible configuration issue, an Icecast bug, or something else? > Any help or suggestions would be greatly appreciated! > > > > Thanks, > > Rob > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yahav.shasha at gmail.com Fri Feb 3 20:25:56 2023 From: yahav.shasha at gmail.com (Yahav Shasha) Date: Fri, 3 Feb 2023 22:25:56 +0200 Subject: [Icecast] "Ghost" connections causing connection limit to be reached In-Reply-To: References: <20230203095743.494A28139A@smtp1.osuosl.org> Message-ID: You could quite simply use the url auth listener_add hook to reject those bots based on the useragent. ?????? ??? ??, 3 ????? 2023, 22:20, ??? Rob Hailman ?: > Interesting, thanks Tony. > > There are some entries that don't have bot UAs but those of course could > be spoofed. > > It's curious that this is only affecting the ogg streams - bots seemingly > are connecting to the mp3 streams but don't get "stuck" like this. Perhaps > the bot is "moving on" in a way that Icecast doesn't notice? In the logs I > periodically see "Client XXXX ([IP address]) has fallen too far behind, > removing" but seemingly only for the mp3 stream - the ogg streams just > accumulate bots until the connection limit is reached. > > It does look like Icecast has both those features - with the > and configuration keys. It seems like > setting a max duration (even a very generous one like 24 hours) will solve > our issue. > > Thanks, > Rob > > On Fri, Feb 3, 2023 at 4:57 AM Tony Harding > wrote: > >> Bots are a Web Crawler problem. They check a web page and follow all the >> links. One is to your stream. They wait for the ?Page? to finish loading, >> but as this is a stream, it never finishes loading. They just see data >> coming and do not check if it is audio or HTML. >> >> >> >> Not that I am advocating for Shoutcast, but it does have two features >> that would be useful, A ban list, and a maximum duration setting. No one >> listens for more than 24 hours. >> >> >> >> Tony >> >> >> ------------------------------ >> >> *From:* Icecast [mailto:icecast-bounces at xiph.org] *On Behalf Of *Rob >> Hailman >> *Sent:* Friday, February 3, 2023 6:53 AM >> *To:* icecast at xiph.org >> *Subject:* [Icecast] "Ghost" connections causing connection limit to be >> reached >> >> >> >> Hello, >> >> >> >> I've been having an issue periodically where our Icecast server (which is >> set to a max 200 connections) will reach that limit and start rejecting all >> connections, but most of the connections don't seem to be real active >> listeners. >> >> >> >> We are running icecast 2.4.4, installed via apt on Ubuntu 22.04.1 LTS. >> >> >> >> We have four streams - two mp3 and two ogg. It seems like what is >> happening is that connections to the ogg streams are never getting released >> - so the number of clients will go up and up until all 200 connections are >> taken up. An excerpt from error.log, showing the mp3 stream count >> fluctuating but the .ogg count only increasing: >> >> >> >> [2023-01-29 10:25:46] INFO source/source_main listener count on /hi-fi >> now 6 >> [2023-01-29 10:25:47] INFO source/source_main listener count on /hi-fi >> now 5 >> [2023-01-29 10:25:47] INFO source/source_main listener count on >> /hi-fi.ogg now 124 >> [2023-01-29 10:25:51] INFO source/source_main listener count on /hi-fi >> now 4 >> [2023-01-29 10:26:17] INFO source/source_main listener count on >> /hi-fi.ogg now 125 >> [2023-01-29 10:26:47] INFO source/source_main listener count on >> /hi-fi.ogg now 126 >> >> >> >> When I restart icecast, the logs will show all 200 connections being >> released - and in access.log, most of the .ogg connections will be for very >> long durations with very small amounts of data transferred - for example: >> >> >> >> 77.88.9.3 - - [02/Feb/2023:21:40:29 +0000] "GET /hi-fi.ogg HTTP/1.1" 200 >> 422 "-" "Mozilla/5.0 (compatible; YandexBot/3.0; +http://yandex.com/bots)" >> 2694965 >> >> >> >> If I'm reading that correctly, the connection was open for 31 days with >> 422 bytes transferred. >> >> >> >> Many (but not all) of these connections seem to be bots. >> >> >> >> Would be happy to provide the full log files but didn't want to send >1MB >> files to the whole list. >> >> >> >> Is this a possible configuration issue, an Icecast bug, or something >> else? Any help or suggestions would be greatly appreciated! >> >> >> >> Thanks, >> >> Rob >> _______________________________________________ >> 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: From ross at stationplaylist.com Fri Feb 3 23:58:39 2023 From: ross at stationplaylist.com (Ross Levis) Date: Sat, 4 Feb 2023 12:58:39 +1300 Subject: [Icecast] "Ghost" connections causing connection limit to be reached In-Reply-To: <881A4129-42D8-4283-A449-7B6C92AB553D@paravelsystems.com> References: <20230203095743.494A28139A@smtp1.osuosl.org> <881A4129-42D8-4283-A449-7B6C92AB553D@paravelsystems.com> Message-ID: <00b001d9382b$7172abf0$545803d0$@com> The KH edition of Icecast has had those features for several years. /* 43200 ./deny.txt From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Fred Gleason Sent: Saturday, 4 February 2023 3:52 am To: Icecast streaming server user discussions Subject: Re: [Icecast] "Ghost" connections causing connection limit to be reached On Feb 3, 2023, at 04:50, Tony Harding wrote: Not that I am advocating for Shoutcast, but it does have two features that would be useful, A ban list, and a maximum duration setting. No one listens for more than 24 hours. Human beings certainly don?t, but the use cases for Icecast are much wider than merely streaming to individual listeners. E.g. broadcast studio-to-transmitter links, where multiple-month long session durations are absolutely typical. Cheers! |---------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |---------------------------------------------------------------------| | "You see, wire telegraph is a kind of very, very long cat. You | | pull his tail in New York and his head is meowing in Los Angeles. | | Do you understand this? And radio operates exactly the same way: | | you send signals here, they receive them there. The only difference | | is that there is no cat." | | | | -- Albert Einstein, upon being asked to describe radio | |---------------------------------------------------------------------| -------------- next part -------------- An HTML attachment was scrubbed... URL: From sm at noisynotes.com Sat Feb 4 14:25:39 2023 From: sm at noisynotes.com (Steve Matzura) Date: Sat, 4 Feb 2023 09:25:39 -0500 Subject: [Icecast] "Ghost" connections causing connection limit to be reached In-Reply-To: <00b001d9382b$7172abf0$545803d0$@com> References: <20230203095743.494A28139A@smtp1.osuosl.org> <881A4129-42D8-4283-A449-7B6C92AB553D@paravelsystems.com> <00b001d9382b$7172abf0$545803d0$@com> Message-ID: <051bad11-1a1e-6cc5-0b31-a3e690b23b45@noisynotes.com> If there's a max-listener-duration on a mountpoiunt, would it affect services like TuneIn when that duration is reached, or do these services connect one stream per user? On 2/3/2023 6:58 PM, Ross Levis wrote: > > The KH edition of Icecast has had those features for several years. > > > > > > /* > > 43200 > > > > > ./deny.txt > > > > > > *From:*Icecast [mailto:icecast-bounces at xiph.org] *On Behalf Of *Fred > Gleason *Sent:* Saturday, 4 February 2023 3:52 am *To:* Icecast > streaming server user discussions *Subject:* Re: [Icecast] "Ghost" > connections causing connection limit to be reached > > > > On Feb 3, 2023, at 04:50, Tony Harding > wrote: > > > > Not that I am advocating for Shoutcast, but it does have two features > that would be useful, A ban list, and a maximum duration setting. No > one listens for more than 24 hours. > > > > Human beings certainly don?t, but the use cases for Icecast are much > wider than merely streaming to individual listeners. E.g. broadcast > studio-to-transmitter links, where multiple-month long session > durations are absolutely typical. > > > > Cheers! > > > > > > |---------------------------------------------------------------------| > > > | Frederick F. Gleason, Jr. |???????????? Chief Developer???????????? | > > | | Paravel Systems > | > > |---------------------------------------------------------------------| > > > | "You see, wire telegraph is a kind of very, very long cat. You????? | > > | pull his tail in New York and his head is meowing in Los Angeles. > | > > | Do you understand this? And radio operates exactly the same way: > | > > | you send signals here, they receive them there. The only difference > | > > | is that there is no cat." > | -------------- next part -------------- An HTML attachment was scrubbed... URL: From webmaster at berean-biblechurch.org Sat Feb 4 20:58:35 2023 From: webmaster at berean-biblechurch.org (webmaster at berean-biblechurch.org) Date: Sat, 04 Feb 2023 14:58:35 -0600 Subject: [Icecast] Still struggling with secure connection to server In-Reply-To: References: Message-ID: <561ae8c9e7af870c489402099aa0cb75@berean-biblechurch.org> You are testing from outside of the network the server is on? You are using PEM-formatted certs? You have a build (Linux or Windows) that has SSL support integrated in it? On 2023-02-03 05:46, Steve Matzura wrote: > I have made some progress though. > > > According to the documentation for SSL-secured connections: > > > ssl-certificate > If specified, this points to the location of a file that contains both > the X.509 private and public key. This is required for HTTPS support > to be enabled. > > I created the required file by concatenating our public and private > keys. However, when I connect to the port using a browser, I get the > PR_END_OF_FILE_ERROR code, and the message: > > > ? The page you are trying to view cannot be shown because the > authenticity of the received data could not be verified. > ? Please contact the website owners to inform them of this problem. > > The keys are valid. If they weren't, everyone visiting our Web page > would get other errors, and that's not what's happening. > > > Anything else I can show or tell, glad to. This is becoming more and > more important as our services are expanding and everybody wants a > secure connection because they're all listening with browsers. > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From ross at stationplaylist.com Sat Feb 4 22:01:20 2023 From: ross at stationplaylist.com (Ross Levis) Date: Sun, 5 Feb 2023 11:01:20 +1300 Subject: [Icecast] "Ghost" connections causing connection limit to be reached In-Reply-To: <051bad11-1a1e-6cc5-0b31-a3e690b23b45@noisynotes.com> References: <20230203095743.494A28139A@smtp1.osuosl.org> <881A4129-42D8-4283-A449-7B6C92AB553D@paravelsystems.com> <00b001d9382b$7172abf0$545803d0$@com> <051bad11-1a1e-6cc5-0b31-a3e690b23b45@noisynotes.com> Message-ID: <005e01d938e4$383b2740$a8b175c0$@com> TuneIn connect listeners just like any other listeners, one per listener. From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Steve Matzura Sent: Sunday, 5 February 2023 3:26 am To: icecast at xiph.org Subject: Re: [Icecast] "Ghost" connections causing connection limit to be reached If there's a max-listener-duration on a mountpoiunt, would it affect services like TuneIn when that duration is reached, or do these services connect one stream per user? On 2/3/2023 6:58 PM, Ross Levis wrote: > > The KH edition of Icecast has had those features for several years. > > > > > > /* > > 43200 > > > > > ./deny.txt > > > > > > *From:*Icecast [mailto:icecast-bounces at xiph.org] *On Behalf Of *Fred > Gleason *Sent:* Saturday, 4 February 2023 3:52 am *To:* Icecast > streaming server user discussions *Subject:* Re: [Icecast] "Ghost" > connections causing connection limit to be reached > > > > On Feb 3, 2023, at 04:50, Tony Harding > wrote: > > > > Not that I am advocating for Shoutcast, but it does have two features > that would be useful, A ban list, and a maximum duration setting. No > one listens for more than 24 hours. > > > > Human beings certainly don?t, but the use cases for Icecast are much > wider than merely streaming to individual listeners. E.g. broadcast > studio-to-transmitter links, where multiple-month long session > durations are absolutely typical. > > > > Cheers! > > > > > > |---------------------------------------------------------------------| > > > | Frederick F. Gleason, Jr. | Chief Developer | > > | | Paravel Systems > | > > |---------------------------------------------------------------------| > > > | "You see, wire telegraph is a kind of very, very long cat. You | > > | pull his tail in New York and his head is meowing in Los Angeles. > | > > | Do you understand this? And radio operates exactly the same way: > | > > | you send signals here, they receive them there. The only difference > | > > | is that there is no cat." > | -------------- next part -------------- An HTML attachment was scrubbed... URL: From sm at noisynotes.com Mon Feb 6 03:34:40 2023 From: sm at noisynotes.com (Steve Matzura) Date: Sun, 5 Feb 2023 22:34:40 -0500 Subject: [Icecast] Still Struggling with Secure Connections Message-ID: <2c01c00e-f053-ae43-95a9-bdaae3cc2bd3@noisynotes.com> I made a special pair of keys just for Icecast with this command: $ openssl req -newkey rsa:2048 -new -nodes -x509 -days 3650 -keyout key.pem -out cert.pem I combined the two files like this: $ cat cert.pem key.pem > icecast.pem I placed icecast.pem in /etc/icecast2 and used 'chown icecast2:icecast icecast.pem' to change owner to icecast2:icecast. I also changed its protection to 600 with 'chmod 600 icecast.pem' since it does contain a private key. The listen socket has SSL enabled: 1 I check in icecast.xml: /etc/icecast2/icecast.pem I reloaded the configuration: $ /etc/init.d/icecast2 reload Tested with: https://theglobalvoice.info:8443/broadband Same PR_END_OF_FILE error. I'm stumped. From zer0___ at hotmail.com Mon Feb 6 08:23:54 2023 From: zer0___ at hotmail.com (_zer0_ gravity) Date: Mon, 6 Feb 2023 08:23:54 +0000 Subject: [Icecast] Still Struggling with Secure Connections In-Reply-To: <2c01c00e-f053-ae43-95a9-bdaae3cc2bd3@noisynotes.com> References: <2c01c00e-f053-ae43-95a9-bdaae3cc2bd3@noisynotes.com> Message-ID: Which version of Icecast are you running and from which repo did you install it? I always used the xiph repo: http://download.opensuse.org/repositories/multimedia:/xiph/ as for example on at least older Debian versions the one on the official repos were NOT compiled with ssl support. Cheers, Paul -----Oorspronkelijk bericht----- Van: Icecast Namens Steve Matzura Verzonden: Monday, 6 February 2023 04:35 Aan: Icecast streaming server user discussions Onderwerp: [Icecast] Still Struggling with Secure Connections I made a special pair of keys just for Icecast with this command: $ openssl req -newkey rsa:2048 -new -nodes -x509 -days 3650 -keyout key.pem -out cert.pem I combined the two files like this: $ cat cert.pem key.pem > icecast.pem I placed icecast.pem in /etc/icecast2 and used 'chown icecast2:icecast icecast.pem' to change owner to icecast2:icecast. I also changed its protection to 600 with 'chmod 600 icecast.pem' since it does contain a private key. The listen socket has SSL enabled: 1 I check in icecast.xml: /etc/icecast2/icecast.pem I reloaded the configuration: $ /etc/init.d/icecast2 reload Tested with: https://theglobalvoice.info:8443/broadband Same PR_END_OF_FILE error. I'm stumped. _______________________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast From yahav.shasha at gmail.com Mon Feb 6 08:32:03 2023 From: yahav.shasha at gmail.com (Yahav Shasha) Date: Mon, 6 Feb 2023 10:32:03 +0200 Subject: [Icecast] Still Struggling with Secure Connections In-Reply-To: References: <2c01c00e-f053-ae43-95a9-bdaae3cc2bd3@noisynotes.com> Message-ID: > openssl req -newkey rsa:2048 -new -nodes -x509 -days 3650 -keyout key.pem -out cert.pem This will produce a csr file, not an actual certificate, you use this csr file to generate an actual certificate which you can use with Icecast. If you're interested in ssl certificate just for testing you can generate a self signed cert: https://devopscube.com/create-self-signed-certificates-openssl/ For production you'll need to acquire a certificate from a trusted CA though. On Mon, Feb 6, 2023 at 10:24 AM _zer0_ gravity wrote: > Which version of Icecast are you running and from which repo did you > install it? > I always used the xiph repo: > http://download.opensuse.org/repositories/multimedia:/xiph/ > as for example on at least older Debian versions the one on the official > repos were NOT compiled with ssl support. > > Cheers, Paul > > -----Oorspronkelijk bericht----- > Van: Icecast Namens Steve Matzura > Verzonden: Monday, 6 February 2023 04:35 > Aan: Icecast streaming server user discussions > Onderwerp: [Icecast] Still Struggling with Secure Connections > > I made a special pair of keys just for Icecast with this command: > > $ openssl req -newkey rsa:2048 -new -nodes -x509 -days 3650 -keyout > key.pem -out cert.pem > > I combined the two files like this: > > $ cat cert.pem key.pem > icecast.pem > > I placed icecast.pem in /etc/icecast2 and used 'chown icecast2:icecast > icecast.pem' to change owner to icecast2:icecast. > > I also changed its protection to 600 with 'chmod 600 icecast.pem' since it > does contain a private key. > > > The listen socket has SSL enabled: > > > 1 > > > I check in icecast.xml: > > /etc/icecast2/icecast.pem > > I reloaded the configuration: > > $ /etc/init.d/icecast2 reload > > Tested with: > > https://theglobalvoice.info:8443/broadband > > > Same PR_END_OF_FILE error. > > > I'm stumped. > _______________________________________________ > 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 > -- Yahav Shasha, Web Developer +972-(0)549214421 http://www.linkedin.com/in/yahavs -------------- next part -------------- An HTML attachment was scrubbed... URL: From yahav.shasha at gmail.com Mon Feb 6 08:33:40 2023 From: yahav.shasha at gmail.com (Yahav Shasha) Date: Mon, 6 Feb 2023 10:33:40 +0200 Subject: [Icecast] Still Struggling with Secure Connections In-Reply-To: References: <2c01c00e-f053-ae43-95a9-bdaae3cc2bd3@noisynotes.com> Message-ID: Wait, my bad. I missed the - x509 arg.. On Mon, Feb 6, 2023 at 10:32 AM Yahav Shasha wrote: > > openssl req -newkey rsa:2048 -new -nodes -x509 -days 3650 -keyout > key.pem -out cert.pem > This will produce a csr file, not an actual certificate, you use this csr > file to generate an actual certificate which you can use with Icecast. > If you're interested in ssl certificate just for testing you can generate > a self signed cert: > https://devopscube.com/create-self-signed-certificates-openssl/ > For production you'll need to acquire a certificate from a trusted CA > though. > > > > On Mon, Feb 6, 2023 at 10:24 AM _zer0_ gravity > wrote: > >> Which version of Icecast are you running and from which repo did you >> install it? >> I always used the xiph repo: >> http://download.opensuse.org/repositories/multimedia:/xiph/ >> as for example on at least older Debian versions the one on the official >> repos were NOT compiled with ssl support. >> >> Cheers, Paul >> >> -----Oorspronkelijk bericht----- >> Van: Icecast Namens Steve Matzura >> Verzonden: Monday, 6 February 2023 04:35 >> Aan: Icecast streaming server user discussions >> Onderwerp: [Icecast] Still Struggling with Secure Connections >> >> I made a special pair of keys just for Icecast with this command: >> >> $ openssl req -newkey rsa:2048 -new -nodes -x509 -days 3650 -keyout >> key.pem -out cert.pem >> >> I combined the two files like this: >> >> $ cat cert.pem key.pem > icecast.pem >> >> I placed icecast.pem in /etc/icecast2 and used 'chown icecast2:icecast >> icecast.pem' to change owner to icecast2:icecast. >> >> I also changed its protection to 600 with 'chmod 600 icecast.pem' since >> it does contain a private key. >> >> >> The listen socket has SSL enabled: >> >> >> 1 >> >> >> I check in icecast.xml: >> >> /etc/icecast2/icecast.pem >> >> I reloaded the configuration: >> >> $ /etc/init.d/icecast2 reload >> >> Tested with: >> >> https://theglobalvoice.info:8443/broadband >> >> >> Same PR_END_OF_FILE error. >> >> >> I'm stumped. >> _______________________________________________ >> 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 >> > > > -- > Yahav Shasha, > Web Developer > +972-(0)549214421 > http://www.linkedin.com/in/yahavs > -- Yahav Shasha, Web Developer +972-(0)549214421 http://www.linkedin.com/in/yahavs -------------- next part -------------- An HTML attachment was scrubbed... URL: From webmaster at berean-biblechurch.org Tue Feb 7 00:38:56 2023 From: webmaster at berean-biblechurch.org (webmaster at berean-biblechurch.org) Date: Mon, 06 Feb 2023 18:38:56 -0600 Subject: [Icecast] Still Struggling with Secure Connections In-Reply-To: <2c01c00e-f053-ae43-95a9-bdaae3cc2bd3@noisynotes.com> References: <2c01c00e-f053-ae43-95a9-bdaae3cc2bd3@noisynotes.com> Message-ID: <5e67f6118d6df65e26c5d092769e4505@berean-biblechurch.org> Remove the ":8443" and it works. On 2023-02-05 21:34, Steve Matzura wrote: > I made a special pair of keys just for Icecast with this command: > > $ openssl req -newkey rsa:2048 -new -nodes -x509 -days 3650 -keyout > key.pem -out cert.pem > > I combined the two files like this: > > $ cat cert.pem key.pem > icecast.pem > > I placed icecast.pem in /etc/icecast2 and used 'chown icecast2:icecast > icecast.pem' to change owner to icecast2:icecast. > > I also changed its protection to 600 with 'chmod 600 icecast.pem' > since it does contain a private key. > > > The listen socket has SSL enabled: > > > 1 > > > I check in icecast.xml: > > /etc/icecast2/icecast.pem > > I reloaded the configuration: > > $ /etc/init.d/icecast2 reload > > Tested with: > > https://theglobalvoice.info:8443/broadband > > > Same PR_END_OF_FILE error. > > > I'm stumped. > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From googe at googe.tv Sun Feb 12 00:32:19 2023 From: googe at googe.tv (Googe) Date: Sat, 11 Feb 2023 16:32:19 -0800 Subject: [Icecast] Icecast 2.5 beta3 web interface GUI - showing Version issue Message-ID: <86d95a85-f4b2-360b-930f-d0634bf7cbd0@googe.tv> When testing Icecast 2.5 beta3 version, web interface (GUI), after clicking on Administration then click Version - I get this error (Could not parse XSLT file Error code: f86b5b28-c1f8-49f6-a4cd-a18e2a6a44fd). But, if I don't click on Administration, and I just click on Version (in the Public Area GUI) it all works fine and no error. It's a bit tricky to explain, but basically: ? when using:? HTTP://IP:PORT/admin/version.xsl -? I get an error ? when using:? HTTP://IP:PORT/server_version.xsl - I have no error and the web page displays correctly Is this a configuration issue, is there anyway to get help troubleshooting this? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: From googe at googe.tv Sun Feb 12 01:19:11 2023 From: googe at googe.tv (Googe) Date: Sat, 11 Feb 2023 17:19:11 -0800 Subject: [Icecast] Icecast 2.5 beta3 web interface GUI - showing Version issue In-Reply-To: <86d95a85-f4b2-360b-930f-d0634bf7cbd0@googe.tv> References: <86d95a85-f4b2-360b-930f-d0634bf7cbd0@googe.tv> Message-ID: <1ab553b7-44ea-1be0-5029-43e043948ba2@googe.tv> Solved. never mind... I found this: https://gitlab.xiph.org/xiph/icecast-server/-/blob/master/admin/version.xsl I put it in my Admin folder, and everything works now... On 2/11/23 4:32 PM, Googe wrote: > > When testing Icecast 2.5 beta3 version, web interface (GUI), after > clicking on Administration then click Version - > > I get this error (Could not parse XSLT file Error code: > f86b5b28-c1f8-49f6-a4cd-a18e2a6a44fd). > > But, if I don't click on Administration, and I just click on Version > (in the Public Area GUI) it all works fine and no error. > > It's a bit tricky to explain, but basically: > > ? when using:? HTTP://IP:PORT/admin/version.xsl -? I get an error > > ? when using:? HTTP://IP:PORT/server_version.xsl - I have no error and > the web page displays correctly > > Is this a configuration issue, is there anyway to get help > troubleshooting this? > > Thanks! > > > > > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From hgalt at gmx.net Mon Feb 13 13:53:37 2023 From: hgalt at gmx.net (HGAlt) Date: Mon, 13 Feb 2023 14:53:37 +0100 Subject: [Icecast] Send admin kill request to server Message-ID: <000901d93fb2$932b7e50$b9827af0$@gmx.net> Hi, I have a strange problem, which I don't understand! I create a URL like: https:// .:8000/admin/killclient.xsl?user=admin&pass=password&mount=/mount.mpeg&id=12 3456 If I send this URL via a browser to the Icecast server, it works fine! But if I send the same URL via JQUERY AJAX, it failed, because "Authentication Required". But the user and the password is included. The browser and the PHP JQuery is running on the same physical Windows server. Was somebody else already run into the same problem? Thanks, HGA -- Diese E-Mail wurde von Avast-Antivirussoftware auf Viren gepr?ft. www.avast.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From phschafft at de.loewenfelsen.net Mon Feb 13 14:12:14 2023 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Mon, 13 Feb 2023 14:12:14 +0000 Subject: [Icecast] Send admin kill request to server In-Reply-To: <000901d93fb2$932b7e50$b9827af0$@gmx.net> References: <000901d93fb2$932b7e50$b9827af0$@gmx.net> Message-ID: Good morning, On Mon, 2023-02-13 at 14:53 +0100, HGAlt wrote: > Hi, > > I have a strange problem, which I don?t understand! > I create a URL like: > > https://?:8000/admin/killclient.xsl?user=admin&pass=password&mount=/mount.mpeg&id=123456 This doesn't look like a valid API endpoint and parameters. endpoints under /admin that end with ".xsl" are for users only, not for machine made requests. Remove the ".xsl" to do an API call. Also there is no "user" or "pass" parameter. > If I send this URL via a browser to the Icecast server, it works > fine! But if I send the same URL via JQUERY AJAX, it failed, because > ?Authentication Required?. But the user and the password is included. Likely the browser sends the required credentials via HTTP auth as required. It may do so without telling you when it has them cached. > The browser and the PHP JQuery is running on the same physical > Windows server. > > Was somebody else already run into the same problem? I just confirmed here with current devel build, the following works fine for me: wget -SO /dev/null --user=admin --password=hackme --post-data='mount=/example1.ogg&id=44' http://localhost:8000/admin/killclient With best regards, -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From hgalt at gmx.net Mon Feb 13 18:29:47 2023 From: hgalt at gmx.net (HGAlt) Date: Mon, 13 Feb 2023 19:29:47 +0100 Subject: [Icecast] Send admin kill request to server In-Reply-To: References: <000901d93fb2$932b7e50$b9827af0$@gmx.net> Message-ID: <002701d93fd9$2778edb0$766ac910$@gmx.net> Hi Philipp, I have tested it. But I still get the message back ?Authentication Required". As I mentioned before, send this request from the same server, where Icecast is running. But the audio is provided from another server. Could be that a problem? Thanks, HGA -----Urspr?ngliche Nachricht----- Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Philipp Schafft Gesendet: Montag, 13. Februar 2023 15:12 An: Icecast streaming server user discussions Betreff: Re: [Icecast] Send admin kill request to server Good morning, On Mon, 2023-02-13 at 14:53 +0100, HGAlt wrote: > Hi, > > I have a strange problem, which I don?t understand! > I create a URL like: > > https://?:8000/admin/killclient.xsl?user=admin&pass=password&mount=/mo > unt.mpeg&id=123456 This doesn't look like a valid API endpoint and parameters. endpoints under /admin that end with ".xsl" are for users only, not for machine made requests. Remove the ".xsl" to do an API call. Also there is no "user" or "pass" parameter. > If I send this URL via a browser to the Icecast server, it works fine! > But if I send the same URL via JQUERY AJAX, it failed, because > ?Authentication Required?. But the user and the password is included. Likely the browser sends the required credentials via HTTP auth as required. It may do so without telling you when it has them cached. > The browser and the PHP JQuery is running on the same physical Windows > server. > > Was somebody else already run into the same problem? I just confirmed here with current devel build, the following works fine for me: wget -SO /dev/null --user=admin --password=hackme --post-data='mount=/example1.ogg&id=44' http://localhost:8000/admin/killclient With best regards, -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -- Diese E-Mail wurde von Avast-Antivirussoftware auf Viren gepr?ft. www.avast.com From phschafft at de.loewenfelsen.net Mon Feb 13 23:15:20 2023 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Mon, 13 Feb 2023 23:15:20 +0000 Subject: [Icecast] Send admin kill request to server In-Reply-To: <002701d93fd9$2778edb0$766ac910$@gmx.net> References: <000901d93fb2$932b7e50$b9827af0$@gmx.net> <002701d93fd9$2778edb0$766ac910$@gmx.net> Message-ID: Good afternoon, On Mon, 2023-02-13 at 19:29 +0100, HGAlt wrote: > Hi Philipp, > > I have tested it. But I still get the message back ?Authentication > Required". > As I mentioned before, send this request from the same server, where > Icecast is running. > But the audio is provided from another server. > Could be that a problem? No, not really. This strongly sounds like the credentials are in fact not provided. both access.log and error.log might have details. Also you could have a look at the actual traffic flow. At this point I don't think there is much to add without knowing your config and the code you use to access the API. I still strongly guess that you just don't provide the credentials in a way they are actually used. Which is most likely a problem with your code, not the API or Icecast. With best regards, > -----Urspr?ngliche Nachricht----- > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Philipp > Schafft > Gesendet: Montag, 13. Februar 2023 15:12 > An: Icecast streaming server user discussions > Betreff: Re: [Icecast] Send admin kill request to server > > Good morning, > > On Mon, 2023-02-13 at 14:53 +0100, HGAlt wrote: > > Hi, > > > > I have a strange problem, which I don?t understand! > > I create a URL like: > > > > https://?:8000/admin/killclient.xsl?user=admin&pass=password&mount=/mo > > unt.mpeg&id=123456 > > This doesn't look like a valid API endpoint and parameters. > > endpoints under /admin that end with ".xsl" are for users only, not > for machine made requests. Remove the ".xsl" to do an API call. > > Also there is no "user" or "pass" parameter. > > > If I send this URL via a browser to the Icecast server, it works > > fine! > > But if I send the same URL via JQUERY AJAX, it failed, because > > ?Authentication Required?. But the user and the password is > > included. > > Likely the browser sends the required credentials via HTTP auth as > required. It may do so without telling you when it has them cached. > > > > The browser and the PHP JQuery is running on the same physical > > Windows > > server. > > > > Was somebody else already run into the same problem? > > I just confirmed here with current devel build, the following works > fine for me: > > wget -SO /dev/null --user=admin --password=hackme --post- > data='mount=/example1.ogg&id=44' > http://localhost:8000/admin/killclient > -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From hgalt at gmx.net Tue Feb 14 11:47:16 2023 From: hgalt at gmx.net (HGAlt) Date: Tue, 14 Feb 2023 12:47:16 +0100 Subject: [Icecast] Send admin kill request to server In-Reply-To: References: <000901d93fb2$932b7e50$b9827af0$@gmx.net> <002701d93fd9$2778edb0$766ac910$@gmx.net> Message-ID: <000c01d9406a$16a910f0$43fb32d0$@gmx.net> Good morning Philipp, in the log files I couldn't find anything, but the level is only set to 3. I set it now to 4, but a restart is require first. How can I set the credentials? If I use is the server than only listen to this IP? Can I have 2 bind-addresses for one port? Where can I find additional information about setting the credentials? Can I provide you my configuration directly? Thanks for your support, HGA -----Urspr?ngliche Nachricht----- Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Philipp Schafft Gesendet: Dienstag, 14. Februar 2023 00:15 An: Icecast streaming server user discussions Betreff: Re: [Icecast] Send admin kill request to server Good afternoon, On Mon, 2023-02-13 at 19:29 +0100, HGAlt wrote: > Hi Philipp, > > I have tested it. But I still get the message back ?Authentication > Required". > As I mentioned before, send this request from the same server, where > Icecast is running. > But the audio is provided from another server. > Could be that a problem? No, not really. This strongly sounds like the credentials are in fact not provided. both access.log and error.log might have details. Also you could have a look at the actual traffic flow. At this point I don't think there is much to add without knowing your config and the code you use to access the API. I still strongly guess that you just don't provide the credentials in a way they are actually used. Which is most likely a problem with your code, not the API or Icecast. With best regards, > -----Urspr?ngliche Nachricht----- > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Philipp > Schafft > Gesendet: Montag, 13. Februar 2023 15:12 > An: Icecast streaming server user discussions > Betreff: Re: [Icecast] Send admin kill request to server > > Good morning, > > On Mon, 2023-02-13 at 14:53 +0100, HGAlt wrote: > > Hi, > > > > I have a strange problem, which I don?t understand! > > I create a URL like: > > > > https://?:8000/admin/killclient.xsl?user=admin&pass=password&mount=/ > > mo > > unt.mpeg&id=123456 > > This doesn't look like a valid API endpoint and parameters. > > endpoints under /admin that end with ".xsl" are for users only, not > for machine made requests. Remove the ".xsl" to do an API call. > > Also there is no "user" or "pass" parameter. > > > If I send this URL via a browser to the Icecast server, it works > > fine! > > But if I send the same URL via JQUERY AJAX, it failed, because > > ?Authentication Required?. But the user and the password is > > included. > > Likely the browser sends the required credentials via HTTP auth as > required. It may do so without telling you when it has them cached. > > > > The browser and the PHP JQuery is running on the same physical > > Windows server. > > > > Was somebody else already run into the same problem? > > I just confirmed here with current devel build, the following works > fine for me: > > wget -SO /dev/null --user=admin --password=hackme --post- > data='mount=/example1.ogg&id=44' > http://localhost:8000/admin/killclient > -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -- Diese E-Mail wurde von Avast-Antivirussoftware auf Viren gepr?ft. www.avast.com From phschafft at de.loewenfelsen.net Tue Feb 14 16:25:02 2023 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Tue, 14 Feb 2023 16:25:02 +0000 Subject: [Icecast] Send admin kill request to server In-Reply-To: <000c01d9406a$16a910f0$43fb32d0$@gmx.net> References: <000901d93fb2$932b7e50$b9827af0$@gmx.net> <002701d93fd9$2778edb0$766ac910$@gmx.net> <000c01d9406a$16a910f0$43fb32d0$@gmx.net> Message-ID: <0f0f5876bda87e81136be59bc73aa0c909bed7cd.camel@de.loewenfelsen.net> Good morning, On Tue, 2023-02-14 at 12:47 +0100, HGAlt wrote: > Good morning Philipp, > > in the log files I couldn't find anything, but the level is only set > to 3. I set it now to 4, but a restart is require first. the access log should always have an entry. If it doesn't something is wrong. In the good case the first request is rejected (with a 401), and then the client will do all other requests authed (mostly 2xx status codes). > How can I set the credentials? That depends on the client you use. Without knowing that nobody can answer that. It should be in the documentation of the software you use to make the request. > If I use is the server than only listen to this IP? > Can I have 2 bind-addresses for one port? This has nothing to do with the listen sockets. > Where can I find additional information about setting the > credentials? In the documentation of the software you use to make the API request. > Can I provide you my configuration directly? I don't think this is in any way related to Icecast's config at this point. With best regards, > -----Urspr?ngliche Nachricht----- > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Philipp > Schafft > Gesendet: Dienstag, 14. Februar 2023 00:15 > An: Icecast streaming server user discussions > Betreff: Re: [Icecast] Send admin kill request to server > > Good afternoon, > > On Mon, 2023-02-13 at 19:29 +0100, HGAlt wrote: > > Hi Philipp, > > > > I have tested it. But I still get the message back ?Authentication > > Required". > > As I mentioned before, send this request from the same server, > > where > > Icecast is running. > > But the audio is provided from another server. > > Could be that a problem? > > No, not really. This strongly sounds like the credentials are in fact > not provided. both access.log and error.log might have details. Also > you could have a look at the actual traffic flow. > > At this point I don't think there is much to add without knowing your > config and the code you use to access the API. I still strongly guess > that you just don't provide the credentials in a way they are > actually used. Which is most likely a problem with your code, not the > API or Icecast. > > With best regards, > > > > > -----Urspr?ngliche Nachricht----- > > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von > > Philipp > > Schafft > > Gesendet: Montag, 13. Februar 2023 15:12 > > An: Icecast streaming server user discussions > > Betreff: Re: [Icecast] Send admin kill request to server > > > > [...] > > I just confirmed here with current devel build, the following works > > fine for me: > > > > wget -SO /dev/null --user=admin --password=hackme --post- > > data='mount=/example1.ogg&id=44' > > http://localhost:8000/admin/killclient > -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From hgalt at gmx.net Tue Feb 14 18:24:20 2023 From: hgalt at gmx.net (HGAlt) Date: Tue, 14 Feb 2023 19:24:20 +0100 Subject: [Icecast] Send admin kill request to server In-Reply-To: <0f0f5876bda87e81136be59bc73aa0c909bed7cd.camel@de.loewenfelsen.net> References: <000901d93fb2$932b7e50$b9827af0$@gmx.net> <002701d93fd9$2778edb0$766ac910$@gmx.net> <000c01d9406a$16a910f0$43fb32d0$@gmx.net> <0f0f5876bda87e81136be59bc73aa0c909bed7cd.camel@de.loewenfelsen.net> Message-ID: <001d01d940a1$8f023860$ad06a920$@gmx.net> Good afternoon Philipp and everyone, I am a little bit confused! http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21 This is an example of the Icecast documentation for kill a client. And this is a HTTP GET, which is send to the Icecast server. You also wrote, that there are no user and pass for an API. What I have to know, what does the Icecast server expect? If there is no user and pass, how the server knows, that is a valid request. I also figured out, that I got a network error, if I address the server with his full URL, like https://www.server.xy, when I use localhost or the local IP like 10.0.0.x, I got a normal error without any addition description. So I believe, that I first have to understand, what I have to send to the server and how the Icecast server understand, that it has to execute this API! As long it is not clear to me, I don't know what to do. The software is written by myself and therefore I can control it. Kind regards, HGA -----Urspr?ngliche Nachricht----- Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Philipp Schafft Gesendet: Dienstag, 14. Februar 2023 17:25 An: Icecast streaming server user discussions Betreff: Re: [Icecast] Send admin kill request to server Good morning, On Tue, 2023-02-14 at 12:47 +0100, HGAlt wrote: > Good morning Philipp, > > in the log files I couldn't find anything, but the level is only set > to 3. I set it now to 4, but a restart is require first. the access log should always have an entry. If it doesn't something is wrong. In the good case the first request is rejected (with a 401), and then the client will do all other requests authed (mostly 2xx status codes). > How can I set the credentials? That depends on the client you use. Without knowing that nobody can answer that. It should be in the documentation of the software you use to make the request. > If I use is the server than only listen to this IP? > Can I have 2 bind-addresses for one port? This has nothing to do with the listen sockets. > Where can I find additional information about setting the credentials? In the documentation of the software you use to make the API request. > Can I provide you my configuration directly? I don't think this is in any way related to Icecast's config at this point. With best regards, > -----Urspr?ngliche Nachricht----- > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Philipp > Schafft > Gesendet: Dienstag, 14. Februar 2023 00:15 > An: Icecast streaming server user discussions > Betreff: Re: [Icecast] Send admin kill request to server > > Good afternoon, > > On Mon, 2023-02-13 at 19:29 +0100, HGAlt wrote: > > Hi Philipp, > > > > I have tested it. But I still get the message back ?Authentication > > Required". > > As I mentioned before, send this request from the same server, where > > Icecast is running. > > But the audio is provided from another server. > > Could be that a problem? > > No, not really. This strongly sounds like the credentials are in fact > not provided. both access.log and error.log might have details. Also > you could have a look at the actual traffic flow. > > At this point I don't think there is much to add without knowing your > config and the code you use to access the API. I still strongly guess > that you just don't provide the credentials in a way they are actually > used. Which is most likely a problem with your code, not the API or > Icecast. > > With best regards, > > > > > -----Urspr?ngliche Nachricht----- > > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von > > Philipp Schafft > > Gesendet: Montag, 13. Februar 2023 15:12 > > An: Icecast streaming server user discussions > > Betreff: Re: [Icecast] Send admin kill request to server > > > > [...] > > I just confirmed here with current devel build, the following works > > fine for me: > > > > wget -SO /dev/null --user=admin --password=hackme --post- > > data='mount=/example1.ogg&id=44' > > http://localhost:8000/admin/killclient > -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -- Diese E-Mail wurde von Avast-Antivirussoftware auf Viren gepr?ft. www.avast.com From phschafft at de.loewenfelsen.net Tue Feb 14 23:51:49 2023 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Tue, 14 Feb 2023 23:51:49 +0000 Subject: [Icecast] Send admin kill request to server In-Reply-To: <001d01d940a1$8f023860$ad06a920$@gmx.net> References: <000901d93fb2$932b7e50$b9827af0$@gmx.net> <002701d93fd9$2778edb0$766ac910$@gmx.net> <000c01d9406a$16a910f0$43fb32d0$@gmx.net> <0f0f5876bda87e81136be59bc73aa0c909bed7cd.camel@de.loewenfelsen.net> <001d01d940a1$8f023860$ad06a920$@gmx.net> Message-ID: Good afternoon, On Tue, 2023-02-14 at 19:24 +0100, HGAlt wrote: > Good afternoon Philipp and everyone, > > I am a little bit confused! > > http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21 > > This is an example of the Icecast documentation for kill a client. > And this is a HTTP GET, which is send to the Icecast server. > You also wrote, that there are no user and pass for an API. I wrote that there are no such form parameters. > What I have to know, what does the Icecast server expect? > If there is no user and pass, how the server knows, that is a valid > request. There are credentials as per standard HTTP auth. See e.g. here: https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#HTTP_authentication > I also figured out, that I got a network error, if I address the > server with his full URL, like https://www.server.xy, when I use > localhost or the local IP like 10.0.0.x, I got a normal error without > any addition description. That sounds more like a problem with your firewall and/or port forwardings (if any). > So I believe, that I first have to understand, what I have to send to > the server and how the Icecast server understand, that it has to > execute this API! > As long it is not clear to me, I don't know what to do. > The software is written by myself and therefore I can control it. Please see above. With best regards, PS: It would be very kind of you if you would avoid TOFU ( https://en.wikipedia.org/wiki/Top-posting). It makes mails much harder to read. > -----Urspr?ngliche Nachricht----- > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Philipp > Schafft > Gesendet: Dienstag, 14. Februar 2023 17:25 > An: Icecast streaming server user discussions > Betreff: Re: [Icecast] Send admin kill request to server > > Good morning, > > On Tue, 2023-02-14 at 12:47 +0100, HGAlt wrote: > > Good morning Philipp, > > > > in the log files I couldn't find anything, but the level is only > > set > > to 3. I set it now to 4, but a restart is require first. > > the access log should always have an entry. If it doesn't something > is wrong. > > In the good case the first request is rejected (with a 401), and then > the client will do all other requests authed (mostly 2xx status > codes). > > > > How can I set the credentials? > > That depends on the client you use. Without knowing that nobody can > answer that. It should be in the documentation of the software you > use to make the request. > > > > If I use is the server than only listen to this IP? > > Can I have 2 bind-addresses for one port? > > This has nothing to do with the listen sockets. > > > > Where can I find additional information about setting the > > credentials? > > In the documentation of the software you use to make the API request. > > > > Can I provide you my configuration directly? > > I don't think this is in any way related to Icecast's config at this > point. > > > > -----Urspr?ngliche Nachricht----- > > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von > > Philipp > > Schafft > > Gesendet: Dienstag, 14. Februar 2023 00:15 > > An: Icecast streaming server user discussions > > Betreff: Re: [Icecast] Send admin kill request to server > > > > Good afternoon, > > > > On Mon, 2023-02-13 at 19:29 +0100, HGAlt wrote: > > > Hi Philipp, > > > > > > I have tested it. But I still get the message back > > > ?Authentication > > > Required". > > > As I mentioned before, send this request from the same server, > > > where > > > Icecast is running. > > > But the audio is provided from another server. > > > Could be that a problem? > > > > No, not really. This strongly sounds like the credentials are in > > fact > > not provided. both access.log and error.log might have details. > > Also > > you could have a look at the actual traffic flow. > > > > At this point I don't think there is much to add without knowing > > your > > config and the code you use to access the API. I still strongly > > guess > > that you just don't provide the credentials in a way they are > > actually > > used. Which is most likely a problem with your code, not the API or > > Icecast. > > > > With best regards, > > > > > > > > > -----Urspr?ngliche Nachricht----- > > > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von > > > Philipp Schafft > > > Gesendet: Montag, 13. Februar 2023 15:12 > > > An: Icecast streaming server user discussions > > > Betreff: Re: [Icecast] Send admin kill request to server > > > > > > [...] > > > I just confirmed here with current devel build, the following > > > works > > > fine for me: > > > > > > wget -SO /dev/null --user=admin --password=hackme --post- > > > data='mount=/example1.ogg&id=44' > > > http://localhost:8000/admin/killclient > -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephone: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ Gesch?ftsf?hrer/CEO: Philipp Schafft L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From fredg at paravelsystems.com Wed Feb 15 15:57:13 2023 From: fredg at paravelsystems.com (Fred Gleason) Date: Wed, 15 Feb 2023 10:57:13 -0500 Subject: [Icecast] Send admin kill request to server In-Reply-To: <001d01d940a1$8f023860$ad06a920$@gmx.net> References: <000901d93fb2$932b7e50$b9827af0$@gmx.net> <002701d93fd9$2778edb0$766ac910$@gmx.net> <000c01d9406a$16a910f0$43fb32d0$@gmx.net> <0f0f5876bda87e81136be59bc73aa0c909bed7cd.camel@de.loewenfelsen.net> <001d01d940a1$8f023860$ad06a920$@gmx.net> Message-ID: On Feb 14, 2023, at 13:24, HGAlt wrote: > I am a little bit confused! > > http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21 > > This is an example of the Icecast documentation for kill a client. > And this is a HTTP GET, which is send to the Icecast server. > You also wrote, that there are no user and pass for an API. > > What I have to know, what does the Icecast server expect? > If there is no user and pass, how the server knows, that is a valid request. You should be able to send this with proper HTTP authentication parameters by using CURL. Something like: curl -u admin:hackme http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21 This is different from encoding the parameters as if they were part of an HTML form. Cheers! |---------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |---------------------------------------------------------------------| | A room without books is like a body without a soul. | | | | -- Cicero | |---------------------------------------------------------------------| -------------- next part -------------- An HTML attachment was scrubbed... URL: From hgalt at gmx.net Thu Feb 16 14:48:46 2023 From: hgalt at gmx.net (HGAlt) Date: Thu, 16 Feb 2023 15:48:46 +0100 Subject: [Icecast] Send admin kill request to server In-Reply-To: References: <000901d93fb2$932b7e50$b9827af0$@gmx.net> <002701d93fd9$2778edb0$766ac910$@gmx.net> <000c01d9406a$16a910f0$43fb32d0$@gmx.net> <0f0f5876bda87e81136be59bc73aa0c909bed7cd.camel@de.loewenfelsen.net> <001d01d940a1$8f023860$ad06a920$@gmx.net> Message-ID: <000801d94215$c6483e30$52d8ba90$@gmx.net> Hi Fred, I am understand the requirements already a little bit better. What I have to Do is a HTTP GET with a Basic Authorization in the header. I have tested it with 'Postman' and it works fine with Icecast. But I have to do it with Javascript or JQuery. Therefore curl doesn't help me. I try to use Ajax for that, but something goes wrong. If I do it without Autorization, I got a return message which says 'Authentication required'. If I enable the Autorization it tells me only readyState: 0. If I will find a solution, I will post it here. Cheers Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Fred Gleason Gesendet: Mittwoch, 15. Februar 2023 16:57 An: Icecast streaming server user discussions Betreff: Re: [Icecast] Send admin kill request to server On Feb 14, 2023, at 13:24, HGAlt wrote: I am a little bit confused! http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21 This is an example of the Icecast documentation for kill a client. And this is a HTTP GET, which is send to the Icecast server. You also wrote, that there are no user and pass for an API. What I have to know, what does the Icecast server expect? If there is no user and pass, how the server knows, that is a valid request. You should be able to send this with proper HTTP authentication parameters by using CURL. Something like: curl -u admin:hackme http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg &id=21 This is different from encoding the parameters as if they were part of an HTML form. Cheers! |---------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |---------------------------------------------------------------------| | A room without books is like a body without a soul. | | | | -- Cicero | |---------------------------------------------------------------------| -- Diese E-Mail wurde von Avast-Antivirussoftware auf Viren gepr?ft. www.avast.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayaubs89 at gmail.com Thu Feb 16 15:06:09 2023 From: jayaubs89 at gmail.com (Coolvibes Reloaded) Date: Thu, 16 Feb 2023 15:06:09 +0000 Subject: [Icecast] New post Message-ID: How can I start a icecast server With autodj? -------------- next part -------------- An HTML attachment was scrubbed... URL: From informatux at gmail.com Thu Feb 16 15:22:09 2023 From: informatux at gmail.com (Kwame Bahena) Date: Thu, 16 Feb 2023 09:22:09 -0600 Subject: [Icecast] New post In-Reply-To: References: Message-ID: I guess this will help you --> https://github.com/Renaud11232/icecast-autodj On Thu, Feb 16, 2023 at 9:06 AM Coolvibes Reloaded wrote: > How can I start a icecast server > With autodj? > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayaubs89 at gmail.com Thu Feb 16 15:24:33 2023 From: jayaubs89 at gmail.com (Coolvibes Reloaded) Date: Thu, 16 Feb 2023 15:24:33 +0000 Subject: [Icecast] New post In-Reply-To: References: Message-ID: Can this also be done on a win10 platform On Thu, 16 Feb 2023, 15:22 Kwame Bahena, wrote: > I guess this will help you --> > https://github.com/Renaud11232/icecast-autodj > > > On Thu, Feb 16, 2023 at 9:06 AM Coolvibes Reloaded > wrote: > >> How can I start a icecast server >> With autodj? >> _______________________________________________ >> 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: From hgalt at gmx.net Sat Feb 18 12:23:52 2023 From: hgalt at gmx.net (HGAlt) Date: Sat, 18 Feb 2023 13:23:52 +0100 Subject: [Icecast] Send admin kill request to server In-Reply-To: <000801d94215$c6483e30$52d8ba90$@gmx.net> References: <000901d93fb2$932b7e50$b9827af0$@gmx.net> <002701d93fd9$2778edb0$766ac910$@gmx.net> <000c01d9406a$16a910f0$43fb32d0$@gmx.net> <0f0f5876bda87e81136be59bc73aa0c909bed7cd.camel@de.loewenfelsen.net> <001d01d940a1$8f023860$ad06a920$@gmx.net> <000801d94215$c6483e30$52d8ba90$@gmx.net> Message-ID: <000601d94393$dd295fb0$977c1f10$@gmx.net> Hi everybody, finally I found a solution! First, Icecast requires a Basic Authorization, which has to provide via a header. But this can't be done via JavaScript or JQuery, due the security features of the browsers. For more detail information see https://stackoverflow.com/questions/75463305/difference-basic-authorization- between-postman-and-jquery-ajax/75493285#75493285. Thanks for help, HGA Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von HGAlt Gesendet: Donnerstag, 16. Februar 2023 15:49 An: 'Icecast streaming server user discussions' Betreff: Re: [Icecast] Send admin kill request to server Hi Fred, I am understand the requirements already a little bit better. What I have to Do is a HTTP GET with a Basic Authorization in the header. I have tested it with 'Postman' and it works fine with Icecast. But I have to do it with Javascript or JQuery. Therefore curl doesn't help me. I try to use Ajax for that, but something goes wrong. If I do it without Autorization, I got a return message which says 'Authentication required'. If I enable the Autorization it tells me only readyState: 0. If I will find a solution, I will post it here. Cheers Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Fred Gleason Gesendet: Mittwoch, 15. Februar 2023 16:57 An: Icecast streaming server user discussions Betreff: Re: [Icecast] Send admin kill request to server On Feb 14, 2023, at 13:24, HGAlt wrote: I am a little bit confused! http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21 This is an example of the Icecast documentation for kill a client. And this is a HTTP GET, which is send to the Icecast server. You also wrote, that there are no user and pass for an API. What I have to know, what does the Icecast server expect? If there is no user and pass, how the server knows, that is a valid request. You should be able to send this with proper HTTP authentication parameters by using CURL. Something like: curl -u admin:hackme http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg &id=21 This is different from encoding the parameters as if they were part of an HTML form. Cheers! |---------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |---------------------------------------------------------------------| | A room without books is like a body without a soul. | | | | -- Cicero | |---------------------------------------------------------------------| Virenfrei. www.avast.com -- Diese E-Mail wurde von Avast-Antivirussoftware auf Viren gepr?ft. www.avast.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayaubs89 at gmail.com Sat Feb 18 13:46:46 2023 From: jayaubs89 at gmail.com (Coolvibes Reloaded) Date: Sat, 18 Feb 2023 13:46:46 +0000 Subject: [Icecast] new post Message-ID: i messaged you guys the otherday asking how i would setup an icecast server with autodj so someone replied then i replied back asking if i could set it up on windows10? but no one replied back? -------------- next part -------------- An HTML attachment was scrubbed... URL: From phschafft at de.loewenfelsen.net Sat Feb 18 19:53:09 2023 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Sat, 18 Feb 2023 19:53:09 +0000 Subject: [Icecast] Send admin kill request to server In-Reply-To: <000601d94393$dd295fb0$977c1f10$@gmx.net> References: <000901d93fb2$932b7e50$b9827af0$@gmx.net> <002701d93fd9$2778edb0$766ac910$@gmx.net> <000c01d9406a$16a910f0$43fb32d0$@gmx.net> <0f0f5876bda87e81136be59bc73aa0c909bed7cd.camel@de.loewenfelsen.net> <001d01d940a1$8f023860$ad06a920$@gmx.net> <000801d94215$c6483e30$52d8ba90$@gmx.net> <000601d94393$dd295fb0$977c1f10$@gmx.net> Message-ID: <2d81eaab10709d74ff8e0a773c24d21b73cb9e6d.camel@de.loewenfelsen.net> Good afternoon, On Sat, 2023-02-18 at 13:23 +0100, HGAlt wrote: > Hi everybody, > > finally I found a solution! > > First, Icecast requires a Basic Authorization, which has to provide > via a header. This is not fully correct. It depends on the configuration and may change with different versions of the server. An important note here, and to be honest the main reason why I answer: NEVER EVER just append a random Authorization:-header without implementing all of the HTTP authorisation mechanism. If you do so you basically are broadcasting cleartext passwords to random peers, and are likely to get in trouble with changes of software versions or configurations. It is a big no-go. Always use the mechanism as provided by your HTTP implementieren. Please see the relevant standards for a full discussion on how and why this breaks security and interoperability. > But this can?t be done via JavaScript or JQuery, due the security > features of the browsers. > For more detail information see > https://stackoverflow.com/questions/75463305/difference-basic-authorization-between-postman-and-jquery-ajax/75493285#75493285 > . If you adhere to CORS it works fine for me. A simple XHR request with credentials passed via open() worked. Naturally you are bound to CORS. Icecast can announce any kind of CORS settings via it's config. XHR also allows you direct access to the response Icecast gives you as it provides you with the response's DOM. So you can directly check the result. :) With best regards, > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von HGAlt > Gesendet: Donnerstag, 16. Februar 2023 15:49 > An: 'Icecast streaming server user discussions' > Betreff: Re: [Icecast] Send admin kill request to server > > Hi Fred, > > I am understand the requirements already a little bit better. > > What I have to Do is a HTTP GET with a Basic Authorization in the > header. I have tested it with ?Postman? and it works fine with > Icecast. > But I have to do it with Javascript or JQuery. Therefore curl doesn?t > help me. > > I try to use Ajax for that, but something goes wrong. > If I do it without Autorization, I got a return message which says > 'Authentication required'. > If I enable the Autorization it tells me only readyState: 0. > > If I will find a solution, I will post it here. > > Cheers > > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Fred > Gleason > Gesendet: Mittwoch, 15. Februar 2023 16:57 > An: Icecast streaming server user discussions > Betreff: Re: [Icecast] Send admin kill request to server > > On Feb 14, 2023, at 13:24, HGAlt wrote: > > > I am a little bit confused! > > > > http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21 > > > > This is an example of the Icecast documentation for kill a client. > > And this is a HTTP GET, which is send to the Icecast server. > > You also wrote, that there are no user and pass for an API. > > > > What I have to know, what does the Icecast server expect? > > If there is no user and pass, how the server knows, that is a valid > > request. > > > You should be able to send this with proper HTTP authentication > parameters by using CURL. Something like: > > curl -u admin:hackme > http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21 > > This is different from encoding the parameters as if they were part > of an HTML form. > -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephone: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ Gesch?ftsf?hrer/CEO: Philipp Schafft L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From hgalt at gmx.net Fri Feb 24 12:40:35 2023 From: hgalt at gmx.net (HGAlt) Date: Fri, 24 Feb 2023 13:40:35 +0100 Subject: [Icecast] Send admin kill request to server In-Reply-To: <2d81eaab10709d74ff8e0a773c24d21b73cb9e6d.camel@de.loewenfelsen.net> References: <000901d93fb2$932b7e50$b9827af0$@gmx.net> <002701d93fd9$2778edb0$766ac910$@gmx.net> <000c01d9406a$16a910f0$43fb32d0$@gmx.net> <0f0f5876bda87e81136be59bc73aa0c909bed7cd.camel@de.loewenfelsen.net> <001d01d940a1$8f023860$ad06a920$@gmx.net> <000801d94215$c6483e30$52d8ba90$@gmx.net> <000601d94393$dd295fb0$977c1f10$@gmx.net> <2d81eaab10709d74ff8e0a773c24d21b73cb9e6d.camel@de.loewenfelsen.net> Message-ID: <001801d9484d$318c72f0$94a558d0$@gmx.net> Good Morning Philipp, that make be a good point. But it would be very helpful, if in the Icecast documentation would be very clear defined, which kind of authorization is required for which server version. At least, I could not find anything! -----Urspr?ngliche Nachricht----- Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Philipp Schafft Gesendet: Samstag, 18. Februar 2023 20:53 An: Icecast streaming server user discussions Betreff: Re: [Icecast] Send admin kill request to server Good afternoon, On Sat, 2023-02-18 at 13:23 +0100, HGAlt wrote: > Hi everybody, > > finally I found a solution! > > First, Icecast requires a Basic Authorization, which has to provide > via a header. This is not fully correct. It depends on the configuration and may change with different versions of the server. An important note here, and to be honest the main reason why I answer: NEVER EVER just append a random Authorization:-header without implementing all of the HTTP authorisation mechanism. If you do so you basically are broadcasting cleartext passwords to random peers, and are likely to get in trouble with changes of software versions or configurations. It is a big no-go. Always use the mechanism as provided by your HTTP implementieren. Please see the relevant standards for a full discussion on how and why this breaks security and interoperability. > But this can?t be done via JavaScript or JQuery, due the security > features of the browsers. > For more detail information see > https://stackoverflow.com/questions/75463305/difference-basic-authoriz > ation-between-postman-and-jquery-ajax/75493285#75493285 > . If you adhere to CORS it works fine for me. A simple XHR request with credentials passed via open() worked. Naturally you are bound to CORS. Icecast can announce any kind of CORS settings via it's config. XHR also allows you direct access to the response Icecast gives you as it provides you with the response's DOM. So you can directly check the result. :) With best regards, > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von HGAlt > Gesendet: Donnerstag, 16. Februar 2023 15:49 > An: 'Icecast streaming server user discussions' > Betreff: Re: [Icecast] Send admin kill request to server > > Hi Fred, > > I am understand the requirements already a little bit better. > > What I have to Do is a HTTP GET with a Basic Authorization in the > header. I have tested it with ?Postman? and it works fine with > Icecast. > But I have to do it with Javascript or JQuery. Therefore curl doesn?t > help me. > > I try to use Ajax for that, but something goes wrong. > If I do it without Autorization, I got a return message which says > 'Authentication required'. > If I enable the Autorization it tells me only readyState: 0. > > If I will find a solution, I will post it here. > > Cheers > > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Fred > Gleason > Gesendet: Mittwoch, 15. Februar 2023 16:57 > An: Icecast streaming server user discussions > Betreff: Re: [Icecast] Send admin kill request to server > > On Feb 14, 2023, at 13:24, HGAlt wrote: > > > I am a little bit confused! > > > > http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21 > > > > This is an example of the Icecast documentation for kill a client. > > And this is a HTTP GET, which is send to the Icecast server. > > You also wrote, that there are no user and pass for an API. > > > > What I have to know, what does the Icecast server expect? > > If there is no user and pass, how the server knows, that is a valid > > request. > > > You should be able to send this with proper HTTP authentication > parameters by using CURL. Something like: > > curl -u admin:hackme > http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21 > > This is different from encoding the parameters as if they were part of > an HTML form. > -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephone: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ Gesch?ftsf?hrer/CEO: Philipp Schafft L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -- Diese E-Mail wurde von Avast-Antivirussoftware auf Viren gepr?ft. www.avast.com From phschafft at de.loewenfelsen.net Fri Feb 24 13:47:38 2023 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Fri, 24 Feb 2023 13:47:38 +0000 Subject: [Icecast] Send admin kill request to server In-Reply-To: <001801d9484d$318c72f0$94a558d0$@gmx.net> References: <000901d93fb2$932b7e50$b9827af0$@gmx.net> <002701d93fd9$2778edb0$766ac910$@gmx.net> <000c01d9406a$16a910f0$43fb32d0$@gmx.net> <0f0f5876bda87e81136be59bc73aa0c909bed7cd.camel@de.loewenfelsen.net> <001d01d940a1$8f023860$ad06a920$@gmx.net> <000801d94215$c6483e30$52d8ba90$@gmx.net> <000601d94393$dd295fb0$977c1f10$@gmx.net> <2d81eaab10709d74ff8e0a773c24d21b73cb9e6d.camel@de.loewenfelsen.net> <001801d9484d$318c72f0$94a558d0$@gmx.net> Message-ID: <65de60c8c55ab087af124af245400ed131b4e877.camel@de.loewenfelsen.net> Good morning, On Fri, 2023-02-24 at 13:40 +0100, HGAlt wrote: > Good Morning Philipp, > > that make be a good point. > But it would be very helpful, if in the Icecast documentation would > be very clear defined, which kind of authorization is required for > which server version. > > At least, I could not find anything! it's very simple: Icecast is a HTTP server so the HTTP authentication as defined in the relevant standards applies (this includes TLS if TLS is used). Everything else are just options and variants of that and your HTTP library will happily handle that for you. See e.g. RFC 9110 Section 11. Beside that it is hard to make a list of used sub options, if we would make a list that would only invite people to implement things against implementations not against the standard. A practice that has been proven problematic many times in the past. And there is really no need as all good HTTP libs do implement that for you. With best regards, > -----Urspr?ngliche Nachricht----- > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Philipp > Schafft > Gesendet: Samstag, 18. Februar 2023 20:53 > An: Icecast streaming server user discussions > Betreff: Re: [Icecast] Send admin kill request to server > > Good afternoon, > > On Sat, 2023-02-18 at 13:23 +0100, HGAlt wrote: > > Hi everybody, > > > > finally I found a solution! > > > > First, Icecast requires a Basic Authorization, which has to provide > > via a header. > > This is not fully correct. It depends on the configuration and may > change with different versions of the server. > > An important note here, and to be honest the main reason why I > answer: > NEVER EVER just append a random Authorization:-header without > implementing all of the HTTP authorisation mechanism. If you do so > you basically are broadcasting cleartext passwords to random peers, > and are likely to get in trouble with changes of software versions or > configurations. It is a big no-go. Always use the mechanism as > provided by your HTTP implementieren. > > Please see the relevant standards for a full discussion on how and > why this breaks security and interoperability. > > > > But this can?t be done via JavaScript or JQuery, due the security > > features of the browsers. > > For more detail information see > > https://stackoverflow.com/questions/75463305/difference-basic-authoriz > > ation-between-postman-and-jquery-ajax/75493285#75493285 > > . > > If you adhere to CORS it works fine for me. A simple XHR request with > credentials passed via open() worked. > > Naturally you are bound to CORS. Icecast can announce any kind of > CORS settings via it's config. > > XHR also allows you direct access to the response Icecast gives you > as it provides you with the response's DOM. So you can directly check > the result. :) > > > With best regards, > > > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von HGAlt > > Gesendet: Donnerstag, 16. Februar 2023 15:49 > > An: 'Icecast streaming server user discussions' > > Betreff: Re: [Icecast] Send admin kill request to server > > > > Hi Fred, > > > > I am understand the requirements already a little bit better. > > > > What I have to Do is a HTTP GET with a Basic Authorization in the > > header. I have tested it with ?Postman? and it works fine with > > Icecast. > > But I have to do it with Javascript or JQuery. Therefore curl > > doesn?t > > help me. > > > > I try to use Ajax for that, but something goes wrong. > > If I do it without Autorization, I got a return message which says > > 'Authentication required'. > > If I enable the Autorization it tells me only readyState: 0. > > > > If I will find a solution, I will post it here. > > > > Cheers > > > > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Fred > > Gleason > > Gesendet: Mittwoch, 15. Februar 2023 16:57 > > An: Icecast streaming server user discussions > > Betreff: Re: [Icecast] Send admin kill request to server > > > > On Feb 14, 2023, at 13:24, HGAlt wrote: > > > > > I am a little bit confused! > > > > > > http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21 > > > > > > This is an example of the Icecast documentation for kill a > > > client. > > > And this is a HTTP GET, which is send to the Icecast server. > > > You also wrote, that there are no user and pass for an API. > > > > > > What I have to know, what does the Icecast server expect? > > > If there is no user and pass, how the server knows, that is a > > > valid > > > request. > > > > You should be able to send this with proper HTTP authentication > > parameters by using CURL. Something like: > > > > curl -u admin:hackme > > http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21 > > > > This is different from encoding the parameters as if they were part > > of > > an HTML form. -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephone: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ Gesch?ftsf?hrer/CEO: Philipp Schafft L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From jayaubs89 at gmail.com Sat Feb 25 14:30:50 2023 From: jayaubs89 at gmail.com (Coolvibes Reloaded) Date: Sat, 25 Feb 2023 14:30:50 +0000 Subject: [Icecast] Own server Message-ID: How do I run my own https stream with autodj -------------- next part -------------- An HTML attachment was scrubbed... URL: From uktony at radiocompany.net Sat Feb 25 17:01:22 2023 From: uktony at radiocompany.net (uktony) Date: Sun, 26 Feb 2023 00:01:22 +0700 Subject: [Icecast] Own server In-Reply-To: Message-ID: <20230225170846.6100560E13@smtp3.osuosl.org> You need:Icecast serverCertbotEzstreamTonySent from my Galaxy -------- Original message --------From: Coolvibes Reloaded Date: 25/02/2023 21:31 (GMT+07:00) To: Icecast streaming server user discussions Subject: [Icecast] Own server How do I run my own https stream with autodj? -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayaubs89 at gmail.com Sat Feb 25 18:06:33 2023 From: jayaubs89 at gmail.com (Coolvibes Reloaded) Date: Sat, 25 Feb 2023 18:06:33 +0000 Subject: [Icecast] Own server In-Reply-To: <20230225170846.6100560E13@smtp3.osuosl.org> References: <20230225170846.6100560E13@smtp3.osuosl.org> Message-ID: Thanks I'm trying to set icecast up via nmms I'm doing all the rite things but can't find icecast folder anywhere On Sat, 25 Feb 2023, 17:08 uktony, wrote: > You need: > > Icecast server > Certbot > Ezstream > > Tony > > > > Sent from my Galaxy > > > -------- Original message -------- > From: Coolvibes Reloaded > Date: 25/02/2023 21:31 (GMT+07:00) > To: Icecast streaming server user discussions > Subject: [Icecast] Own server > > How do I run my own https stream with autodj > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordan at subj.am Sat Feb 25 18:52:59 2023 From: jordan at subj.am (Jordan Erickson) Date: Sat, 25 Feb 2023 10:52:59 -0800 Subject: [Icecast] Own server In-Reply-To: References: <20230225170846.6100560E13@smtp3.osuosl.org> Message-ID: <8dc22e52-9b23-7af7-ba82-c830d2781338@subj.am> Hi, I suggest studying the Icecast documentation before diving straight in. There's a good amount of information that goes through setup and configuration, including what you're asking. Cheers, Jordan https://icecast.org/docs/icecast-trunk/basic_setup/ On 2/25/23 10:06, Coolvibes Reloaded wrote: > Thanks I'm trying to set icecast up via nmms I'm doing all the rite > things but can't find icecast folder anywhere > > On Sat, 25 Feb 2023, 17:08 uktony, wrote: > > You need: > > Icecast server > Certbot > Ezstream > > Tony > > > > Sent from my Galaxy > > > -------- Original message -------- > From: Coolvibes Reloaded > Date: 25/02/2023 21:31 (GMT+07:00) > To: Icecast streaming server user discussions > Subject: [Icecast] Own server > > How do I run my own https stream with autodj > _______________________________________________ > 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: From jayaubs89 at gmail.com Sun Feb 26 13:12:27 2023 From: jayaubs89 at gmail.com (Coolvibes Reloaded) Date: Sun, 26 Feb 2023 13:12:27 +0000 Subject: [Icecast] Own server In-Reply-To: <8dc22e52-9b23-7af7-ba82-c830d2781338@subj.am> References: <20230225170846.6100560E13@smtp3.osuosl.org> <8dc22e52-9b23-7af7-ba82-c830d2781338@subj.am> Message-ID: Ok thank you! I thought icecast was https not http? On Sat, 25 Feb 2023, 19:02 Jordan Erickson, wrote: > Hi, I suggest studying the Icecast documentation before diving straight > in. There's a good amount of information that goes through setup and > configuration, including what you're asking. > > > Cheers, > Jordan > > https://icecast.org/docs/icecast-trunk/basic_setup/ > > On 2/25/23 10:06, Coolvibes Reloaded wrote: > > Thanks I'm trying to set icecast up via nmms I'm doing all the rite things > but can't find icecast folder anywhere > > On Sat, 25 Feb 2023, 17:08 uktony, wrote: > >> You need: >> >> Icecast server >> Certbot >> Ezstream >> >> Tony >> >> >> >> Sent from my Galaxy >> >> >> -------- Original message -------- >> From: Coolvibes Reloaded >> Date: 25/02/2023 21:31 (GMT+07:00) >> To: Icecast streaming server user discussions >> Subject: [Icecast] Own server >> >> How do I run my own https stream with autodj >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >> > > _______________________________________________ > Icecast mailing listIcecast at xiph.orghttp://lists.xiph.org/mailman/listinfo/icecast > > > -- > Jordan Erickson > SubJam, SPC - https://subj.am/ > +1 360.209.2057 > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From uktony at radiocompany.net Sun Feb 26 13:47:29 2023 From: uktony at radiocompany.net (uktony) Date: Sun, 26 Feb 2023 20:47:29 +0700 Subject: [Icecast] Own server In-Reply-To: Message-ID: <20230226135453.7F6CF814BB@smtp1.osuosl.org> You can turn on some port to https bt purring a 1 in the secure setting for that port in the icecast xml file.For instance sett 8443 to secure but port 80 no not secure.?TonySent from my Galaxy -------- Original message --------From: Coolvibes Reloaded Date: 26/02/2023 20:12 (GMT+07:00) To: Icecast streaming server user discussions Subject: Re: [Icecast] Own server Ok thank you! I thought icecast was https not http?On Sat, 25 Feb 2023, 19:02 Jordan Erickson, wrote: Hi, I suggest studying the Icecast documentation before diving straight in. There's a good amount of information that goes through setup and configuration, including what you're asking. Cheers, Jordan https://icecast.org/docs/icecast-trunk/basic_setup/ On 2/25/23 10:06, Coolvibes Reloaded wrote: Thanks I'm trying to set icecast up via nmms I'm doing all the rite things but can't find icecast folder anywhere? On Sat, 25 Feb 2023, 17:08 uktony, wrote: You need: Icecast server Certbot Ezstream Tony Sent from my Galaxy -------- Original message -------- From: Coolvibes Reloaded Date: 25/02/2023 21:31 (GMT+07:00) To: Icecast streaming server user discussions Subject: [Icecast] Own server How do I run my own https stream with autodj? _______________________________________________ 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 _______________________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From verten at xs4all.nl Sun Feb 26 14:01:28 2023 From: verten at xs4all.nl (Verten Radio) Date: Sun, 26 Feb 2023 15:01:28 +0100 Subject: [Icecast] Connections explained Message-ID: <0fd0d2a0-b5de-11ed-9d31-00505699d6e5@smtp.kpnmail.nl> I have a question about regular connections from ip-addresses such as 136.244.94.87 - - [26/Feb/2023:14:54:27 +0100] "GET /stream HTTP/1.1" 200 133567 "-" "Lavf/58.45.100" 3 Which never lead to a long lasting connection. Can anybody explain what kind of connections these are? THX Johan Verzonden vanuit Mail voor Windows -------------- next part -------------- An HTML attachment was scrubbed... URL: From uktony at radiocompany.net Sun Feb 26 14:00:02 2023 From: uktony at radiocompany.net (uktony at radiocompany.net) Date: Sun, 26 Feb 2023 07:00:02 -0700 Subject: [Icecast] Own server Message-ID: <20230226070002.d7a8cce5dc2a9772485faf40d3248484.921edeee3f.wbe@email26.godaddy.com> An HTML attachment was scrubbed... URL: From jayaubs89 at gmail.com Sun Feb 26 14:53:02 2023 From: jayaubs89 at gmail.com (Coolvibes Reloaded) Date: Sun, 26 Feb 2023 14:53:02 +0000 Subject: [Icecast] Own server In-Reply-To: <20230226070002.d7a8cce5dc2a9772485faf40d3248484.921edeee3f.wbe@email26.godaddy.com> References: <20230226070002.d7a8cce5dc2a9772485faf40d3248484.921edeee3f.wbe@email26.godaddy.com> Message-ID: Were it says in icecast.xml Can I have my website domain https://Coolvibes-reloaded.com On Sun, 26 Feb 2023, 14:08 , wrote: > You need something like this: > > > > 80 > > > > 443 > 1 > > > > 8000 > > > > 8080 > > > > 8443 > 1 > > > *AND YOU NEED* > > > > c:\icecast.pem > > > The location of the PEM file depends on if you are using Linux or windows. > > > -------- Original Message -------- > Subject: Re: [Icecast] Own server > From: Coolvibes Reloaded > Date: Sun, February 26, 2023 9:12 pm > To: Icecast streaming server user discussions > > Ok thank you! I thought icecast was https not http? > > On Sat, 25 Feb 2023, 19:02 Jordan Erickson, wrote: > >> Hi, I suggest studying the Icecast documentation before diving straight >> in. There's a good amount of information that goes through setup and >> configuration, including what you're asking. >> >> >> Cheers, >> Jordan >> >> https://icecast.org/docs/icecast-trunk/basic_setup/ >> >> On 2/25/23 10:06, Coolvibes Reloaded wrote: >> >> Thanks I'm trying to set icecast up via nmms I'm doing all the rite >> things but can't find icecast folder anywhere >> >> On Sat, 25 Feb 2023, 17:08 uktony, wrote: >> >>> You need: >>> >>> Icecast server >>> Certbot >>> Ezstream >>> >>> Tony >>> >>> >>> >>> Sent from my Galaxy >>> >>> >>> -------- Original message -------- >>> From: Coolvibes Reloaded >>> Date: 25/02/2023 21:31 (GMT+07:00) >>> To: Icecast streaming server user discussions >>> Subject: [Icecast] Own server >>> >>> How do I run my own https stream with autodj >>> _______________________________________________ >>> Icecast mailing list >>> Icecast at xiph.org >>> http://lists.xiph.org/mailman/listinfo/icecast >>> >> >> _______________________________________________ >> Icecast mailing listIcecast at xiph.orghttp://lists.xiph.org/mailman/listinfo/icecast >> >> >> -- >> Jordan Erickson >> SubJam, SPC - https://subj.am/ >> +1 360.209.2057 >> >> _______________________________________________ >> 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 > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayaubs89 at gmail.com Sun Feb 26 16:22:52 2023 From: jayaubs89 at gmail.com (Coolvibes Reloaded) Date: Sun, 26 Feb 2023 16:22:52 +0000 Subject: [Icecast] Own server In-Reply-To: <20230226135453.7F6CF814BB@smtp1.osuosl.org> References: <20230226135453.7F6CF814BB@smtp1.osuosl.org> Message-ID: have i configured this correctly? could you take a look please On Sun, Feb 26, 2023 at 1:54?PM uktony wrote: > You can turn on some port to https bt purring a 1 in the secure setting > for that port in the icecast xml file. > > For instance sett 8443 to secure but port 80 no not secure. > > Tony > > > > Sent from my Galaxy > > > -------- Original message -------- > From: Coolvibes Reloaded > Date: 26/02/2023 20:12 (GMT+07:00) > To: Icecast streaming server user discussions > Subject: Re: [Icecast] Own server > > Ok thank you! I thought icecast was https not http? > > On Sat, 25 Feb 2023, 19:02 Jordan Erickson, wrote: > >> Hi, I suggest studying the Icecast documentation before diving straight >> in. There's a good amount of information that goes through setup and >> configuration, including what you're asking. >> >> >> Cheers, >> Jordan >> >> https://icecast.org/docs/icecast-trunk/basic_setup/ >> >> On 2/25/23 10:06, Coolvibes Reloaded wrote: >> >> Thanks I'm trying to set icecast up via nmms I'm doing all the rite >> things but can't find icecast folder anywhere >> >> On Sat, 25 Feb 2023, 17:08 uktony, wrote: >> >>> You need: >>> >>> Icecast server >>> Certbot >>> Ezstream >>> >>> Tony >>> >>> >>> >>> Sent from my Galaxy >>> >>> >>> -------- Original message -------- >>> From: Coolvibes Reloaded >>> Date: 25/02/2023 21:31 (GMT+07:00) >>> To: Icecast streaming server user discussions >>> Subject: [Icecast] Own server >>> >>> How do I run my own https stream with autodj >>> _______________________________________________ >>> Icecast mailing list >>> Icecast at xiph.org >>> http://lists.xiph.org/mailman/listinfo/icecast >>> >> >> _______________________________________________ >> Icecast mailing listIcecast at xiph.orghttp://lists.xiph.org/mailman/listinfo/icecast >> >> >> -- >> Jordan Erickson >> SubJam, SPC - https://subj.am/ >> +1 360.209.2057 >> >> _______________________________________________ >> 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: icecast.xml Type: text/xml Size: 9008 bytes Desc: not available URL: From uktony at radiocompany.net Sun Feb 26 16:48:35 2023 From: uktony at radiocompany.net (uktony) Date: Sun, 26 Feb 2023 23:48:35 +0700 Subject: [Icecast] Own server In-Reply-To: Message-ID: <20230226164840.5E1D1403FB@smtp2.osuosl.org> I take it Laura is your wifeYou should NEVER post thinks to the net with your passwords in them. So change the passwords right way.You still have the ports rem'ed outRemove the around the ports to get them to work.More later?Sent from my Galaxy -------- Original message --------From: Coolvibes Reloaded Date: 26/02/2023 23:23 (GMT+07:00) To: Icecast streaming server user discussions Subject: Re: [Icecast] Own server have i configured this correctly?could you take a look pleaseOn Sun, Feb 26, 2023 at 1:54?PM uktony wrote:You can turn on some port to https bt purring a 1 in the secure setting for that port in the icecast xml file.For instance sett 8443 to secure but port 80 no not secure.?TonySent from my Galaxy-------- Original message --------From: Coolvibes Reloaded Date: 26/02/2023 20:12 (GMT+07:00) To: Icecast streaming server user discussions Subject: Re: [Icecast] Own server Ok thank you! I thought icecast was https not http?On Sat, 25 Feb 2023, 19:02 Jordan Erickson, wrote: Hi, I suggest studying the Icecast documentation before diving straight in. There's a good amount of information that goes through setup and configuration, including what you're asking. Cheers, Jordan https://icecast.org/docs/icecast-trunk/basic_setup/ On 2/25/23 10:06, Coolvibes Reloaded wrote: Thanks I'm trying to set icecast up via nmms I'm doing all the rite things but can't find icecast folder anywhere? On Sat, 25 Feb 2023, 17:08 uktony, wrote: You need: Icecast server Certbot Ezstream Tony Sent from my Galaxy -------- Original message -------- From: Coolvibes Reloaded Date: 25/02/2023 21:31 (GMT+07:00) To: Icecast streaming server user discussions Subject: [Icecast] Own server How do I run my own https stream with autodj? _______________________________________________ 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 _______________________________________________ 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: From uktony at radiocompany.net Sun Feb 26 17:17:51 2023 From: uktony at radiocompany.net (uktony) Date: Mon, 27 Feb 2023 00:17:51 +0700 Subject: [Icecast] Own server In-Reply-To: Message-ID: <20230226171806.C6F0260BEC@smtp3.osuosl.org> If you open this file in an html browser you will see different colours for the text and see that important parts are rem'ed out. The line towards the bottom of the file is commented out. That is those things. They tell systems to ignore the text between the two markers.This has the server working only on port 80. If you have this on your website server, that will cause a clash and I would guess that the website has grabbed port 80 and so icecast will not work.?I would put in a real email address for the administrator?All of this is explained in the icecast docs on the icecast.org website.TonySent from my Galaxy -------- Original message --------From: Coolvibes Reloaded Date: 26/02/2023 23:23 (GMT+07:00) To: Icecast streaming server user discussions Subject: Re: [Icecast] Own server have i configured this correctly?could you take a look pleaseOn Sun, Feb 26, 2023 at 1:54?PM uktony wrote:You can turn on some port to https bt purring a 1 in the secure setting for that port in the icecast xml file.For instance sett 8443 to secure but port 80 no not secure.?TonySent from my Galaxy-------- Original message --------From: Coolvibes Reloaded Date: 26/02/2023 20:12 (GMT+07:00) To: Icecast streaming server user discussions Subject: Re: [Icecast] Own server Ok thank you! I thought icecast was https not http?On Sat, 25 Feb 2023, 19:02 Jordan Erickson, wrote: Hi, I suggest studying the Icecast documentation before diving straight in. There's a good amount of information that goes through setup and configuration, including what you're asking. Cheers, Jordan https://icecast.org/docs/icecast-trunk/basic_setup/ On 2/25/23 10:06, Coolvibes Reloaded wrote: Thanks I'm trying to set icecast up via nmms I'm doing all the rite things but can't find icecast folder anywhere? On Sat, 25 Feb 2023, 17:08 uktony, wrote: You need: Icecast server Certbot Ezstream Tony Sent from my Galaxy -------- Original message -------- From: Coolvibes Reloaded Date: 25/02/2023 21:31 (GMT+07:00) To: Icecast streaming server user discussions Subject: [Icecast] Own server How do I run my own https stream with autodj? _______________________________________________ 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 _______________________________________________ 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: From jayaubs89 at gmail.com Sun Feb 26 17:20:02 2023 From: jayaubs89 at gmail.com (Coolvibes Reloaded) Date: Sun, 26 Feb 2023 17:20:02 +0000 Subject: [Icecast] Own server In-Reply-To: <20230226164840.5E1D1403FB@smtp2.osuosl.org> References: <20230226164840.5E1D1403FB@smtp2.osuosl.org> Message-ID: yes lauras my wife :) but where you referring to for the around the ports to get them to work. > > > > More later > > > > Sent from my Galaxy > > > -------- Original message -------- > From: Coolvibes Reloaded > Date: 26/02/2023 23:23 (GMT+07:00) > To: Icecast streaming server user discussions > Subject: Re: [Icecast] Own server > > have i configured this correctly? > > could you take a look please > > On Sun, Feb 26, 2023 at 1:54?PM uktony wrote: > >> You can turn on some port to https bt purring a 1 in the secure setting >> for that port in the icecast xml file. >> >> For instance sett 8443 to secure but port 80 no not secure. >> >> Tony >> >> >> >> Sent from my Galaxy >> >> >> -------- Original message -------- >> From: Coolvibes Reloaded >> Date: 26/02/2023 20:12 (GMT+07:00) >> To: Icecast streaming server user discussions >> Subject: Re: [Icecast] Own server >> >> Ok thank you! I thought icecast was https not http? >> >> On Sat, 25 Feb 2023, 19:02 Jordan Erickson, wrote: >> >>> Hi, I suggest studying the Icecast documentation before diving straight >>> in. There's a good amount of information that goes through setup and >>> configuration, including what you're asking. >>> >>> >>> Cheers, >>> Jordan >>> >>> https://icecast.org/docs/icecast-trunk/basic_setup/ >>> >>> On 2/25/23 10:06, Coolvibes Reloaded wrote: >>> >>> Thanks I'm trying to set icecast up via nmms I'm doing all the rite >>> things but can't find icecast folder anywhere >>> >>> On Sat, 25 Feb 2023, 17:08 uktony, wrote: >>> >>>> You need: >>>> >>>> Icecast server >>>> Certbot >>>> Ezstream >>>> >>>> Tony >>>> >>>> >>>> >>>> Sent from my Galaxy >>>> >>>> >>>> -------- Original message -------- >>>> From: Coolvibes Reloaded >>>> Date: 25/02/2023 21:31 (GMT+07:00) >>>> To: Icecast streaming server user discussions >>>> Subject: [Icecast] Own server >>>> >>>> How do I run my own https stream with autodj >>>> _______________________________________________ >>>> Icecast mailing list >>>> Icecast at xiph.org >>>> http://lists.xiph.org/mailman/listinfo/icecast >>>> >>> >>> _______________________________________________ >>> Icecast mailing listIcecast at xiph.orghttp://lists.xiph.org/mailman/listinfo/icecast >>> >>> >>> -- >>> Jordan Erickson >>> SubJam, SPC - https://subj.am/ >>> +1 360.209.2057 >>> >>> _______________________________________________ >>> 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 >> > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayaubs89 at gmail.com Mon Feb 27 02:06:54 2023 From: jayaubs89 at gmail.com (Coolvibes Reloaded) Date: Mon, 27 Feb 2023 02:06:54 +0000 Subject: [Icecast] Own server In-Reply-To: References: <20230226164840.5E1D1403FB@smtp2.osuosl.org> Message-ID: rite i've got the icecast2 page setup but i don't have any active mounts? why's that On Sun, Feb 26, 2023 at 5:20?PM Coolvibes Reloaded wrote: > yes lauras my wife :) but where you referring to for the around the ports to get them to work. >> >> >> >> More later >> >> >> >> Sent from my Galaxy >> >> >> -------- Original message -------- >> From: Coolvibes Reloaded >> Date: 26/02/2023 23:23 (GMT+07:00) >> To: Icecast streaming server user discussions >> Subject: Re: [Icecast] Own server >> >> have i configured this correctly? >> >> could you take a look please >> >> On Sun, Feb 26, 2023 at 1:54?PM uktony wrote: >> >>> You can turn on some port to https bt purring a 1 in the secure setting >>> for that port in the icecast xml file. >>> >>> For instance sett 8443 to secure but port 80 no not secure. >>> >>> Tony >>> >>> >>> >>> Sent from my Galaxy >>> >>> >>> -------- Original message -------- >>> From: Coolvibes Reloaded >>> Date: 26/02/2023 20:12 (GMT+07:00) >>> To: Icecast streaming server user discussions >>> Subject: Re: [Icecast] Own server >>> >>> Ok thank you! I thought icecast was https not http? >>> >>> On Sat, 25 Feb 2023, 19:02 Jordan Erickson, wrote: >>> >>>> Hi, I suggest studying the Icecast documentation before diving straight >>>> in. There's a good amount of information that goes through setup and >>>> configuration, including what you're asking. >>>> >>>> >>>> Cheers, >>>> Jordan >>>> >>>> https://icecast.org/docs/icecast-trunk/basic_setup/ >>>> >>>> On 2/25/23 10:06, Coolvibes Reloaded wrote: >>>> >>>> Thanks I'm trying to set icecast up via nmms I'm doing all the rite >>>> things but can't find icecast folder anywhere >>>> >>>> On Sat, 25 Feb 2023, 17:08 uktony, wrote: >>>> >>>>> You need: >>>>> >>>>> Icecast server >>>>> Certbot >>>>> Ezstream >>>>> >>>>> Tony >>>>> >>>>> >>>>> >>>>> Sent from my Galaxy >>>>> >>>>> >>>>> -------- Original message -------- >>>>> From: Coolvibes Reloaded >>>>> Date: 25/02/2023 21:31 (GMT+07:00) >>>>> To: Icecast streaming server user discussions >>>>> Subject: [Icecast] Own server >>>>> >>>>> How do I run my own https stream with autodj >>>>> _______________________________________________ >>>>> Icecast mailing list >>>>> Icecast at xiph.org >>>>> http://lists.xiph.org/mailman/listinfo/icecast >>>>> >>>> >>>> _______________________________________________ >>>> Icecast mailing listIcecast at xiph.orghttp://lists.xiph.org/mailman/listinfo/icecast >>>> >>>> >>>> -- >>>> Jordan Erickson >>>> SubJam, SPC - https://subj.am/ >>>> +1 360.209.2057 >>>> >>>> _______________________________________________ >>>> 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 >>> >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hgalt at gmx.net Mon Feb 27 09:50:10 2023 From: hgalt at gmx.net (HGAlt) Date: Mon, 27 Feb 2023 10:50:10 +0100 Subject: [Icecast] Send admin kill request to server In-Reply-To: <65de60c8c55ab087af124af245400ed131b4e877.camel@de.loewenfelsen.net> References: <000901d93fb2$932b7e50$b9827af0$@gmx.net> <002701d93fd9$2778edb0$766ac910$@gmx.net> <000c01d9406a$16a910f0$43fb32d0$@gmx.net> <0f0f5876bda87e81136be59bc73aa0c909bed7cd.camel@de.loewenfelsen.net> <001d01d940a1$8f023860$ad06a920$@gmx.net> <000801d94215$c6483e30$52d8ba90$@gmx.net> <000601d94393$dd295fb0$977c1f10$@gmx.net> <2d81eaab10709d74ff8e0a773c24d21b73cb9e6d.camel@de.loewenfelsen.net> <001801d9484d$318c72f0$94a558d0$@gmx.net> <65de60c8c55ab087af124af245400ed131b4e877.camel@de.loewenfelsen.net> Message-ID: <000f01d94a90$e289fba0$a79df2e0$@gmx.net> Good Morning Philipp, I think it is not that simple, that you maybe believe. In the standard, you are mentioned, are described the possibilities, which are possible. The Icecast documentation should define, which one is implemented by the Icecast server und this part is missing. Have a good time, HGA -----Urspr?ngliche Nachricht----- Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Philipp Schafft Gesendet: Freitag, 24. Februar 2023 14:48 An: Icecast streaming server user discussions Betreff: Re: [Icecast] Send admin kill request to server Good morning, On Fri, 2023-02-24 at 13:40 +0100, HGAlt wrote: > Good Morning Philipp, > > that make be a good point. > But it would be very helpful, if in the Icecast documentation would be > very clear defined, which kind of authorization is required for which > server version. > > At least, I could not find anything! it's very simple: Icecast is a HTTP server so the HTTP authentication as defined in the relevant standards applies (this includes TLS if TLS is used). Everything else are just options and variants of that and your HTTP library will happily handle that for you. See e.g. RFC 9110 Section 11. Beside that it is hard to make a list of used sub options, if we would make a list that would only invite people to implement things against implementations not against the standard. A practice that has been proven problematic many times in the past. And there is really no need as all good HTTP libs do implement that for you. With best regards, > -----Urspr?ngliche Nachricht----- > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Philipp > Schafft > Gesendet: Samstag, 18. Februar 2023 20:53 > An: Icecast streaming server user discussions > Betreff: Re: [Icecast] Send admin kill request to server > > Good afternoon, > > On Sat, 2023-02-18 at 13:23 +0100, HGAlt wrote: > > Hi everybody, > > > > finally I found a solution! > > > > First, Icecast requires a Basic Authorization, which has to provide > > via a header. > > This is not fully correct. It depends on the configuration and may > change with different versions of the server. > > An important note here, and to be honest the main reason why I > answer: > NEVER EVER just append a random Authorization:-header without > implementing all of the HTTP authorisation mechanism. If you do so you > basically are broadcasting cleartext passwords to random peers, and > are likely to get in trouble with changes of software versions or > configurations. It is a big no-go. Always use the mechanism as > provided by your HTTP implementieren. > > Please see the relevant standards for a full discussion on how and why > this breaks security and interoperability. > > > > But this can?t be done via JavaScript or JQuery, due the security > > features of the browsers. > > For more detail information see > > https://stackoverflow.com/questions/75463305/difference-basic-author > > iz > > ation-between-postman-and-jquery-ajax/75493285#75493285 > > . > > If you adhere to CORS it works fine for me. A simple XHR request with > credentials passed via open() worked. > > Naturally you are bound to CORS. Icecast can announce any kind of CORS > settings via it's config. > > XHR also allows you direct access to the response Icecast gives you as > it provides you with the response's DOM. So you can directly check the > result. :) > > > With best regards, > > > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von HGAlt > > Gesendet: Donnerstag, 16. Februar 2023 15:49 > > An: 'Icecast streaming server user discussions' > > Betreff: Re: [Icecast] Send admin kill request to server > > > > Hi Fred, > > > > I am understand the requirements already a little bit better. > > > > What I have to Do is a HTTP GET with a Basic Authorization in the > > header. I have tested it with ?Postman? and it works fine with > > Icecast. > > But I have to do it with Javascript or JQuery. Therefore curl > > doesn?t help me. > > > > I try to use Ajax for that, but something goes wrong. > > If I do it without Autorization, I got a return message which says > > 'Authentication required'. > > If I enable the Autorization it tells me only readyState: 0. > > > > If I will find a solution, I will post it here. > > > > Cheers > > > > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Fred > > Gleason > > Gesendet: Mittwoch, 15. Februar 2023 16:57 > > An: Icecast streaming server user discussions > > Betreff: Re: [Icecast] Send admin kill request to server > > > > On Feb 14, 2023, at 13:24, HGAlt wrote: > > > > > I am a little bit confused! > > > > > > http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=2 > > > 1 > > > > > > This is an example of the Icecast documentation for kill a client. > > > And this is a HTTP GET, which is send to the Icecast server. > > > You also wrote, that there are no user and pass for an API. > > > > > > What I have to know, what does the Icecast server expect? > > > If there is no user and pass, how the server knows, that is a > > > valid request. > > > > You should be able to send this with proper HTTP authentication > > parameters by using CURL. Something like: > > > > curl -u admin:hackme > > http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21 > > > > This is different from encoding the parameters as if they were part > > of an HTML form. -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephone: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ Gesch?ftsf?hrer/CEO: Philipp Schafft L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -- Diese E-Mail wurde von Avast-Antivirussoftware auf Viren gepr?ft. www.avast.com From phschafft at de.loewenfelsen.net Mon Feb 27 10:14:32 2023 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Mon, 27 Feb 2023 10:14:32 +0000 Subject: [Icecast] Send admin kill request to server In-Reply-To: <000f01d94a90$e289fba0$a79df2e0$@gmx.net> References: <000901d93fb2$932b7e50$b9827af0$@gmx.net> <002701d93fd9$2778edb0$766ac910$@gmx.net> <000c01d9406a$16a910f0$43fb32d0$@gmx.net> <0f0f5876bda87e81136be59bc73aa0c909bed7cd.camel@de.loewenfelsen.net> <001d01d940a1$8f023860$ad06a920$@gmx.net> <000801d94215$c6483e30$52d8ba90$@gmx.net> <000601d94393$dd295fb0$977c1f10$@gmx.net> <2d81eaab10709d74ff8e0a773c24d21b73cb9e6d.camel@de.loewenfelsen.net> <001801d9484d$318c72f0$94a558d0$@gmx.net> <65de60c8c55ab087af124af245400ed131b4e877.camel@de.loewenfelsen.net> <000f01d94a90$e289fba0$a79df2e0$@gmx.net> Message-ID: <35b54968c75a89185c0bebd908a271fcae479da6.camel@de.loewenfelsen.net> Good morning, On Mon, 2023-02-27 at 10:50 +0100, HGAlt wrote: > Good Morning Philipp, > > I think it is not that simple, that you maybe believe. > In the standard, you are mentioned, are described the possibilities, > which are possible. > > The Icecast documentation should define, which one is implemented by > the Icecast server und this part is missing. Why? Icecast is a HTTP server. It speaks HTTP. What you ask for is like having a contract with your energy provider that tells you that they will only ever allow one specific type of lightbulb. Never ever will they do anything but this type. Even if that type at some point becomes unavailable. This is the same kind of thing. HTTP specifies how negotiation of many of it's options work (not just auth related options). And it does that for good reasons. Often those reasons are discussed in the standards. (Everyone have a look! Reading those parts can be very fun and educational :) Also there is completely no need: Your HTTP implementation will negotia te with the server and they will find a common set of options that works for them. As a user of the HTTP implementation you don't need nor should worry about that. This is why you use such an implementation in the first place: it abstracts those protocols and standards to some API for you. So if you want to pass username+password, then pass that to your library and it will do the rest for you automagically. If you want to use something else then do that via the API. If the server is configured to let you access with a specific username+password combination than it will do that. How it does it, really doesn't nor shouldn't matter to you. You just pass those to the implementation and that's it. With best regards, > -----Urspr?ngliche Nachricht----- > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Philipp > Schafft > Gesendet: Freitag, 24. Februar 2023 14:48 > An: Icecast streaming server user discussions > Betreff: Re: [Icecast] Send admin kill request to server > > Good morning, > > On Fri, 2023-02-24 at 13:40 +0100, HGAlt wrote: > > Good Morning Philipp, > > > > that make be a good point. > > But it would be very helpful, if in the Icecast documentation would > > be > > very clear defined, which kind of authorization is required for > > which > > server version. > > > > At least, I could not find anything! > > it's very simple: Icecast is a HTTP server so the HTTP authentication > as defined in the relevant standards applies (this includes TLS if > TLS is used). Everything else are just options and variants of that > and your HTTP library will happily handle that for you. > > See e.g. RFC 9110 Section 11. > > > Beside that it is hard to make a list of used sub options, if we > would make a list that would only invite people to implement things > against implementations not against the standard. A practice that has > been proven problematic many times in the past. And there is really > no need as all good HTTP libs do implement that for you. > > > With best regards, > > > -----Urspr?ngliche Nachricht----- > > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von > > Philipp > > Schafft > > Gesendet: Samstag, 18. Februar 2023 20:53 > > An: Icecast streaming server user discussions > > Betreff: Re: [Icecast] Send admin kill request to server > > > > Good afternoon, > > > > On Sat, 2023-02-18 at 13:23 +0100, HGAlt wrote: > > > Hi everybody, > > > > > > finally I found a solution! > > > > > > First, Icecast requires a Basic Authorization, which has to > > > provide > > > via a header. > > > > This is not fully correct. It depends on the configuration and may > > change with different versions of the server. > > > > An important note here, and to be honest the main reason why I > > answer: > > NEVER EVER just append a random Authorization:-header without > > implementing all of the HTTP authorisation mechanism. If you do so > > you > > basically are broadcasting cleartext passwords to random peers, and > > are likely to get in trouble with changes of software versions or > > configurations. It is a big no-go. Always use the mechanism as > > provided by your HTTP implementieren. > > > > Please see the relevant standards for a full discussion on how and > > why > > this breaks security and interoperability. > > > > > > > But this can?t be done via JavaScript or JQuery, due the security > > > features of the browsers. > > > For more detail information see > > > https://stackoverflow.com/questions/75463305/difference-basic-author > > > iz > > > ation-between-postman-and-jquery-ajax/75493285#75493285 > > > . > > > > If you adhere to CORS it works fine for me. A simple XHR request > > with > > credentials passed via open() worked. > > > > Naturally you are bound to CORS. Icecast can announce any kind of > > CORS > > settings via it's config. > > > > XHR also allows you direct access to the response Icecast gives you > > as > > it provides you with the response's DOM. So you can directly check > > the > > result. :) > > > > > > With best regards, > > > > > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von > > > HGAlt > > > Gesendet: Donnerstag, 16. Februar 2023 15:49 > > > An: 'Icecast streaming server user discussions' > > > Betreff: Re: [Icecast] Send admin kill request to server > > > > > > Hi Fred, > > > > > > I am understand the requirements already a little bit better. > > > > > > What I have to Do is a HTTP GET with a Basic Authorization in the > > > header. I have tested it with ?Postman? and it works fine with > > > Icecast. > > > But I have to do it with Javascript or JQuery. Therefore curl > > > doesn?t help me. > > > > > > I try to use Ajax for that, but something goes wrong. > > > If I do it without Autorization, I got a return message which > > > says > > > 'Authentication required'. > > > If I enable the Autorization it tells me only readyState: 0. > > > > > > If I will find a solution, I will post it here. > > > > > > Cheers > > > > > > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von > > > Fred > > > Gleason > > > Gesendet: Mittwoch, 15. Februar 2023 16:57 > > > An: Icecast streaming server user discussions > > > Betreff: Re: [Icecast] Send admin kill request to server > > > > > > On Feb 14, 2023, at 13:24, HGAlt wrote: > > > > > > > I am a little bit confused! > > > > > > > > http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=2 > > > > 1 > > > > > > > > This is an example of the Icecast documentation for kill a > > > > client. > > > > And this is a HTTP GET, which is send to the Icecast server. > > > > You also wrote, that there are no user and pass for an API. > > > > > > > > What I have to know, what does the Icecast server expect? > > > > If there is no user and pass, how the server knows, that is a > > > > valid request. > > > > > > You should be able to send this with proper HTTP authentication > > > parameters by using CURL. Something like: > > > > > > curl -u admin:hackme > > > http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21 > > > > > > This is different from encoding the parameters as if they were > > > part > > > of an HTML form. -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephone: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ Gesch?ftsf?hrer/CEO: Philipp Schafft L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From phschafft at de.loewenfelsen.net Mon Feb 27 10:24:10 2023 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Mon, 27 Feb 2023 10:24:10 +0000 Subject: [Icecast] Connections explained In-Reply-To: <0fd0d2a0-b5de-11ed-9d31-00505699d6e5@smtp.kpnmail.nl> References: <0fd0d2a0-b5de-11ed-9d31-00505699d6e5@smtp.kpnmail.nl> Message-ID: Good morning, On Sun, 2023-02-26 at 15:01 +0100, Verten Radio wrote: > I have a question about regular connections from ip-addresses such as > 136.244.94.87 - - [26/Feb/2023:14:54:27 +0100] "GET /stream HTTP/1.1" > 200 133567 "-" "Lavf/58.45.100" 3 > Which never lead to a long lasting connection. > > Can anybody explain what kind of connections these are? "Lavf" is basically ffmpeg. And such short connections can be probes of some kind. Short probe connections are common to detect if a connection should be downgraded to ICY to support legacy codecs such as MP3 and AAC. I would guess that you will see another log entry for the same client with a longer connection time later on. But as the log entry can (for obvious reasons) only be written when the client disconnected it might be much later in the log file. It could also be some kind of monitoring. E.g. some aggregation services do that so they know the stream is actually be working before they offer it in listings to the actual user. Generally speaking probes don't do harm and are hardly a source of worry. With best regards, -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephone: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ Gesch?ftsf?hrer/CEO: Philipp Schafft L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From phschafft at de.loewenfelsen.net Mon Feb 27 10:27:50 2023 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Mon, 27 Feb 2023 10:27:50 +0000 Subject: [Icecast] Own server In-Reply-To: References: <20230226164840.5E1D1403FB@smtp2.osuosl.org> Message-ID: Good morning, On Mon, 2023-02-27 at 02:06 +0000, Coolvibes Reloaded wrote: > rite i've got the icecast2 page setup but i don't have any active > mounts? > why's that once you got your server running it will list those sources that are connected. So if it is freshly started and there are no sources connected nothing is shown as there is nothing to show. The next step would be to get your source client ready and let it connect. With best regards, -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephone: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ Gesch?ftsf?hrer/CEO: Philipp Schafft L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From jayaubs89 at gmail.com Mon Feb 27 12:34:46 2023 From: jayaubs89 at gmail.com (Coolvibes Reloaded) Date: Mon, 27 Feb 2023 12:34:46 +0000 Subject: [Icecast] Own server In-Reply-To: References: <20230226164840.5E1D1403FB@smtp2.osuosl.org> Message-ID: can i send you my xml file so you can check it over? i'v changed my passwords to example123 just for sending to the community for this instance so the config file isn't showing any of my private passwords On Mon, Feb 27, 2023 at 10:27?AM Philipp Schafft < phschafft at de.loewenfelsen.net> wrote: > Good morning, > > On Mon, 2023-02-27 at 02:06 +0000, Coolvibes Reloaded wrote: > > rite i've got the icecast2 page setup but i don't have any active > > mounts? > > why's that > > once you got your server running it will list those sources that are > connected. So if it is freshly started and there are no sources > connected nothing is shown as there is nothing to show. > > The next step would be to get your source client ready and let it > connect. > > > With best regards, > > -- > Philipp Schafft (CEO/Gesch?ftsf?hrer) > Telephone: +49.3535 490 17 92 > Website: https://www.loewenfelsen.net/ > Follow us: https://www.linkedin.com/company/loewenfelsen/ > Gesch?ftsf?hrer/CEO: Philipp Schafft > > L?wenfelsen UG (haftungsbeschr?nkt) Registration number: > Bickinger Stra?e 21 HRB 12308 CB > 04916 Herzberg (Elster) VATIN/USt-ID: > Germany DE305133015 > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayaubs89 at gmail.com Mon Feb 27 12:38:39 2023 From: jayaubs89 at gmail.com (Coolvibes Reloaded) Date: Mon, 27 Feb 2023 12:38:39 +0000 Subject: [Icecast] Send admin kill request to server In-Reply-To: <001801d9484d$318c72f0$94a558d0$@gmx.net> References: <000901d93fb2$932b7e50$b9827af0$@gmx.net> <002701d93fd9$2778edb0$766ac910$@gmx.net> <000c01d9406a$16a910f0$43fb32d0$@gmx.net> <0f0f5876bda87e81136be59bc73aa0c909bed7cd.camel@de.loewenfelsen.net> <001d01d940a1$8f023860$ad06a920$@gmx.net> <000801d94215$c6483e30$52d8ba90$@gmx.net> <000601d94393$dd295fb0$977c1f10$@gmx.net> <2d81eaab10709d74ff8e0a773c24d21b73cb9e6d.camel@de.loewenfelsen.net> <001801d9484d$318c72f0$94a558d0$@gmx.net> Message-ID: ha funny stating about authorization i can't find anything either On Fri, Feb 24, 2023 at 12:40?PM HGAlt wrote: > Good Morning Philipp, > > that make be a good point. > But it would be very helpful, if in the Icecast documentation would be > very clear defined, which kind of authorization is required for which > server version. > > At least, I could not find anything! > > -----Urspr?ngliche Nachricht----- > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Philipp > Schafft > Gesendet: Samstag, 18. Februar 2023 20:53 > An: Icecast streaming server user discussions > Betreff: Re: [Icecast] Send admin kill request to server > > Good afternoon, > > On Sat, 2023-02-18 at 13:23 +0100, HGAlt wrote: > > Hi everybody, > > > > finally I found a solution! > > > > First, Icecast requires a Basic Authorization, which has to provide > > via a header. > > This is not fully correct. It depends on the configuration and may change > with different versions of the server. > > An important note here, and to be honest the main reason why I answer: > NEVER EVER just append a random Authorization:-header without implementing > all of the HTTP authorisation mechanism. If you do so you basically are > broadcasting cleartext passwords to random peers, and are likely to get in > trouble with changes of software versions or configurations. It is a big > no-go. Always use the mechanism as provided by your HTTP implementieren. > > Please see the relevant standards for a full discussion on how and why > this breaks security and interoperability. > > > > But this can?t be done via JavaScript or JQuery, due the security > > features of the browsers. > > For more detail information see > > https://stackoverflow.com/questions/75463305/difference-basic-authoriz > > ation-between-postman-and-jquery-ajax/75493285#75493285 > > . > > If you adhere to CORS it works fine for me. A simple XHR request with > credentials passed via open() worked. > > Naturally you are bound to CORS. Icecast can announce any kind of CORS > settings via it's config. > > XHR also allows you direct access to the response Icecast gives you as it > provides you with the response's DOM. So you can directly check the result. > :) > > > With best regards, > > > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von HGAlt > > Gesendet: Donnerstag, 16. Februar 2023 15:49 > > An: 'Icecast streaming server user discussions' > > Betreff: Re: [Icecast] Send admin kill request to server > > > > Hi Fred, > > > > I am understand the requirements already a little bit better. > > > > What I have to Do is a HTTP GET with a Basic Authorization in the > > header. I have tested it with ?Postman? and it works fine with > > Icecast. > > But I have to do it with Javascript or JQuery. Therefore curl doesn?t > > help me. > > > > I try to use Ajax for that, but something goes wrong. > > If I do it without Autorization, I got a return message which says > > 'Authentication required'. > > If I enable the Autorization it tells me only readyState: 0. > > > > If I will find a solution, I will post it here. > > > > Cheers > > > > Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Fred > > Gleason > > Gesendet: Mittwoch, 15. Februar 2023 16:57 > > An: Icecast streaming server user discussions > > Betreff: Re: [Icecast] Send admin kill request to server > > > > On Feb 14, 2023, at 13:24, HGAlt wrote: > > > > > I am a little bit confused! > > > > > > http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21 > > > > > > This is an example of the Icecast documentation for kill a client. > > > And this is a HTTP GET, which is send to the Icecast server. > > > You also wrote, that there are no user and pass for an API. > > > > > > What I have to know, what does the Icecast server expect? > > > If there is no user and pass, how the server knows, that is a valid > > > request. > > > > > > You should be able to send this with proper HTTP authentication > > parameters by using CURL. Something like: > > > > curl -u admin:hackme > > http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg&id=21 > > > > This is different from encoding the parameters as if they were part of > > an HTML form. > > > > -- > Philipp Schafft (CEO/Gesch?ftsf?hrer) > Telephone: +49.3535 490 17 92 > Website: https://www.loewenfelsen.net/ > Follow us: https://www.linkedin.com/company/loewenfelsen/ > Gesch?ftsf?hrer/CEO: Philipp Schafft > > L?wenfelsen UG (haftungsbeschr?nkt) Registration number: > Bickinger Stra?e 21 HRB 12308 CB > 04916 Herzberg (Elster) VATIN/USt-ID: > Germany DE305133015 > > > -- > Diese E-Mail wurde von Avast-Antivirussoftware auf Viren gepr?ft. > www.avast.com > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From phschafft at de.loewenfelsen.net Mon Feb 27 17:14:27 2023 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Mon, 27 Feb 2023 17:14:27 +0000 Subject: [Icecast] Presentation this Friday Message-ID: <7e94bc86831af983c5a3777533de8346b505661c.camel@de.loewenfelsen.net> Good morning, after the inter-year break we are considering schedules and topics for this year's presentations. (If anyone has request, please let us know off-list :) This Friday 15:00 UTC we would like to start with bit informal session. I will talk about recent development in Icecast. This includes the changes from November to now. Topics include: * recent security fixes, * updates to the auth backend, * updates to the event backend and how the event backend can provide a performance benefit for more complex setups, * a few words on updated stats and dump file code, * general direction for the next months. As always we hope for an active discussion in the second part of the presentation. If you want to join please send me a short message off-list or on IRC. Virtual seats are as always limited. With best regards, -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephone: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ Gesch?ftsf?hrer/CEO: Philipp Schafft L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From jayaubs89 at gmail.com Tue Feb 28 01:07:02 2023 From: jayaubs89 at gmail.com (Coolvibes Reloaded) Date: Tue, 28 Feb 2023 01:07:02 +0000 Subject: [Icecast] add user failed check log Message-ID: i'm trying to config the usr authentication but when i goto add myself into the admin part i get add user failed check log? so i did and i'm getting this [2023-02-28 00:46:16] INFO admin/admin.c Received admin command manageauth.xsl on mount "/live.mp3" [2023-02-28 00:46:16] EROR auth_htpasswd/auth_htpasswd.c No filename given in options for authenticator. [2023-02-28 00:46:16] EROR auth_htpasswd/auth_htpasswd.c No filename given in options for authenticator. [2023-02-28 00:46:16] DBUG admin/admin.c Sending XSLT (./admin\manageauth.xsl) [2023-02-28 00:46:16] DBUG xslt/xslt.c Using cached sheet 0 [2023-02-28 00:44:26] WARN auth/auth.c unknown auth setting (auth) [2023-02-28 00:44:26] WARN auth/auth.c unknown auth setting (comment) [2023-02-28 00:44:26] EROR auth_htpasswd/auth_htpasswd.c No filename given in options for authenticator. [2023-02-28 00:44:26] EROR connection/connection.c Could not create listener socket on port 8080 bind my ip [2023-02-28 00:44:26] EROR connection/connection.c Could not create listener socket on port 8081 bind my ip now my config file is United Kingdom someemail at example.com yourip/url 9000 2 524288 30 15 10 1 65535 somepass somepass admin somepass /stream 15 http://dir.xiph.org/cgi-bin/yp-cgi someport someip /stream 1 1 8080 1 8080 1 8080 /stream 8080 8080 8080 1
someip someport /coolvibes.ogg /strawbs.ogg 0 0 /live.mp3 someusername someexamplepass 900 3600 /tmp/dump-example1.ogg /intro.ogg /stream.ogg 1 1 ISO8859-1 1 somestream 'hello' someurl World 160 application/mp3 mp3 1 65536 4096
/home/icecast/bin/source-start /home/icecast/bin/source-end 1 ./log ./web ./admin 0 user users access.log error.log 4 10000 -------------- next part -------------- An HTML attachment was scrubbed... URL: From phschafft at de.loewenfelsen.net Tue Feb 28 11:28:08 2023 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Tue, 28 Feb 2023 11:28:08 +0000 Subject: [Icecast] add user failed check log In-Reply-To: References: Message-ID: <059d4064b092c6b4e3836504bc53e5b95207ddf4.camel@de.loewenfelsen.net> Good morning, On Tue, 2023-02-28 at 01:07 +0000, Coolvibes Reloaded wrote: > i'm trying to config the usr authentication > but when i goto add myself into the admin part > i get add user failed check log? > > so i did and i'm getting this > [...] > [2023-02-28 00:46:16] EROR auth_htpasswd/auth_htpasswd.c No filename > given in options for authenticator. > [...] There is no filename given for the htpasswd auth, will comment below. > [2023-02-28 00:44:26] WARN auth/auth.c unknown auth setting (auth) > [2023-02-28 00:44:26] WARN auth/auth.c unknown auth setting > (comment) > [2023-02-28 00:44:26] EROR auth_htpasswd/auth_htpasswd.c No filename > given in options for authenticator. > [2023-02-28 00:44:26] EROR connection/connection.c Could not create > listener socket on port 8080 bind my ip > [2023-02-28 00:44:26] EROR connection/connection.c Could not create > listener socket on port 8081 bind my ip Another set of warnings. Looking at the config below you seem to have fallen into the over configuration trap. Plus I'm not sure where some of that came from. Maybe you want to comment on that so we can improve docs/default configs. What is also missing is which exact version of Icecast you are running. The below seems to be a mix of 2.4.x and 2.5.x. I try to answer in a generic was for both. I would also suggest you to run xmllint every time you change the config as it checks the syntax. Helps to spot problems early. It also provides a way to autoformat (with the --format option) the file. Which is very nice. Another general note here: Everyone using 2.5.x is recommended to have a look at the dashboard. Icecast reports many common problems there. It is much easier to spot things very early there. > now my config file is > > > > United Kingdom > someemail at example.com > > > yourip/url This is not for an IP address nor an URL. It is for the hostname of the server. ;) > > > > 9000 > 2 > 524288 > 30 > 15 > 10 > > 1 > > 65535 > > > > > somepass > > somepass > > > admin > somepass > > > > > > > /stream > > 15 > http://dir.xiph.org/cgi-bin/yp-cgi > > > > > someport > someip > /stream > 1 > 1 > > > > 8080 > 1 > > > > 8080 > 1 > > > > 8080 > /stream > > > > 8080 > > > > 8080 > > > > 8080 > 1 > You repeat yourself a lot here. Clearly you can only bind once to each port and address pair. (If no bind address is given, the wildcard address is assumed.) As for the TLS settings: in 2.4.x it is 1 and in 2.5.x it is true (which is the same as setting it to "rfc2818"). However for 2.5.x I would recommend to set this to auto (which allows any mode, including non-TLS) or auto_no_plain which allows any mode but non-TLS. More details can be found e.g. here: https://wiki.xiph.org/Icecast_Server/known_https_restrictions#Icecast2_2.5.x_.28branch_.22master.22.29 If there is general interest in this I can talk a little bit about this on Friday as well. > > >
>
/> > > > > > > > > > > > > > someip > someport > /coolvibes.ogg > /strawbs.ogg > 0 > > 0 > If you're using recent 2.5.x you can also use http://example.org/blubb here for the upstream address. > > > > > > /live.mp3 In this block you set a real huge amount of options. I guess most of them can go. Some are set to the default value (e.g. you set to the same value as the global default). Some should be avoided unless there is a real requiement (e.g. <*type*>, <*metadata*>, <*header*>, , ...). And for some I'm not sure if you actually use them (, , ). Generally speaking use as little options as possible. > someusername > someexamplepass > 900 > 3600 > /tmp/dump-example1.ogg > /intro.ogg > /stream.ogg > 1 > 1 > ISO8859-1 > 1 > somestream > 'hello' > someurl > World > 160 > application/mp3 > mp3 > 1 > 65536 > 4096 > > > Not sure where you got this block from. Generally the htpasswd type takes an option with the filename. From the 2.4.4 example: The filename is relativ to Icecast's cwd (after chroot if any). So depending on your setup you might want to set it absolute. > >
>
>
>
> > /home/icecast/bin/source-start > /home/icecast/bin/source-end > The rest below is 2.4.x style config. Nothing wroth with it even for 2.5.x. But it might be a bit nicer to read/work with in 2.5.x style. > 1 > > > ./log > ./web > ./admin Relative paths here look a bit like you try to run it not as a service. I would avoid this outside of testing. > > > > > > > > > > 0 > > Having changeowner active is not the nicest thing. Unless you need the extra permissions for e.g. binding to a privileged port I would suggest to not use this. If running as a service it is best to let the operating system change to the correct user before starting Icecast. if running ?n a more test setup sudo/doas -u works very nice to switch to the target user. > user > users > > > > > > access.log > error.log > > 4 > 10000 > > > > With best regards, -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephone: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ Gesch?ftsf?hrer/CEO: Philipp Schafft L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From jayaubs89 at gmail.com Tue Feb 28 12:32:15 2023 From: jayaubs89 at gmail.com (Coolvibes Reloaded) Date: Tue, 28 Feb 2023 12:32:15 +0000 Subject: [Icecast] add user failed check log In-Reply-To: <059d4064b092c6b4e3836504bc53e5b95207ddf4.camel@de.loewenfelsen.net> References: <059d4064b092c6b4e3836504bc53e5b95207ddf4.camel@de.loewenfelsen.net> Message-ID: Good afternoon Ah that's probably why I'm getting errors I'm running version 2.4.4 on a windows 10 laptop using command prompt in admin mode, also you mentioned about a trap what's that? And why am I getting adding user failed I don't want listeners to consistently login everytime they tune in? On Tue, 28 Feb 2023, 11:28 Philipp Schafft, wrote: > Good morning, > > On Tue, 2023-02-28 at 01:07 +0000, Coolvibes Reloaded wrote: > > i'm trying to config the usr authentication > > but when i goto add myself into the admin part > > i get add user failed check log? > > > > so i did and i'm getting this > > [...] > > [2023-02-28 00:46:16] EROR auth_htpasswd/auth_htpasswd.c No filename > > given in options for authenticator. > > [...] > > There is no filename given for the htpasswd auth, will comment below. > > > > > [2023-02-28 00:44:26] WARN auth/auth.c unknown auth setting (auth) > > [2023-02-28 00:44:26] WARN auth/auth.c unknown auth setting > > (comment) > > [2023-02-28 00:44:26] EROR auth_htpasswd/auth_htpasswd.c No filename > > given in options for authenticator. > > [2023-02-28 00:44:26] EROR connection/connection.c Could not create > > listener socket on port 8080 bind my ip > > [2023-02-28 00:44:26] EROR connection/connection.c Could not create > > listener socket on port 8081 bind my ip > > Another set of warnings. Looking at the config below you seem to have > fallen into the over configuration trap. Plus I'm not sure where some > of that came from. Maybe you want to comment on that so we can improve > docs/default configs. > > > What is also missing is which exact version of Icecast you are running. > The below seems to be a mix of 2.4.x and 2.5.x. I try to answer in a > generic was for both. > > I would also suggest you to run xmllint every time you change the > config as it checks the syntax. Helps to spot problems early. It also > provides a way to autoformat (with the --format option) the file. Which > is very nice. > > Another general note here: Everyone using 2.5.x is recommended to have > a look at the dashboard. Icecast reports many common problems there. It > is much easier to spot things very early there. > > > > now my config file is > > > > > > > > United Kingdom > > someemail at example.com > > > > > > yourip/url > > This is not for an IP address nor an URL. It is for the hostname of the > server. ;) > > > > > > > > > > 9000 > > 2 > > 524288 > > 30 > > 15 > > 10 > > > > 1 > > > > 65535 > > > > > > > > > > somepass > > > > somepass > > > > > > admin > > somepass > > > > > > > > > > > > > > /stream > > > > > > 15 > > http://dir.xiph.org/cgi-bin/yp-cgi > > > > > > > > > > someport > > someip > > /stream > > 1 > > 1 > > > > > > > > 8080 > > 1 > > > > > > > > 8080 > > 1 > > > > > > > > 8080 > > /stream > > > > > > > > 8080 > > > > > > > > 8080 > > > > > > > > 8080 > > 1 > > > > You repeat yourself a lot here. Clearly you can only bind once to each > port and address pair. (If no bind address is given, the wildcard > address is assumed.) > > As for the TLS settings: in 2.4.x it is 1 and in 2.5.x it is > true (which is the same as setting it to "rfc2818"). However > for 2.5.x I would recommend to set this to auto (which > allows any mode, including non-TLS) or auto_no_plain which > allows any mode but non-TLS. > > More details can be found e.g. here: > > https://wiki.xiph.org/Icecast_Server/known_https_restrictions#Icecast2_2.5.x_.28branch_.22master.22.29 > > If there is general interest in this I can talk a little bit about this > on Friday as well. > > > > > > > >
> >
> /> > > > > > > > > > > > > > > > > > > > > > > > > > > someip > > someport > > /coolvibes.ogg > > /strawbs.ogg > > 0 > > > > 0 > > > > If you're using recent 2.5.x you can also use > http://example.org/blubb here for the upstream address. > > > > > > > > > > > > > > /live.mp3 > > In this block you set a real huge amount of options. I guess most of > them can go. Some are set to the default value (e.g. you set size> to the same value as the global default). Some should be avoided > unless there is a real requiement (e.g. <*type*>, <*metadata*>, > <*header*>, , ...). And for some I'm not sure if you actually > use them (, , ). > > Generally speaking use as little options as possible. > > > > someusername > > someexamplepass > > 900 > > 3600 > > /tmp/dump-example1.ogg > > /intro.ogg > > /stream.ogg > > 1 > > 1 > > ISO8859-1 > > 1 > > somestream > > 'hello' > > someurl > > World > > 160 > > application/mp3 > > mp3 > > 1 > > 65536 > > 4096 > > > > > > > > > Not sure where you got this block from. > Generally the htpasswd type takes an option with the filename. From the > 2.4.4 example: > > > > The filename is relativ to Icecast's cwd (after chroot if any). So > depending on your setup you might want to set it absolute. > > > > > > >
> >
> >
> >
> > > > /home/icecast/bin/source-start > > /home/icecast/bin/source-end > > > > > The rest below is 2.4.x style config. Nothing wroth with it even for > 2.5.x. But it might be a bit nicer to read/work with in 2.5.x style. > > > 1 > > > > > > ./log > > ./web > > ./admin > > Relative paths here look a bit like you try to run it not as a service. > I would avoid this outside of testing. > > > > > > > > > > > > > > > > > > > > > > 0 > > > > > > Having changeowner active is not the nicest thing. Unless you need the > extra permissions for e.g. binding to a privileged port I would suggest > to not use this. If running as a service it is best to let the > operating system change to the correct user before starting Icecast. if > running ?n a more test setup sudo/doas -u works very nice to switch to > the target user. > > > > user > > users > > > > > > > > > > > > access.log > > error.log > > > > 4 > > 10000 > > > > > > > > > > > With best regards, > > -- > Philipp Schafft (CEO/Gesch?ftsf?hrer) > Telephone: +49.3535 490 17 92 > Website: https://www.loewenfelsen.net/ > Follow us: https://www.linkedin.com/company/loewenfelsen/ > Gesch?ftsf?hrer/CEO: Philipp Schafft > > L?wenfelsen UG (haftungsbeschr?nkt) Registration number: > Bickinger Stra?e 21 HRB 12308 CB > 04916 Herzberg (Elster) VATIN/USt-ID: > Germany DE305133015 > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayaubs89 at gmail.com Mon Feb 27 17:18:03 2023 From: jayaubs89 at gmail.com (Coolvibes Reloaded) Date: Mon, 27 Feb 2023 17:18:03 +0000 Subject: [Icecast] Own server In-Reply-To: References: <20230226164840.5E1D1403FB@smtp2.osuosl.org> Message-ID: sorry source client is up n running ip:port is streaming, now i want to know about the authentication i don't want outsiders to keep logging in eachtime they tune in. so how do i turn authentication off? also i'm getting these errors [image: image.png] On Mon, Feb 27, 2023 at 10:27?AM Philipp Schafft < phschafft at de.loewenfelsen.net> wrote: > Good morning, > > On Mon, 2023-02-27 at 02:06 +0000, Coolvibes Reloaded wrote: > > rite i've got the icecast2 page setup but i don't have any active > > mounts? > > why's that > > once you got your server running it will list those sources that are > connected. So if it is freshly started and there are no sources > connected nothing is shown as there is nothing to show. > > The next step would be to get your source client ready and let it > connect. > > > With best regards, > > -- > Philipp Schafft (CEO/Gesch?ftsf?hrer) > Telephone: +49.3535 490 17 92 > Website: https://www.loewenfelsen.net/ > Follow us: https://www.linkedin.com/company/loewenfelsen/ > Gesch?ftsf?hrer/CEO: Philipp Schafft > > L?wenfelsen UG (haftungsbeschr?nkt) Registration number: > Bickinger Stra?e 21 HRB 12308 CB > 04916 Herzberg (Elster) VATIN/USt-ID: > Germany DE305133015 > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 143351 bytes Desc: not available URL: From jayaubs89 at gmail.com Tue Feb 28 16:21:29 2023 From: jayaubs89 at gmail.com (Coolvibes Reloaded) Date: Tue, 28 Feb 2023 16:21:29 +0000 Subject: [Icecast] add user failed check log In-Reply-To: <059d4064b092c6b4e3836504bc53e5b95207ddf4.camel@de.loewenfelsen.net> References: <059d4064b092c6b4e3836504bc53e5b95207ddf4.camel@de.loewenfelsen.net> Message-ID: rite now i have this code in which i got from xiph guide LAPTOP-U97RKMM3 United Kingdom jayaubs89 at gmail.com 1 icecast 2.4.4 100 2 102400 30 15 10 1 65536 examplepass examplepass admin examplepass /stream /example.ogg 8000 127.0.0.1 8443 1 8004 /live.mp3
./ ./logs ./icecast.pid ./web ./admin /path/to/ip_allowlist /path_to_ip_denylist /path/to/certificate.pem ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS access.log error.log playlist.log 4 15 http://dir.xiph.org/cgi-bin/yp-cgi but i'm running the gui on windows10 i can't for the life of me find logs folder and any of the other folders? On Tue, Feb 28, 2023 at 11:28?AM Philipp Schafft < phschafft at de.loewenfelsen.net> wrote: > Good morning, > > On Tue, 2023-02-28 at 01:07 +0000, Coolvibes Reloaded wrote: > > i'm trying to config the usr authentication > > but when i goto add myself into the admin part > > i get add user failed check log? > > > > so i did and i'm getting this > > [...] > > [2023-02-28 00:46:16] EROR auth_htpasswd/auth_htpasswd.c No filename > > given in options for authenticator. > > [...] > > There is no filename given for the htpasswd auth, will comment below. > > > > > [2023-02-28 00:44:26] WARN auth/auth.c unknown auth setting (auth) > > [2023-02-28 00:44:26] WARN auth/auth.c unknown auth setting > > (comment) > > [2023-02-28 00:44:26] EROR auth_htpasswd/auth_htpasswd.c No filename > > given in options for authenticator. > > [2023-02-28 00:44:26] EROR connection/connection.c Could not create > > listener socket on port 8080 bind my ip > > [2023-02-28 00:44:26] EROR connection/connection.c Could not create > > listener socket on port 8081 bind my ip > > Another set of warnings. Looking at the config below you seem to have > fallen into the over configuration trap. Plus I'm not sure where some > of that came from. Maybe you want to comment on that so we can improve > docs/default configs. > > > What is also missing is which exact version of Icecast you are running. > The below seems to be a mix of 2.4.x and 2.5.x. I try to answer in a > generic was for both. > > I would also suggest you to run xmllint every time you change the > config as it checks the syntax. Helps to spot problems early. It also > provides a way to autoformat (with the --format option) the file. Which > is very nice. > > Another general note here: Everyone using 2.5.x is recommended to have > a look at the dashboard. Icecast reports many common problems there. It > is much easier to spot things very early there. > > > > now my config file is > > > > > > > > United Kingdom > > someemail at example.com > > > > > > yourip/url > > This is not for an IP address nor an URL. It is for the hostname of the > server. ;) > > > > > > > > > > 9000 > > 2 > > 524288 > > 30 > > 15 > > 10 > > > > 1 > > > > 65535 > > > > > > > > > > somepass > > > > somepass > > > > > > admin > > somepass > > > > > > > > > > > > > > /stream > > > > > > 15 > > http://dir.xiph.org/cgi-bin/yp-cgi > > > > > > > > > > someport > > someip > > /stream > > 1 > > 1 > > > > > > > > 8080 > > 1 > > > > > > > > 8080 > > 1 > > > > > > > > 8080 > > /stream > > > > > > > > 8080 > > > > > > > > 8080 > > > > > > > > 8080 > > 1 > > > > You repeat yourself a lot here. Clearly you can only bind once to each > port and address pair. (If no bind address is given, the wildcard > address is assumed.) > > As for the TLS settings: in 2.4.x it is 1 and in 2.5.x it is > true (which is the same as setting it to "rfc2818"). However > for 2.5.x I would recommend to set this to auto (which > allows any mode, including non-TLS) or auto_no_plain which > allows any mode but non-TLS. > > More details can be found e.g. here: > > https://wiki.xiph.org/Icecast_Server/known_https_restrictions#Icecast2_2.5.x_.28branch_.22master.22.29 > > If there is general interest in this I can talk a little bit about this > on Friday as well. > > > > > > > >
> >
> /> > > > > > > > > > > > > > > > > > > > > > > > > > > someip > > someport > > /coolvibes.ogg > > /strawbs.ogg > > 0 > > > > 0 > > > > If you're using recent 2.5.x you can also use > http://example.org/blubb here for the upstream address. > > > > > > > > > > > > > > /live.mp3 > > In this block you set a real huge amount of options. I guess most of > them can go. Some are set to the default value (e.g. you set size> to the same value as the global default). Some should be avoided > unless there is a real requiement (e.g. <*type*>, <*metadata*>, > <*header*>, , ...). And for some I'm not sure if you actually > use them (, , ). > > Generally speaking use as little options as possible. > > > > someusername > > someexamplepass > > 900 > > 3600 > > /tmp/dump-example1.ogg > > /intro.ogg > > /stream.ogg > > 1 > > 1 > > ISO8859-1 > > 1 > > somestream > > 'hello' > > someurl > > World > > 160 > > application/mp3 > > mp3 > > 1 > > 65536 > > 4096 > > > > > > > > > Not sure where you got this block from. > Generally the htpasswd type takes an option with the filename. From the > 2.4.4 example: > > > > The filename is relativ to Icecast's cwd (after chroot if any). So > depending on your setup you might want to set it absolute. > > > > > > >
> >
> >
> >
> > > > /home/icecast/bin/source-start > > /home/icecast/bin/source-end > > > > > The rest below is 2.4.x style config. Nothing wroth with it even for > 2.5.x. But it might be a bit nicer to read/work with in 2.5.x style. > > > 1 > > > > > > ./log > > ./web > > ./admin > > Relative paths here look a bit like you try to run it not as a service. > I would avoid this outside of testing. > > > > > > > > > > > > > > > > > > > > > > 0 > > > > > > Having changeowner active is not the nicest thing. Unless you need the > extra permissions for e.g. binding to a privileged port I would suggest > to not use this. If running as a service it is best to let the > operating system change to the correct user before starting Icecast. if > running ?n a more test setup sudo/doas -u works very nice to switch to > the target user. > > > > user > > users > > > > > > > > > > > > access.log > > error.log > > > > 4 > > 10000 > > > > > > > > > > > With best regards, > > -- > Philipp Schafft (CEO/Gesch?ftsf?hrer) > Telephone: +49.3535 490 17 92 > Website: https://www.loewenfelsen.net/ > Follow us: https://www.linkedin.com/company/loewenfelsen/ > Gesch?ftsf?hrer/CEO: Philipp Schafft > > L?wenfelsen UG (haftungsbeschr?nkt) Registration number: > Bickinger Stra?e 21 HRB 12308 CB > 04916 Herzberg (Elster) VATIN/USt-ID: > Germany DE305133015 > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: