How To Setup Kaltura CE 4.0 VMWare Image in 15 minutes

This post is no longer relevant. Please see for Kaltura CE howtos and guides.
Various forum threads (@, @, @) discussed issues with the VMWare image of Kaltura CE 4.0. The following video tutorial will guide you how to install Kaltura CE 4.0 VMWare image in 15 minutes.
In the video, we deliberately re-created most of the problems users encountered while setting up the VMWare image. The fixes mentioned in this video also apply to the generic Kaltura Server installation and are not specific to the VMWare image installation (We’ll make sure that in the next release these are simplified and fixed).
Two problems that the video solves particularly are the logs and cache folder permissions and the Sphinx localhost issue.
Now set your clocks, follow the video and in 15 minutes you’ll be good to go.

[kaltura-widget uiconfid=”6420041″ entryid=”1_1hzciy7o” width=”551″ height=”330″ addpermission=”” editpermission=”” /]CE 4.0 VMWare Image Setup Video Tutorial

The logs and cache folder permissions problem
In order to fix the logs and cache folder permissions problem, you must first generate it; Access the server management via the KMC or the Admin Console, that will populate the logs and cache folders. Then to solve the issue, increase permissions on those folders running the following commands

chmod 777 -R /opt/kaltura/log
chmod 777 -R /opt/kaltura/app/cache

The above is a good troubleshooting tip for most issues.

<div class=”trd-ph-embedded” data-group=”Upper_embedded_CTA”></div>

The Sphinx issue 
The Sphinx issue is raised when you log in to KMC content tab and then presented with the following error message: “Internal Server Error”  before any content is visible. This happens because Sphinx (the indexing & search server Kaltura uses) is required to retrieve entries metadata. When not properly setup and run, the Media.list API call will fail. To resolve this issue, verify that sphinx is running on your server by running the following command: ps -ef | grep searchd
If searchd doesn’t come up on the grep results, to start sphinx run the following:

./opt/kaltura/bin/sphinx/searchd --config /opt/kaltura/app/configurations/sphinx/kaltura.conf

The Video Instructions in a list – Setting up Kaltura CE 4.0 VMWare image

  1. Go into
  2. Register as a user or log in
  3. Press the Kaltura CE Download link
  4. Download the Kaltura CE4 VMware image
  5. Wait for the download to finish
  6. Open the VMWare image installation guide
  7. Open the Set the VMWare image guide
  8. Unzip the image using WinRar
  9. Download and install VMWare Player
  10. Open the VMWare Player
  11. Change the network, disk and processors settings
  12. Open the Kaltura CE 4.0 image
  13. Follow the step by step guide on the VMWare image installation doc
  14. Login to the image using user: root, password: kaltura
  15. Run the following commande: ifconfig – and copy the your ip address
  16. Edit c:/windows/system32/etc/hosts file and add: local.ce (note the space between the ip and local.ce)
  17. Run the following command: php /opt/kaltura/installer/configure.php
  18. Run the following command: vim /etc/hosts (this will open the vim editor and edit the /etc/hosts file)
  19. Add the following line: local.ce (note the space between the ip and local.ce)
  20. Hit the Esc key, then type ‘:wq’ to save and exit.
  21. Add the following line: vim /etc/httpd/conf/httpd.conf
  22. Add the following line at the end of the file: include /opt/kaltura/app/configurations/apache/my_kaltura.conf
  23. Hit the Esc key, then type ‘:wq’ to save and exit.
  24. Run the following command: vim /opt/kaltura/app/alpha/config/kConfLocal.php
  25. Type /sphinx and then hit the N key to search for sphinx
  26. Instead of change to localhost (this will solve the Sphinx issue)
  27. Hit the Esc key, then type wq to save and exit.
  28. To restart the Apache service, run the following command: service httpd restart
  29. Head your browser to the following address: https://local.ce/start
  30. Click the links to Admin Console and the KMC (the Kaltura Management Console)
  31. Close the Admin Console and KMC tabs.
  32. Note that you’ll see the errors, as logs and cache are being created
  33. Run the following command: chmod 777 -R /opt/kaltura/log
  34. Run the following command: chmod 777 -R /opt/kaltura/app/cache
  35. Head your browser to the following address: https://local.ce/start
  36. Open the Admin Console
  37. Add a new Kaltura Publisher
  38. In the Publishers list, select Manage in the actions drop-down for the new publisher account
  39. All done. Enjoy your new Kaltura Server 🙂

Help us make the next version better by sharing in the comments below any other problems you may have encountered.

Let's Get Going