500 Internal Server Error - KMC

Hi everyone!,
I installed the kaltura, and the get first page of the “Get Started!”,
BUT, when i click on the link to KMC, i get this error:
"symfony PHP framwork
page not found

Oops! An Error Occurred
The server returned a “500 Internal Server Error”.

I search for solution for this error but nothing helped me…

Thank’s !!


Lets start with running:
# . /etc/profile.d/kaltura*base.sh
# kaltlog

In the shell, while making the request and look at the output.
Also, use an HTTP sniffer and check what call causes the HTTP 500

Then we can proceed.

In ./etc/profile.d there isn’t “kaltura_bash.sh” … there are other thing but not that…

what to do?


Typo. its /etc/profile.d/kaltura_base.sh

Also not there…
There is :

You mean one of them?

Should have:
# rpm -qf /etc/profile.d/kaltura_base.sh

I am not using red-hat. I’m using ubuntu. I could install rpm to manage alien packages, however, that is error prone. Is there a similar command with apt-get or using deb?


# dpkg -S /etc/profile.d/kaltura-base.sh
Should return:
kaltura-base: /etc/profile.d/kaltura-base.sh

Then you need to source:
# . /etc/profile.d/kaltura-base.sh

Note there is a pace between ‘.’ and /etc/profile.d/kaltura-base.sh.

Then run kaltlog and a sniffer and see what you get.

Hello Team,

I am facing the same problem while trying to open KMC page.

"symfony PHP framwork
page not found

Oops! An Error Occurred
The server returned a “500 Internal Server Error”.

kindly help if this problem is resolved at yuur end.


In the shell on the server, run:
# . /etc/profile.d/kaltura*base.sh
# kaltlog

Then make the request and look at the log to find the error.
In parallel, also open the dev tools in your browser and look at the errors under the console and network tabs. Once you have the error, we can take from there.

This error means there is a problem on the server side. A Server Error can be caused by any number of things from uploading the incorrect file to as bug in a piece of code. This error response is a generic “catch-all” response. The web server is telling you that something went wrong, but it’s not sure exactly what that is. If you have root access, you should review your web server’s error logs to get more information about this. If you are using shared hosting plan, you should contact your host to get more information. The best way to debug the error depends upon the server and what’s actually running at the time. Consider some debugging tips to help diagnose and fix common causes of this problem.