Skip to main content

Updated SSL Certificates on Site Players

I updated the ssl certificates with my dhoytt.com site certificates so you can stream from the website using my embedded players. I updated my overall site certificates earlier this month but failed to point stunnel the secure utility I use to keep you safe to my new certificate. Now all my embedded players here on dhoytt.com will play in your secure browsers and applications.

Find a button anywhere on my site like the one above and hit play to listen to my stream. The player above plays at 320kbps. There are several like this at various bit rates on the sidebars of my site that will play 192kbps, 128kbps or 64kbps. You can choose a ShoutCast or IceCast then they will stream securely in your browser or audio application.

If you want to drop the url in your stream use one of these secure URL’s in your favorite audio streaming application:

ShoutCast secure:
https:dhoytt.com:8002/320kbps
https://dhoytt.com:8002/192kbps
https://dhoytt.com:8002/128kbps
https://dhoytt.com:8002/64kbps

IceCast secure:
https://dhoytt.com:8032/320kbps
https://dhoytt.com:8032/160kbps
https://dhoytt.com:8032/128kbps
https://dhoytt.com:8032/64kbps

Now if your application or browser doesn't handle ssl you can use the following:

ShoutCast:
https://dhoytt.com:8000/320kbps
https://dhoytt.com:8000/192kbps
https://dhoytt.com:8000/128kbps
https://dhoytt.com:8000/64kbps

IceCast:
https://dhoytt.com:8030/320kbps
https://dhoytt.com:8030/160kbps
https://dhoytt.com:8030/128kbps
https://dhoytt.com:8030/64kbps

Change In Music Relay Ports for IceCast Streams Plus adding SSL to Streams

I am consolidating all my streaming ports to 8000 for ShoutCast unencrypted and 8002 for encrypted then IceCast non-encrypted streams to port 8030 with encrypted IceCast on port 8032 with the same mounts for all bit rates. I’m making this change not solely for the benefit of streaming ssl so modern browsers and some applications will not block the unencrypted streams I wanted less ports opened. I ad intended to do this for a while but had to prioritize and get my infrastructure in place first before implementing changes on top of that layer.

You can still stream at different bitrates but now to get the ssl version of the streams for IceCast you would use port 8032 instead of 8030 and 8002 for ShoutCast instead of 8000 for unencrypted.

Here’s a list of the streams you can type of copy and paste into your favorite application or browser (use encrypted for modern browsers) to play the music streams:

Icecast non-encrypted streams:

http://dhoytt.com:8030/320kbps

http://dhoytt.com:8030/160kbps

http://dhoytt.com:8030/128kbps

http://dhoytt.com:8030/64kbps

Icecast encrypted streams:

https://dhoytt.com:8032/320kbps
https://dhoytt.com:8032/160kbps
https://dhoytt.com:8032/128kbps
https://dhoytt.com:8032/64kbps

Shoutcast non-encrypted streams:

http://dhoytt.com:8000/320kbps

http://dhoytt.com:8000/192kbps

http://dhoytt.com:8000/128kbps

http://dhoytt.com:8000/64kbps

Shoutcast encrypted streams:

https://dhoytt.com:8002/320kbps
https://dhoytt.com:8002/192kbps
https://dhoytt.com:8002/128kbps
https://dhoytt.com:8002/64kbps

As I tend to, I made this a modular change and made it as robust as possible, I tried different methodologies using Apache and Nginx I was familiar with but ultimately opting to go with stunnel which seemed to work better for streaming unencrypted music without added modules. My embedded music players on the site will now have the appropriate encrypted music streams in them. Since my stream is sourced by my W2019 Data Center server and must interact with that applications encoder unencrypted I wasn’t sure how the binds to the network ports would behave on my Linux system I use to relay the streams but worked that out and things are looking good!