Wowza 4.8.x – Ubuntu 18.04 – Letsencrypt

Update june 19, 2023: I have created an update series for Letsencrypt. Please follow the new tutorial.

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).

If you need a clean install of Wowza Streaming Engine on Ubuntu 18.04 LTS  then checkout the installer scripts: which i have created  Those includes Firewall (CSF), Java 11 and Wowza installation. All you need is a valid license key or developer key. 


  • Ubuntu 18.04 LTS server installed
  • Wowza 4.8.x 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)

Keep in mind:

  • 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.

Start of installation

Open an ssh connection to your Server and run scripts as root 

# update your server
apt-get update && apt-get upgrade -y
apt-get install git

# clone the certbot repository and configure certbot
git clone /opt/letsencrypt
cd /opt/letsencrypt

# create an SSL certificate. change SUB.DOMAIN.EXT to the domain that points to your server
sudo -H ./letsencrypt-auto certonly --standalone -d SUB.DOMAIN.EXT --key-type rsa

# Some questions will be asked. Fill them in accordingly
# Answer some of the questions:
enter email: set-your-email
agree TOS(Terms of Service): A
Share your email: (up to you): N

Set 2 cronjobs so the ssl certificate will be updated automaticly

# crontab -e
@weekly root cd /opt/letsencrypt && git pull >> /var/log/letsencrypt/letsencrypt-auto-update.log
@monthly root /opt/letsencrypt/letsencrypt-auto 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.1

*Minor update april 6 2021. replaced the 0.1 version with 0.2. The procedure hasn’t changed

# Go to the wowza directory
cd /usr/local/WowzaStreamingEngine/lib 

# Download the jar file in the lib directory

# 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 <!–  and –> at the end of the HostPort. Remove those tags.  Second is that we have to change the KeyStorePath and KeyStorePassword in this part



And after we have changed the settings. Also make sure to change SUB.DOMAIN.EXT to your own domainname.


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/

#Change the default values


# TO:


Now we will restart Wowza

service WowzaStreamingEngineManager restart
service WowzaStreamingEngine restart

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. 

Encoder configuration

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)

Playback url’s



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)

Screenshot example. 

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. 

If it doesn’t work for you, try to give as much detail as possible. (It doesn’t work isn’t enough).

You may also like...

0 0 votes
Article Rating
Notify of

Newest Most Voted
Inline Feedbacks
View all comments
Ian Liuzzi-Fedun
Ian Liuzzi-Fedun
4 years ago

While creating the cert I’m being told that it can’t bind to port 80. Would I have to stop any Wowza services while doing this?

Ian Liuzzi-Fedun
Ian Liuzzi-Fedun
Reply to  maca
4 years ago

I’d say 80 is forwarded. Check it out:

3 years ago

Is it necessary to recreate the JKS file after every letsencrypt renewal?

3 years ago

can you pls check they have update the letsencrypt, I am getting these error dear,

[root@server222 letsencrypt]# sudo -H ./letsencrypt-auto certonly –standalone -d
Skipping bootstrap because certbot-auto is deprecated on this system.
Your system is not supported by certbot-auto anymore.
Certbot cannot be installed.
Please visit to check for other alternatives.
[root@server222 letsencrypt]#

3 years ago

Robert Elek (robymus) recomended use v0.2
What do you think about?

3 years ago

Thank you for this tutorial. I have an old Wowza perpetual license and used their streamlock server for the ssl cert. But my cert expired (my fault for ignoring emails) and Wowza was not interested in helping me because I’m not paying them.

Anyway, your tutorial and github page saved the day. You can check out our live stream on

3 years ago

Thanks for documenting this, really helpful.

I needed to install Certbot using their snapd guide as the auto install didn’t work. I also had to register the Wowza java install using update-alternatives

sudo update-alternatives --install /usr/bin/java java /usr/local/WowzaStreamingEngine/jre/bin/java 1
2 years ago

I have ubuntu 20.10 and wowza 4.8.12 installed. but this method did not work for me. any help?

2 years ago

Hi can you help me installed wowza on pc, when you installed icecast it stops working how do I get it to work on ubuntu 20 icecast and wowza

1 year ago

Hello, I’ve been following your tutorials for a long time.
And I would like to thank you for everything, your work helps me to this day.

I wanted to ask you for some help, my Wowza Media Server on Ubuntu Server has an expired certificate and I can’t renew it, when I run the command to convert the certificate, using the command that calls java in the LIB folder. It gives a key error and cannot copy the certificate files that were renewed.

My Wowza I changed port 80 and 443.

Would you help me ?