From webmaster at berean-biblechurch.org Tue Jun 2 01:34:36 2020 From: webmaster at berean-biblechurch.org (webmaster at berean-biblechurch.org) Date: Mon, 01 Jun 2020 20:34:36 -0500 Subject: [Icecast] Icecast Stream Keeps Repeating Sent Friday 29th May 2020 At: 16.19.hrs. GMT In-Reply-To: <02d18be7-4108-2eaf-785d-7b168664b560@coolmic.net> References: <897141340.37843.1590765607060@apps.talktalk.co.uk> <02d18be7-4108-2eaf-785d-7b168664b560@coolmic.net> Message-ID: <341082c9fbeebb188a99e323843c589e@berean-biblechurch.org> I've had this same problem. That is why I have been asking about how to remove the no-cache header. But no answer in the ether... Justin On 2020-05-29 11:48, Jordan Erickson wrote: > Hi, > > > On 5/29/20 8:20 AM, Les Durno wrote: >> However, when I stop my audio source, after some seconds, eg, ten, >> then >> once that audio stream has finished, after about six seconds the audio >> stream repeats playing, >> then does so after the same time interval, again for many times. Each >> time the volume of these >> repetitions, decreases. > > This sounds like a listener client issue. It makes sense to me, it > sounds like you're listening through a browser, is that correct? It is > likely re-playing through the cache it received since the stream > stopped > suddenly. The only thing that comes to mind is that your URL should be > unique per every stream instance (like if Icecast stops streaming then > starts again, generate a unique URL.) > > Take a look at this: > https://impactjs.com/forums/help/nocache-how-to-force-user-page-to-refresh-in-order-to-load-my-updated-changes/page/1 > > > Cheers, > Jordan > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From ross at stationplaylist.com Tue Jun 2 04:03:39 2020 From: ross at stationplaylist.com (Ross Levis) Date: Tue, 2 Jun 2020 16:03:39 +1200 Subject: [Icecast] Icecast Stream Keeps Repeating Sent Friday 29th May 2020 At: 16.19.hrs. GMT In-Reply-To: <341082c9fbeebb188a99e323843c589e@berean-biblechurch.org> References: <897141340.37843.1590765607060@apps.talktalk.co.uk> <02d18be7-4108-2eaf-785d-7b168664b560@coolmic.net> <341082c9fbeebb188a99e323843c589e@berean-biblechurch.org> Message-ID: <002901d63892$cdb15560$69140020$@com> How would caching the stream content in browsers be useful to anyone? It surely always needs to be set to no-cache. -----Original Message----- From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of webmaster at berean-biblechurch.org Sent: Tuesday, 2 June 2020 1:35 p.m. To: Icecast streaming server user discussions Subject: Re: [Icecast] Icecast Stream Keeps Repeating Sent Friday 29th May 2020 At: 16.19.hrs. GMT I've had this same problem. That is why I have been asking about how to remove the no-cache header. But no answer in the ether... Justin On 2020-05-29 11:48, Jordan Erickson wrote: > Hi, > > > On 5/29/20 8:20 AM, Les Durno wrote: >> However, when I stop my audio source, after some seconds, eg, ten, >> then >> once that audio stream has finished, after about six seconds the audio >> stream repeats playing, >> then does so after the same time interval, again for many times. Each >> time the volume of these >> repetitions, decreases. > > This sounds like a listener client issue. It makes sense to me, it > sounds like you're listening through a browser, is that correct? It is > likely re-playing through the cache it received since the stream > stopped > suddenly. The only thing that comes to mind is that your URL should be > unique per every stream instance (like if Icecast stops streaming then > starts again, generate a unique URL.) > > Take a look at this: > https://impactjs.com/forums/help/nocache-how-to-force-user-page-to-refresh-in-order-to-load-my-updated-changes/page/1 > > > Cheers, > Jordan > _______________________________________________ > 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 From webmaster at berean-biblechurch.org Tue Jun 2 23:09:00 2020 From: webmaster at berean-biblechurch.org (webmaster at berean-biblechurch.org) Date: Tue, 02 Jun 2020 18:09:00 -0500 Subject: [Icecast] Icecast Stream Keeps Repeating Sent Friday 29th May 2020 At: 16.19.hrs. GMT In-Reply-To: <002901d63892$cdb15560$69140020$@com> References: <897141340.37843.1590765607060@apps.talktalk.co.uk> <02d18be7-4108-2eaf-785d-7b168664b560@coolmic.net> <341082c9fbeebb188a99e323843c589e@berean-biblechurch.org> <002901d63892$cdb15560$69140020$@com> Message-ID: That is my question, but no-cache can cache parts of the stream, and that is why *I think* only no-store should be in the header. "If you mean to not store the response in any cache, use no-store instead." Justin On 2020-06-01 23:03, Ross Levis wrote: > How would caching the stream content in browsers be useful to anyone? > It surely always needs to be set to no-cache. > > -----Original Message----- > From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of > webmaster at berean-biblechurch.org > Sent: Tuesday, 2 June 2020 1:35 p.m. > To: Icecast streaming server user discussions > Subject: Re: [Icecast] Icecast Stream Keeps Repeating Sent Friday 29th > May 2020 At: 16.19.hrs. GMT > > I've had this same problem. That is why I have been asking about how > to > remove the no-cache header. But no answer in the ether... > > Justin > > On 2020-05-29 11:48, Jordan Erickson wrote: >> Hi, >> >> >> On 5/29/20 8:20 AM, Les Durno wrote: >>> However, when I stop my audio source, after some seconds, eg, ten, >>> then >>> once that audio stream has finished, after about six seconds the >>> audio >>> stream repeats playing, >>> then does so after the same time interval, again for many times. Each >>> time the volume of these >>> repetitions, decreases. >> >> This sounds like a listener client issue. It makes sense to me, it >> sounds like you're listening through a browser, is that correct? It is >> likely re-playing through the cache it received since the stream >> stopped >> suddenly. The only thing that comes to mind is that your URL should be >> unique per every stream instance (like if Icecast stops streaming then >> starts again, generate a unique URL.) >> >> Take a look at this: >> https://impactjs.com/forums/help/nocache-how-to-force-user-page-to-refresh-in-order-to-load-my-updated-changes/page/1 >> >> >> Cheers, >> Jordan >> _______________________________________________ >> 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 From daniel at pocock.pro Wed Jun 3 08:04:08 2020 From: daniel at pocock.pro (Daniel Pocock) Date: Wed, 3 Jun 2020 10:04:08 +0200 Subject: [Icecast] using Icecast source client as PulseAudio source Message-ID: <2361b21c-d1f5-b248-4c16-e7ba2b0e3d77@pocock.pro> There are many Icecast source clients[1] available now. The Coolmic[2] app is particularly interesting because it can turn a Android phone (e.g. SmartLav+ lapel mic[3]) into a wearable mic for presenters. Not everybody is keen to run Icecast though, some people may want to mix-and-match the Icecast source clients like that with some other broadcasting platform, Jitsi Meet[4], Zoom or whatever. Is there any documented way to make the Icecast source client appear as a source in PulseAudio so that any arbitrary application can use the sound feed as if it was a local microphone? For example, has anybody tried to do this with PulseAudio module-pipe-source[5] or module-tunnel-source[6]? We can already do stuff like this with video, for example, using the v4l2loopback kernel module with gstreamer. I provided a very trivial[7] script for that and it would be interesting to have a parallel example for audio. Regards, Daniel 1. https://icecast.org/apps/ 2. https://coolmic.net/ 3. https://www.rode.com/microphones/smartlav-plus 4. https://meet.jit.si 5. https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules/#module-pipe-source 6. https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules/#module-tunnel-source-new 7. https://gitlab.com/freertc/gstreamer-chroma-key From mustafejen at gmail.com Wed Jun 3 13:28:23 2020 From: mustafejen at gmail.com (Per Gunnarsson) Date: Wed, 3 Jun 2020 15:28:23 +0200 Subject: [Icecast] using Icecast source client as PulseAudio source In-Reply-To: <2361b21c-d1f5-b248-4c16-e7ba2b0e3d77@pocock.pro> References: <2361b21c-d1f5-b248-4c16-e7ba2b0e3d77@pocock.pro> Message-ID: If you want to pick up the sound from the icecast server mount point this should work: gst-launch-1.0 -v souphttpsrc location=https://mustafejen.se:8443/verket.opus ! decodebin ! pulsesink device="sndio-sink" In this case the audio is picked up from the icecast server, not directly from the icecast source client. If you want to pick up the audio within the source client itself maybe it's possible with pulsesrc (related to pulsesink). I don't know much about how Cool Mic works (even if I use it everyday) but I have had occasional contact with Cool Mic developers and they were real nice. My suggestion is that you look for the Cool Mic contact information: https://coolmic.net/contact/ Same goes for pulseaudio. Regards, Per Gunnarsson On 2020-06-03 10:04, Daniel Pocock wrote: > There are many Icecast source clients[1] available now. > > The Coolmic[2] app is particularly interesting because it can turn a > Android phone (e.g. SmartLav+ lapel mic[3]) into a wearable mic for > presenters. > > Not everybody is keen to run Icecast though, some people may want to > mix-and-match the Icecast source clients like that with some other > broadcasting platform, Jitsi Meet[4], Zoom or whatever. > > Is there any documented way to make the Icecast source client appear as > a source in PulseAudio so that any arbitrary application can use the > sound feed as if it was a local microphone? For example, has anybody > tried to do this with PulseAudio module-pipe-source[5] or > module-tunnel-source[6]? > > We can already do stuff like this with video, for example, using the > v4l2loopback kernel module with gstreamer. I provided a very trivial[7] > script for that and it would be interesting to have a parallel example > for audio. > > Regards, > > Daniel > > > 1. https://icecast.org/apps/ > 2. https://coolmic.net/ > 3. https://www.rode.com/microphones/smartlav-plus > 4. https://meet.jit.si > 5. > https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules/#module-pipe-source > 6. > https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules/#module-tunnel-source-new > 7. https://gitlab.com/freertc/gstreamer-chroma-key > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From webmaster at berean-biblechurch.org Mon Jun 8 23:53:57 2020 From: webmaster at berean-biblechurch.org (webmaster at berean-biblechurch.org) Date: Mon, 08 Jun 2020 18:53:57 -0500 Subject: [Icecast] best practice for high-latency connections Message-ID: What can be tweaked in the Icecast server to help users maintain a connection when on a high-latency connection? Would a queue-size (now 524288) adjustment help? burst-size is the default 64kb. Most of my listeners use iOS (phone or tablet); I don't know how many are on a cell connection. Sometimes I'll see a particular listener seem to have trouble because they'll try to force the stream to restart several times in a row (I have a button for that...) or they'll jump between mounts. I'm guess the issue is high-latency so the stream is dropping or momentarily cutting out, or they just have a bad net connection. Using my desktop as a client, disabling bursting seems to have no effect. Maybe because it has a high bandwidth connection? Justin -------------- next part -------------- An HTML attachment was scrubbed... URL: From pm at nowster.me.uk Wed Jun 10 21:53:01 2020 From: pm at nowster.me.uk (Paul Martin) Date: Wed, 10 Jun 2020 22:53:01 +0100 Subject: [Icecast] using Icecast source client as PulseAudio source In-Reply-To: <2361b21c-d1f5-b248-4c16-e7ba2b0e3d77@pocock.pro> References: <2361b21c-d1f5-b248-4c16-e7ba2b0e3d77@pocock.pro> Message-ID: <20200610215301.GB516753@thinkpad.nowster.org.uk> On Wed, Jun 03, 2020 at 10:04:08AM +0200, Daniel Pocock wrote: > Is there any documented way to make the Icecast source client appear as > a source in PulseAudio so that any arbitrary application can use the > sound feed as if it was a local microphone? For example, has anybody > tried to do this with PulseAudio module-pipe-source[5] or > module-tunnel-source[6]? pactl load-module module-null-sink sink_name=NULL pactl load-module module-remap-source master=NULL.monitor \ source_properties=device.description=VirtualMike Anything you feed into the NULL sink device will appear on the VirtualMike source. I've used it to feed live mixed audio from OBS into Zoom. -- Paul Martin From ervin.bizjak at gmail.com Thu Jun 11 11:18:08 2020 From: ervin.bizjak at gmail.com (Ervin Bizjak) Date: Thu, 11 Jun 2020 13:18:08 +0200 Subject: [Icecast] SSL-Question In-Reply-To: <1962600fa9d0520078e816e3f8011698@berean-biblechurch.org> References: <20190731124934.GA11538@aporee.org> <0d6c2bd6-0e06-f230-e89b-b3884387230a@yandex.com> <20190731135632.GE11872@aporee.org> <20190731144411.GE14677@aporee.org> <1962600fa9d0520078e816e3f8011698@berean-biblechurch.org> Message-ID: Hello! Sorry, but SSL in my windows where is installed icecast not work. Create certificate (.crt) and convert to .pem with openssl x509 -in mycert.crt -out mycert.pem -outform PEM certificate.pem copy to c:/icecast/cert/ Edit icecast.xml: ./cert/icecast.pem 8443 1 I don't know what can I do wrong V V pet., 2. avg. 2019 ob 03:47 je oseba napisala: > On 2019-07-31 09:44, unosonic wrote: > > Thomas B. R?cker: > >> After all, Icecast is just another web server. > >> > >> Please note the absence of 8000 and 8443. Neither are officially > >> specified for WWW type HTTP(S). They are commonly used as such, but 80 > >> and 443 are *much* better choices and should be preferred. > > > > makes sense, but if my webserver needs to serve http/s from the same > > IP, > > that would not work. Unless I want to use Icecast as a nginx or apache > > replacement ;) > > Uno, could you create a sub-domain, like radio.yoursite.com, and have it > point to the Icecast server? > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ervin.bizjak at gmail.com Thu Jun 11 11:34:50 2020 From: ervin.bizjak at gmail.com (Ervin Bizjak) Date: Thu, 11 Jun 2020 13:34:50 +0200 Subject: [Icecast] SSL-Question In-Reply-To: References: <20190731124934.GA11538@aporee.org> <0d6c2bd6-0e06-f230-e89b-b3884387230a@yandex.com> <20190731135632.GE11872@aporee.org> <20190731144411.GE14677@aporee.org> <1962600fa9d0520078e816e3f8011698@berean-biblechurch.org> Message-ID: Browser display: Secure connection failed An error occurred while connecting to localhost: 8443. PR_END_OF_FILE_ERROR The page you are viewing cannot be displayed because the received data cannot be authenticated. V V ?et., 11. jun. 2020 ob 13:18 je oseba Ervin Bizjak < ervin.bizjak at gmail.com> napisala: > Hello! > Sorry, but SSL in my windows where is installed icecast not work. > Create certificate (.crt) and convert to .pem with openssl x509 -in > mycert.crt -out mycert.pem -outform PEM > certificate.pem copy to c:/icecast/cert/ > Edit icecast.xml: > ./cert/icecast.pem > > 8443 > 1 > > > I don't know what can I do wrong > > V V pet., 2. avg. 2019 ob 03:47 je oseba > napisala: > >> On 2019-07-31 09:44, unosonic wrote: >> > Thomas B. R?cker: >> >> After all, Icecast is just another web server. >> >> >> >> Please note the absence of 8000 and 8443. Neither are officially >> >> specified for WWW type HTTP(S). They are commonly used as such, but 80 >> >> and 443 are *much* better choices and should be preferred. >> > >> > makes sense, but if my webserver needs to serve http/s from the same >> > IP, >> > that would not work. Unless I want to use Icecast as a nginx or apache >> > replacement ;) >> >> Uno, could you create a sub-domain, like radio.yoursite.com, and have it >> point to the Icecast server? >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chiapas at aktivix.org Thu Jun 11 11:36:33 2020 From: chiapas at aktivix.org (Chip) Date: Thu, 11 Jun 2020 12:36:33 +0100 Subject: [Icecast] SSL-Question In-Reply-To: References: <20190731124934.GA11538@aporee.org> <0d6c2bd6-0e06-f230-e89b-b3884387230a@yandex.com> <20190731135632.GE11872@aporee.org> <20190731144411.GE14677@aporee.org> <1962600fa9d0520078e816e3f8011698@berean-biblechurch.org> Message-ID: Hi This is for Linux but you might be able to find something useful in there for your situation: - https://serverok.in/centovacast-enable-ssl-on-icecast If you are using Letsencrypt then this, IMHO, is a good way to make the icecast.pem file: cat privkey.pem fullchain.pem > icecast.pem The above creates a useful SSL cert format which, for example, a range of devices are able to interpret. Hope that helps Chip Scooter On Thu, 11 Jun 2020 at 12:18, Ervin Bizjak wrote: > Hello! > Sorry, but SSL in my windows where is installed icecast not work. > Create certificate (.crt) and convert to .pem with openssl x509 -in > mycert.crt -out mycert.pem -outform PEM > certificate.pem copy to c:/icecast/cert/ > Edit icecast.xml: > ./cert/icecast.pem > > 8443 > 1 > > > I don't know what can I do wrong > > V V pet., 2. avg. 2019 ob 03:47 je oseba > napisala: > >> On 2019-07-31 09:44, unosonic wrote: >> > Thomas B. R?cker: >> >> After all, Icecast is just another web server. >> >> >> >> Please note the absence of 8000 and 8443. Neither are officially >> >> specified for WWW type HTTP(S). They are commonly used as such, but 80 >> >> and 443 are *much* better choices and should be preferred. >> > >> > makes sense, but if my webserver needs to serve http/s from the same >> > IP, >> > that would not work. Unless I want to use Icecast as a nginx or apache >> > replacement ;) >> >> Uno, could you create a sub-domain, like radio.yoursite.com, and have it >> point to the Icecast server? >> _______________________________________________ >> 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 ervin.bizjak at gmail.com Thu Jun 11 12:17:23 2020 From: ervin.bizjak at gmail.com (Ervin Bizjak) Date: Thu, 11 Jun 2020 14:17:23 +0200 Subject: [Icecast] SSL-Question In-Reply-To: References: <20190731124934.GA11538@aporee.org> <0d6c2bd6-0e06-f230-e89b-b3884387230a@yandex.com> <20190731135632.GE11872@aporee.org> <20190731144411.GE14677@aporee.org> <1962600fa9d0520078e816e3f8011698@berean-biblechurch.org> Message-ID: I copy certificate.crt and private.key to one file and this file convert to .pem. This is in icecast error.log: [2020-06-11 13:37:30] INFO main/main.c Icecast 2.4.4 server started [2020-06-11 13:37:30] INFO yp/yp.c YP update thread started [2020-06-11 13:37:30] WARN connection/connection.c Invalid private key file ./cert/icecast.pem [2020-06-11 13:37:30] INFO connection/connection.c No SSL capability on any configured ports V V ?et., 11. jun. 2020 ob 13:37 je oseba Chip napisala: > Hi > > This is for Linux but you might be able to find something useful in there > for your situation: > > - https://serverok.in/centovacast-enable-ssl-on-icecast > > If you are using Letsencrypt then this, IMHO, is a good way to make the > icecast.pem file: > > cat privkey.pem fullchain.pem > icecast.pem > > The above creates a useful SSL cert format which, for example, a range of > devices are able to interpret. > > Hope that helps > > Chip Scooter > > On Thu, 11 Jun 2020 at 12:18, Ervin Bizjak wrote: > >> Hello! >> Sorry, but SSL in my windows where is installed icecast not work. >> Create certificate (.crt) and convert to .pem with openssl x509 -in >> mycert.crt -out mycert.pem -outform PEM >> certificate.pem copy to c:/icecast/cert/ >> Edit icecast.xml: >> ./cert/icecast.pem >> >> 8443 >> 1 >> >> >> I don't know what can I do wrong >> >> V V pet., 2. avg. 2019 ob 03:47 je oseba < >> webmaster at berean-biblechurch.org> napisala: >> >>> On 2019-07-31 09:44, unosonic wrote: >>> > Thomas B. R?cker: >>> >> After all, Icecast is just another web server. >>> >> >>> >> Please note the absence of 8000 and 8443. Neither are officially >>> >> specified for WWW type HTTP(S). They are commonly used as such, but 80 >>> >> and 443 are *much* better choices and should be preferred. >>> > >>> > makes sense, but if my webserver needs to serve http/s from the same >>> > IP, >>> > that would not work. Unless I want to use Icecast as a nginx or apache >>> > replacement ;) >>> >>> Uno, could you create a sub-domain, like radio.yoursite.com, and have >>> it >>> point to the Icecast server? >>> _______________________________________________ >>> 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 pm at nowster.me.uk Thu Jun 11 14:28:16 2020 From: pm at nowster.me.uk (Paul Martin) Date: Thu, 11 Jun 2020 15:28:16 +0100 Subject: [Icecast] SSL-Question In-Reply-To: References: <20190731124934.GA11538@aporee.org> <0d6c2bd6-0e06-f230-e89b-b3884387230a@yandex.com> <20190731135632.GE11872@aporee.org> <20190731144411.GE14677@aporee.org> <1962600fa9d0520078e816e3f8011698@berean-biblechurch.org> Message-ID: <20200611142816.GB542968@thinkpad.nowster.org.uk> On Thu, Jun 11, 2020 at 02:17:23PM +0200, Ervin Bizjak wrote: > I copy certificate.crt and private.key to one file and this file convert to > .pem. That won't work. OpenSSL can't handle both the certificate and private key at once. Skip the OpenSSL step. Just cat the cert and private key together into a new file. -- Paul Martin From ervin.bizjak at gmail.com Thu Jun 11 14:39:23 2020 From: ervin.bizjak at gmail.com (Ervin Bizjak) Date: Thu, 11 Jun 2020 16:39:23 +0200 Subject: [Icecast] SSL-Question In-Reply-To: <20200611142816.GB542968@thinkpad.nowster.org.uk> References: <20190731124934.GA11538@aporee.org> <0d6c2bd6-0e06-f230-e89b-b3884387230a@yandex.com> <20190731135632.GE11872@aporee.org> <20190731144411.GE14677@aporee.org> <1962600fa9d0520078e816e3f8011698@berean-biblechurch.org> <20200611142816.GB542968@thinkpad.nowster.org.uk> Message-ID: I from zerossl.com download .zip file. In this file are: ca_bundle.crt, certificate.crt and V V ?et., 11. jun. 2020 ob 16:28 je oseba Paul Martin napisala: > On Thu, Jun 11, 2020 at 02:17:23PM +0200, Ervin Bizjak wrote: > > I copy certificate.crt and private.key to one file and this file convert > to > > .pem. > > That won't work. OpenSSL can't handle both the certificate and private > key at once. > > Skip the OpenSSL step. Just cat the cert and private key together into > a new file. > > -- > Paul Martin > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ervin.bizjak at gmail.com Thu Jun 11 14:40:07 2020 From: ervin.bizjak at gmail.com (Ervin Bizjak) Date: Thu, 11 Jun 2020 16:40:07 +0200 Subject: [Icecast] SSL-Question In-Reply-To: References: <20190731124934.GA11538@aporee.org> <0d6c2bd6-0e06-f230-e89b-b3884387230a@yandex.com> <20190731135632.GE11872@aporee.org> <20190731144411.GE14677@aporee.org> <1962600fa9d0520078e816e3f8011698@berean-biblechurch.org> <20200611142816.GB542968@thinkpad.nowster.org.uk> Message-ID: from zerossl.com download .zip file. In this file are: ca_bundle.crt, certificate.crt andprivate.key V V ?et., 11. jun. 2020 ob 16:39 je oseba Ervin Bizjak < ervin.bizjak at gmail.com> napisala: > I from zerossl.com download .zip file. In this file are: ca_bundle.crt, > certificate.crt and > > V V ?et., 11. jun. 2020 ob 16:28 je oseba Paul Martin > napisala: > >> On Thu, Jun 11, 2020 at 02:17:23PM +0200, Ervin Bizjak wrote: >> > I copy certificate.crt and private.key to one file and this file >> convert to >> > .pem. >> >> That won't work. OpenSSL can't handle both the certificate and private >> key at once. >> >> Skip the OpenSSL step. Just cat the cert and private key together into >> a new file. >> >> -- >> Paul Martin >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kurt+icecast at va1der.ca Mon Jun 15 01:55:52 2020 From: kurt+icecast at va1der.ca (Kurt Fitzner) Date: Sun, 14 Jun 2020 22:55:52 -0300 Subject: [Icecast] Can't play from iPhone Message-ID: I am having a terrible time getting an iPhone to connect to my stream. I am trying to connect through just a normal web browser (Safari) to my icecast 2.4.4 server. When I connect to the web page, the iphone doesn't see the