Hey there, I’ve since moved the domain over to another host to try to set up a secured landing page-style site with the iframe embed code (the embed code’s not currently playing nice with a WP install + Divi theme for whatever reason).
This one I have NOT used certbot, but the original install I was referring to did. I used certbot, got 100% install success, and then installed libretime/icetime. it was never secured via https.
In addition, importing podcasts did not work (a major requirement for the station), hence why I reinstalled on another VPS box later.
Thanks, but no dice. The ServerName flag appears lower in my file anyway, but I added it up there instead just in case, but it didn’t work. This is really weird — I have no idea what to try next…
Yes, the DNS is absolutely pointing to the right IP address.
When I try https://www.radiowrite.com/ I get shown a Wordpress site, which seems to be on the same ip address. Have you tried to turn off that site? If that is on the same server, then it might interfere with Libretime.
No, they’re two completely different servers. I changed the domain to point to the WP install after finally giving up with SSL… when you responded at first, I switched it back to mess around again. So you should be seeing the libretime install, not WP.
Edit: I added 443/tcp to the firewall and things are working. Please advise as to anything else I may have forgotten, and/or if this is not the proper way to do things.
Chrome, therefore, refuses to play the stream, as it’s “Mixed content.” Does anyone actually know if there’s a way to set this up so that Libretime AND the stream can be secured via SSL?
Libretime has to be configured to use a non SSL stream, then in the website you must use the SSL configured port. Check this website: https://basatisound.com as an example.
And this are the instructions to compile icecast with openssl support:
apt update && apt install icecast2
apt remove icecast2
# Install the development tools required to build Icecast from source
apt install git gcc build-essential
# Now some of the dependencies required to compile Icecast from source
apt install libcurl4-openssl-dev libxslt1-dev libxml2-dev libogg-dev libvorbis-dev libflac-dev libtheora-dev libssl-dev
cd /usr/src
# git clone --recursive https://gitlab.xiph.org/xiph/icecast-server.git
wget https://ftp.osuosl.org/pub/xiph/releases/icecast/icecast-2.4.4.tar.gz
tar zxvf icecast-2.4.4.tar.gz
# Move into the source directory and prepare the configuration script
# cd icecast-server; ./autogen.sh
cd icecast-2.4.4/;
# Configure the source code with SSL support enabled
./configure --with-curl --with-openssl
# If you have a 4-core ARM, let’s use all 4 of them:
# make -j 4
# Otherwise, stick with your single core
make
# Install Icecast:
make install
# Suponemos que hay un certicado creado ya en /etc/ssl/certs/icecast2.pem, y así lo indicaremos en el archivo icecast2.xml: <ssl-certificate>/etc/ssl/certs/icecast2.pem</ssl-certificate>. Nota: el certificado generado con ACME no funciona
# Create symbolic links to the old repository version of Icecast2, so that we can use the /etc files:
ln -s /usr/local/bin/icecast /usr/bin/icecast2
ln -s /usr/local/share/icecast /usr/share/icecast2
# Finally start icecast
service icecast2 restart