Tobias Gillström wrote: > Is the Icecast software running as a server-application and listening for > connections from clients on port 8000? > > I have no experience with audio streams and how they work, that is why I'm > asking the stupid question of how the Icecast software works and how it > connects. > > > [Icecast-server] > client=no > cert=fullchain.pem > accept=8443 ;listening for secure connections > connect=127.0.0.1:8000 ;makes unsecure connection to the Icecast software > listening on port 8000 on localhost > > > Den lör 11 mars 2023 18:30 <nathan.king(a)unpredictableporridge.co.uk> > skrev: > > > ringbretson@keplp.com wrote: > > I'm relatively new to stunnel, but I believe > > your connect should contain > > both IP and port. > > Like this. > > accept = 127.0.0.1:83 > > connect = 158.224.83.39:443 > > Thanks for that suggestion, ringbretson, appreciated. > > > > However, have tried to make that change, and because Icecast runs on Port > > 8443 securely, and have stunnel set to the same Port, receive a blocked > > Port error message, whether I start Icecast or stunnel first. > > > > Thanks for trying to help.
Essentially, yes, Tobias! Have Icecast server on W10, setup for connections on Ports 8443 and 8000, the encoder software streams the audio to the Internet via these Ports, and have stunnel setup to listen to Port 8443, from Icecast Server/econder, encrypt, and send out on Port 8000. At least, hope that is the case?! Cheers. _______________________________________________ stunnel-users mailing list -- stunnel-users@stunnel.org To unsubscribe send an email to stunnel-users-le...@stunnel.org