[Icecast] Problem with SSL

[Ervin Bizjak]

I don't need SSL in localhost. Icecast runs on my computer, without a
website or domain. The stream is accessible to the public via IP address.

Why SSL? Because Chrome no longer supports http connections.

I don't mean two different radios, but one, which is now accessible on
8080, and from now on it would only be on 8443.

Is there perhaps another solution?

Ervin

V V ned., 12. jan. 2025 ob 20:18 je oseba Thomas Schmidt <
schmidt at netaction.de> napisala:

> Hi Ervin!
>
> > The problem is that it shows the same number of listeners on both
> connections.
>
> > My configuration is:
> >    <!-- You may have multiple <listener> elements -->
> >     <listen-socket>
> >         <port>8080</port>
> >         <!-- <bind-address>127.0.0.1</bind-address> -->
> >         <!-- <shoutcast-mount>/stream</shoutcast-mount> -->
> >     </listen-socket>
> >
> >     <listen-socket>
> >         <port>8443</port>
> >         <ssl>1</ssl>
> >     </listen-socket>
>
> This configuration simply opens two ports for the exact same server.
> If you need independent radio stations and listeners on both ports,
> you have to start Icecast twice.
>
> Why do you need SSL on a local Icecast? Keep in mind the SSL
> implementation of Icecast is very buggy. For example, some connections
> never close, keeping them locked forever.
> https://gitlab.xiph.org/xiph/icecast-server/-/issues/2445
> You should use Icecast without SSL and usually for security reasons
> only on machines like localhost.
>
> Thomas
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20250112/f7e630ab/attachment.htm>