HTTPS ‘upgrades’ to web browsers have made my locally generated BA1 webstreams all but impossible for the non-technical types to tune in. I want to make the BA1 audio streams we’ve been running for a couple of years able to run as HTTPS so that the average user can hear us. A few of our diehard fans have gotten set up to hear us, but many more get nothing when they tune us in at http://supercfl.ddns.net:20111 . Anybody with a hint or useful link to get me going?
Usually the stream provider/host will offer SSL as an option to add to your streams. Shouldn’t be a big issue. I don’t think you’re hosting your own streams, so you would only need to update the encoder to send the stream to the new https url they provide to you. You would then need to update all your stream links on all the listing services. Ultimately, it’s on your stream host to get that setup for you.
You’ll need to read up on how to get an SSL cert added to your server. There should be plenty of documentation out there.. Are you using IceCast or ShoutCast?
I am hosting my own stream, but use the free VLC app as the receiver on both smartphones when travelling and my laptop at home. No problems encountered.
VLC works on my stream as well. As does Firefox if I turn off the site safety. I’m trying to get HTTPS compliant for the nervous types. There are tons of pages telling me how to get HTTPS on my server, but so far nothing has fixed the problem. I’ve been poking at it for about 2 years now and was hoping somebody who uses BA1 was also hosting their own stream and could tell me that it can be done. Offsite hosts also seem unable to pick up this stream even though I can hear it and have a few listeners who obviously can hear it. So yes, I’m aware of many pages of HTTPS instructions. So far I have not had success using them and am pretty much done with the whole mess. This is my last gasp effort before I just accept limited listenership online via BA1 direct streaming and go back to the ever annoying Icecast 2 server that works when it feels like it.