How configure godaddy certificates in shoutcast

I have a radio station using centova and shoutcast, but i need to configure it with ssl, I acquired the godaddy certificatesbut i don’t know how i have to configure shoutcast, because google chrome said me that i have mixed content, i need help.
Thanks !
Ps: my english isn’t very good

My domain is: https://latamradio.com/

My web server is (include version): Linux AMI

The operating system my web server runs on is (include version):Linux

My hosting provider, if applicable, is: Route 53

1 Like

So if I'm understanding this correctly, you are using GoDaddy certificates and not Let's Encrypt certificates?

Personally, I don't feel like this community is for any TLS question. If you're not using Let's Encrypt certificates, I don't think this is the right forum for this question.

You might be in luck however and someone else feels differently about helping someone with GoDaddy certificates.

2 Likes

Ok, but i tried to use Let’s Encrypt certificates but i cant configure them.
Thanks for your answer and your time.

1 Like

Now I'm confused. Are you (trying to) using(/use) Let's Encrypt certificates in your current issue?

2 Likes

Yes, but when i did it i couldn’t configure it, so i buy the godaddy certificates.

1 Like

Well, a certificate is a certificate. Let’s Encrypt or GoDaddy, their configuration would have been exactly the same.

Further more, it seems SSL for Shoutcast Server Software is only for Premium customers? Although it’s strange that the article doesn’t even mention on how to install the cert into Shoutcast. It only mentions using the certbot-auto script (which isn’t recommended by the way for most systems) and it even puts the script in the wrong directory. Why would they put “binaries”/scripts directly in /etc/? That’s not the right place.

So no luck there.

2 Likes

As an aside, your website references some content from an IP address, so the website itself will show an error in some browsers because the content linked on the IP address is invalid for that certificate: https://3.221.20.192/wp-content/uploads/2019/09/cropped-back-radio-2.jpg

For shoutcast, it looks to me like you need to update your shoutcast server config to point to your certificate files. https://help.shoutcast.com/hc/en-us/articles/360003410493-Shoutcast-Server-Configuration-New-Features-

Regarding ACME/Let’s Encrypt, if you have Windows, you can use https://certifytheweb.com on your desktop, using dns-01, AWS route53 (see the DNS Authorization tab), then add a Deployment Task under Deployment to ssh/sftp the certificate files where you need them. You can also use certbot to do all that but I can’t help you there :slight_smile:


Looking at this more closely you seem to have it mostly configured… your https service on port 2199 is working fine (https://streaming.latamradio.com:2199/system/streaminfo.js) but your audio stream on port 8040 still needs to be configured somehow.

2 Likes

@AndresMartinez !

Looks to me like the Player is being called via http:// …
If you change the source to https:// on the player AND script that will be a step forward.

<audio width="200" height="50" src="http://streaming.latamradio.com:8030/;stream.nsv" type="audio/mp3" controls="" preload="auto" autoplay="" loop=""></audio>
	<script language="javascript" type="text/javascript" src="http://streaming.latamradio.com:2199/system/streaminfo.js"></script>

Hope that helps.
Rip

2 Likes

Thanks for your answer but, do you know what is the configuration file, i need to add the certificates path and i don’t know where do it !

1 Like

Thanks, i know it but, if i don’t configure ssl in shoutcast that change doesn’t work

1 Like

Sorry Andres you’re going to have to google that! It will be a .conf file, possibly where the other shoutcast files are, possibly in your home folder as ~/shoutcast or you may have a shoutcast user profile under /home/shoutcast - that’s just from googling the topic though, I don’t know anything about shoutcast.

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.