Kaltura CE 12.13.0 released

Hello all,

The latest version is now available.

kaltura-base (12.13.0) changelog:

  • PLAT-6942 - Clipped entry offset and duration are not retuned by Kaltura API
  • PLAT-7135 - Drop folder watcher not getting folders
  • PLAT-7163 - Race between old and new recording causes wrong call to cancelReplace
  • PLAT-7163 - Add media-server permission get permission
  • https://github.com/kaltura/server/issues/4411

kaltura-batch (12.13.0) changelog:

  • Added needed KAsyncDropFolderWatcher config

kaltura-nginx (1.10.3) changelog:

  • Set protocol for kalapi based on whether or not we’re working over SSL

To upgrade, please follow:

RPM based:

Deb based:

Or, if running a cluster:


I have followed the guide to install the latest version on a fresh install on CentOS 6.5, however nginx is failing to install. I am getting the error below.

Starting nginx: nginx: [emerg] invalid URL prefix in /etc/nginx/conf.d/kaltura.conf:24
ERROR: /opt/kaltura/bin/kaltura-nginx-config.sh failed:( You can re-run it when the issue is fixed.

I have viewed the file in question the line in question is below.

       proxy_pass ://kalapi/;

After some seraching i attempted to add http to the proxy pass

       proxy_pass http://kalapi/;

Saved and quit and attempted to re run /opt/kaltura/bin/kaltura-nginx-config.sh however i am still getting the same error, upon viewin the file in question after re running the above command the ‘http’ is not there.

Hi @amar,

Thank you for your report. You are most correct. There was a bug and I just fixed it and pushed kaltura-postinst-1.0.33-6.noarch.rpm to the 12.13.0 repo.
Since it’s on CDN, it may take a while to propagate but the fix is very simple so you can patch the file manually.
Please edit /opt/kaltura/bin/kaltura-nginx-config.sh and right before line 88 add:


Save it and rerun and it should be fine.

Please confirm.


Hey Jess

Yes patching the file manually has allowed me to get it working :slight_smile:

Many thanks

I have another single server install that we are using whilst we develop a front facing admin panel and video management panel. It is on on aws using centOs 6.5, after restarting the instance the ip address changed for the server and i then re ran the setup to align it with the new ip address however the only thing that isnt working on it is playing the media.

After some analysis i have noticed that it appears that the install is still looking at the old ip address when loading any passthrough streams or videos.

Im guessing that i will have to change this somewhere in the database.

Hi @amar,

Most welcome and thanks for reporting.
Yes, you need to update the records in the kaltura.delivery_profile MySQL table.
This is documented here:

Let me know if you come across any issues.


1 Like

That worked a treat everything is back up and running now


Glad to hear it, Amar.

Hi jess

Is it possible to run a newer version of ngninx with older version frontserver (kalapi) like 12.10 and kaltura-base 12.10 on the nginx-server or are there dependencies ?

Kind regards

Hi @roger78,

All API/front and batch servers must be of the same version across the cluster mainly since DB schema changes/additions are often made between versions.
You could usually use a newer kaltura-nginx package with older Kaltura Server versions but if something does not work, my first reply would be that you should upgrade. In general, it’s not recommended to mix and match. What’s the use case that’s making you contemplate such an approach?

Because I still struggeling with the setup of the nginx server and I thougth it would be better, if I install the newer
version 1.10.3 instead of 1.10.2 of nginx for the kaltura-xxx version 12.10

I cannot update my whole cluster because i would need a downtime for this and the risk somethis go wrong, which i cannot do it right now.

I usually test it on a single server before install it in the cluster.
My cluster environment is behind a ssl-offloading loadbancer.

Kind Regards

Hi @roger78,

I certainly understand and appreciate that upgrading any server ENV, esp. a clustered one, is an operation that you have to prepare for [as in create proper backups], do over the weekend [to avoid downtime] and also have a practised rollback plan. In that regard, Kaltura is no different than anything else… Since I have held plenty positions where that was done by me, I know the pains:)

However, it is still important to do. Not only from a bug fixing perspective but also, from a security standpoint.

That said, what exactly is the issue you have with your current Nginx version? I am sure we can solve it.

This topic was automatically closed after 8 days. New replies are no longer allowed.