en en en en es en ru pl en en en en pl es en ru pl en en en en pl en en en en fr en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en da en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en de en de en en fr en en en en en en en en en en en ht ko en en en ht ko en en en en en en en la it en en en en en en it en en en en en en en en en it en en en en it en en en en it en en en en en en it en en en en fi it en en en en en en en en it en en en en en en en en en en en en en en en en en en en en en en en de en en en en en en en en de en en en en en en en en it en en en en nl en en en en en en en en en en en en en en en en ia tr
I had many questions in my previous topic about the ssl configuration in Ubuntu or CentOS. So i decided to update this, create new installers and see if the configuration of SSL has changed. And indeed it had. I prefer Ubuntu myself, but i use CentOS as well. It’s up to you which OS you want to use.
This second post will be the configuration of LetsEncrypt on Ubuntu 18.04 LTS
See this page: Wowza 4.8.x CentOS 7 Letsencrypt  for the CentOS version
Feel free to place a comment (comments will be approved first, to avoid spam).
The procedure for 20.04 is almost the same except for the creation of the SSL certificate. Everything else is the same as on a Ubuntu 18.04 installation. I still decided to create a new post for this, just in case if specific OS problems occur.
Ubuntu 20.04 LTS server installed
Firewall open ports: 8088, 8090, 443, 80, 1935
a domainname pointing to your wowza server (we need this for SSL activation)
What will i show you:
Installation of letsencrypt on Ubuntu Server
SSL converter to JKS file
configuration of frontend (playback) and backend (enginemanager) over SSL
Testing  of playback url’s (vlc, jwplayer)
Your server might have an increase of virtual memory because of the ssl encryption in your stream(s).
Always test this in your test environment. Don’t keep me responsible for it. This is a guide as is.
Open an ssh connection to your Server and run scripts as root
Note: Certbot-auto will not be supported on Ubuntu 20.04 so this command has slightly changed comparing to 18.04
Set 2 cronjobs so the ssl certificate will be updated automatically
# crontab -e @weekly root cd /opt/letsencrypt && git pull >> /var/log/letsencrypt/letsencrypt-auto-update.log @monthly root /opt/letsencrypt/ certbot certonly --quiet --standalone --renew-by-default -d SUB.DOMAIN.EXT >> /var/log/letsencrypt/letsencrypt-auto-update.log
Wowza needs an JKS file. So we need to convert our just created ssl certificate to a JKS file. On the github page of robymus you can find the script. We will use version 0.2
# Go to the wowza directory cd /usr/local/WowzaStreamingEngine/lib # Download the jar file in the lib directory wget https://github.com/robymus/wowza-letsencrypt-converter/releases/download/v0.2/wowza-letsencrypt-converter-0.2.jar # Create a jks file java -jar wowza-letsencrypt-converter-0.2.jar -v /usr/local/WowzaStreamingEngine/conf/ /etc/letsencrypt/live/ # This file will be created in the /usr/local/WowzaStreamingEngine/conf/ directory (jksmap.txt and the jks file).
We now need the contents of the jksmap.txt (copy them to a temporary notepad).
cat /usr/local/WowzaStreamingEngine/conf/jksmap.txt # This will show you something like this: SUB.DOMAIN.EXT={"keyStorePath":"/usr/local/WowzaStreamingEngine/conf/SUB.DOMAIN.EXT.jks", "keyStorePassword":"secret", "keyStoreType":"JKS"}
Now we need to enable 443 in the VHost.xml file
cd /usr/local/WowzaStreamingEngine/conf vi VHost.xml
You will see that the 443 is in comment tags   at the end of the HostPort. Remove those tags.  Second is that we have to change the KeyStorePath and KeyStorePassword in this part
${com.wowza.wms.context.VHostConfigHome}/conf/keystore.jks   [password]   JKS      TLS   SunX509         false
And after we have changed the settings. Also make sure to change SUB.DOMAIN.EXT to your own domainname.
${com.wowza.wms.context.VHostConfigHome}/conf/SUB.DOMAIN.EXT.jks   secret   JKS      TLS   SunX509         false
Save the file after you have made the changes.
The last thing before restarting is to change the tomcat properties
vi /usr/local/WowzaStreamingEngine/manager/conf/tomcat.properties #Change the default values #httpsPort=8090 #httpsKeyStore=conf/certificate.jks #httpsKeyStorePassword=[password] #httpsKeyAlias=[key-alias] # TO: httpsPort=8090 httpsKeyStore=/usr/local/WowzaStreamingEngine/conf/SUB.DOMAIN.EXT.jks httpsKeyStorePassword=secret #httpsKeyAlias=[key-alias]
Now we will restart Wowza
systemctl restart WowzaStreamingEngineManager systemctl restart WowzaStreamingEngine
The configuration is almost done.
Open your browser and instead of using the http://wowza-server:8088/enginemanager now change this to https://wowza-server:8090/enginemanager
That should give you a valid certificate. Also login in to the enginemanager. We have to do some extra steps there.
Go to Server > Virtual Host Setup and click Edit
If you don’t see port 443 as a Host Port, create it and fill in the fields . Here you have to set the location of the SSL jks file and the password. Change SUB.DOMAIN.EXT to your domainname.
Click Apply to save settings
At this point we are done. To be sure restart wowza or your complete server.
Normally via Adobe Media Live or OBS you can stream via RTMP (which is not over ssl). So make sure to stream the http port (1935  by default is http)
If you want to use another port then 1935 add it as an host port and make sure to add the port also to your Firewall (inbound)
In this case i also enabled SSL for port 1935, so these are my new url’s i can use:
#SSL over the default port (443) https://SUB.DOMAIN.EXT/vod/mp4:sample.mp4/playlist.m3u8
I make use of a free edition of JWPlayer. I added the livestream url (https) in the player and run the player via a javascript on my website.
The second stream is the https stream in vlc.
Click on the image for a larger view
Please feel free to give it a try. If you have any questions, just leave a comment.
The ssl certificate can’t authenticate on port 80 ?
First check if the ports are open on your server:
lsof -i -P -n | grep LISTEN # it should return the open ports on your server. sshd 2028 root 3u IPv4 28753 0t0 TCP *:22 (LISTEN) sshd 2028 root 4u IPv6 28764 0t0 TCP *:22 (LISTEN) systemd-r 4703 systemd-resolve 13u IPv4 37166 0t0 TCP 127.0.0.53:53 (LISTEN) java 658615 root 57u IPv4 434159 0t0 TCP *:8088 (LISTEN) java 658615 root 62u IPv4 434163 0t0 TCP *:8090 (LISTEN) java 658737 root 10u IPv4 434357 0t0 TCP *:35501 (LISTEN) java 658737 root 108u IPv4 435335 0t0 TCP *:8087 (LISTEN) java 658737 root 117u IPv4 434496 0t0 TCP *:8083 (LISTEN) java 658737 root 120u IPv4 434511 0t0 TCP *:1935 (LISTEN) java 658737 root 124u IPv4 434515 0t0 TCP *:443 (LISTEN) java 658737 root 128u IPv4 434519 0t0 TCP *:8086 (LISTEN)
If it doesn’t show port 80,443,8090, 1935 you have to check your firewall to open these ports.
Of course i’m willing to help, but i need information for that.  Which steps did you do, what is the error you get,  Then feel free to leave a comment.
If the installation works for you i would also like to hear.
You may also like...
SSL Letsencrypt on Wowza 4.x Server – Frontend + Backend
Wowza 4.8.x – CentOS7 – Letsencrypt
Wowza changed developer license model
new follow-up comments new replies to my comments
I have ubuntu 20.10 and wowza 4.8.12 installed. but this method did not work for me. any help?
Can you give me a bit more detail where you have problems. Which steps don’t work?. I will see if i can run a test setup. I thought 20.10 didn;t exist, but it did haha. But i see 2010 is already EOL as of july 2021, so i advise you to upgrade. I only run LTS versions.
Did you also patch your wowza version because of the Log4j exploids?. Make sure to do that. Please check my github page for more info on that.
Already replied here: https://vanmarion.nl/blog/blog/wowza-4-8-x-ubuntu-20-04-lts-letsencrypt/
java -jar wowza-letsencrypt-converter-0.2.jar -v /usr/local/WowzaStreamingEngine/conf/ /etc/letsencrypt/live/ is is not working in my machine while i have install javaVoluptate perferendi.
Configuring SSL For Wowza Streaming Engine Using Letsencrypt On Windows 10 – Grahil
[…] Written with inspiration from the original post on thia topic targeting Ubuntu at maca’s blog. […]
Reply to  Configuring SSL For Wowza Streaming Engine Using Letsencrypt On Windows 10 – Grahil
I think many users will find it useful. Thx for the link and referral. Highly appreciated!
STEP: # Create a jks file
Read error in initialization:/etc/letsencrypt/live
Error reading certificates, aborting without writing anything
Can you check if the file wowza-letsencrypt-converter-0.2.jar is present in your /usr/local/WowzaStreamingEngine/lib directory?
Next story Wowza 4.x – AudioRepeater 2 Module [EOL]
Previous story Wowza 4.8.x – Ubuntu 18.04 – Letsencrypt
Wowza changed developer license model
Wowza 4.x / Wowza Modules
Wowza 4.x – AudioRepeater 2 Module [EOL]
Wowza 4.8.x – Ubuntu 20.04 LTS – Letsencrypt
Wowza 4.8.x – Ubuntu 18.04 – Letsencrypt
Wowza 4.8.x – CentOS7 – Letsencrypt
Wowza StreamingEngine 4.x Installation
SSL Letsencrypt on Wowza 4.x Server – Frontend + Backend
Wowza 4.8.x – CentOS7 – Letsencrypt
Wowza 4.8.x – Ubuntu 18.04 – Letsencrypt
Enecsys Dashboard / Rpi
Enecsys Image for pvoutput V2.0
Maca's Blog © 2022. All Rights Reserved.
Powered by  - Designed with the Hueman theme
This website uses cookies to improve your experience on our website. Tracking data is anonymous. Close & Accept Read More
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.