Cannot get to KMC login page after new install - flash issue

Hi,
I installed the Kaltura on CentOS 6.5 (upgraded to 6.6,). When I try to login to the KMC (192.168.1.10/kmc) I get a page saying : You must have flash installl in all browser, even chrome and even after installation.
192.168.1.10/admin_console - works great.

What to do in order to log in to kmc?

Thanks,
Alex.

kaltlog while trying to access the kmc page

]' in /opt/kaltura/app/infra/log/KalturaLog.php:82
Stack trace:
0 /opt/kaltura/app/ui_infra/InfraBootstrapper.php(113): KalturaLog::err('Class [EventNot...')
--
[2014-12-10 09:51:57]failed to connect [1] [0.00015997886657715] mysql:host=127.0.0.1;port=3306;dbname=kaltura_sphinx_log;
PHP Fatal error:  Uncaught exception 'PropelException' with message 'Unable to open PDO connection dsn[mysql:host=127.0.0.1;port=3306;dbname=kaltura_sphinx_log;] user[kaltura] password[nPqUQpIbvbVwrGA] [wrapped: SQLSTATE[HY000] [2013] Lost connection to MySQL server at 'reading initial communication packet', system error: 111]' in /opt/kaltura/app/vendor/propel/Propel.php:649
Stack trace:
#0 /opt/kaltura/app/vendor/propel/Propel.php(532): Propel::initConnection(Array, 'sphinx_log')
--
2014-12-10 10:08:22 [0.000515] [127.0.0.1] [504319702] [PS2] [sfView->initialize] INFO: {sfView} initialize view for "kmc/kmc"
2014-12-10 10:08:22 [0.000387] [127.0.0.1] [504319702] [PS2] [sfPHPView->renderFile] INFO: {sfView} render "/opt/kaltura/app/alpha/apps/kaltura/modules/kmc/templates/kmcSuccess.php"
2014-12-10 10:08:22 [0.000696] [127.0.0.1] [504319702] [PS2] [sfPHPView->decorate] INFO: {sfView} decorate content with "/opt/kaltura/app/alpha/apps/kaltura/templates/kmclayout.php"
2014-12-10 10:08:22 [0.000097] [127.0.0.1] [504319702] [PS2] [sfPHPView->renderFile] INFO: {sfView} render "/opt/kaltura/app/alpha/apps/kaltura/templates/kmclayout.php"
2014-12-10 10:08:22 [0.000469] [127.0.0.1] [504319702] [PS2] [sfRenderingFilter->execute] INFO: {sfFilter} render to client
--
2014-12-07 13:47:09 [1887927462] [addPermissionsAndItems.php] [addItemToPermissions] ALERT: exception 'Exception' with message 'ERROR - Permission name [] for partner [0] not found in database - skipping!' in /opt/kaltura/app/infra/log/KalturaLog.php:64
Stack trace:
#0 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(280): KalturaLog::alert('ERROR - Permiss...')
--
==> /opt/kaltura/log/batch/bulkupload-0-2014-12-07.err.log <==
PHP Notice:  Use of undefined constant DUPLICATE_CATEGORY - assumed 'DUPLICATE_CATEGORY' in /opt/kaltura/app/plugins/bulk_upload/xml/batch/BulkUploadEngineXml.php on line 1251
PHP Notice:  Use of undefined constant DUPLICATE_CATEGORY - assumed 'DUPLICATE_CATEGORY' in /opt/kaltura/app/plugins/bulk_upload/xml/batch/BulkUploadEngineXml.php on line 1251

--
==> /opt/kaltura/log/batch/validatelivemediaservers-0-2014-12-07.err.log <==
PHP Fatal error:  Uncaught exception 'KalturaException' with message 'Internal server error occurred' in /opt/kaltura/app/batch/client/KalturaClientBase.php:734
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(3996): KalturaClientBase->throwExceptionIfError(Array)
--
==> /opt/kaltura/log/batch/validatelivemediaservers-0-2014-12-10.err.log <==
PHP Fatal error:  Uncaught exception 'KalturaClientException' with message 'couldn't connect to host' in /opt/kaltura/app/batch/client/KalturaClientBase.php:357
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(3995): KalturaClientBase->doQueue()
--
2014-12-10 10:09:19 [0.000472] [10.61.41.125] [363753439] [PS2] [sfView->initialize] INFO: {sfView} initialize view for "kmc/kmc"
2014-12-10 10:09:19 [0.000401] [10.61.41.125] [363753439] [PS2] [sfPHPView->renderFile] INFO: {sfView} render "/opt/kaltura/app/alpha/apps/kaltura/modules/kmc/templates/kmcSuccess.php"
2014-12-10 10:09:19 [0.000688] [10.61.41.125] [363753439] [PS2] [sfPHPView->decorate] INFO: {sfView} decorate content with "/opt/kaltura/app/alpha/apps/kaltura/templates/kmclayout.php"
2014-12-10 10:09:19 [0.000208] [10.61.41.125] [363753439] [PS2] [sfPHPView->renderFile] INFO: {sfView} render "/opt/kaltura/app/alpha/apps/kaltura/templates/kmclayout.php"
2014-12-10 10:09:19 [0.000482] [10.61.41.125] [363753439] [PS2] [sfRenderingFilter->execute] INFO: {sfFilter} render to client
--
    [line:protected] => 41
    [trace:Exception:private] => Array
        (
--
    [line:protected] => 41
    [trace:Exception:private] => Array
        (
--
2014-12-10 10:09:32 [0.000361] [127.0.0.1] [1398287983] [API] [KalturaStatement->execute] DEBUG: Sql took - 0.00022506713867188 seconds
2014-12-10 10:09:32 [0.001122] [127.0.0.1] [1398287983] [API] [KalturaObject->validateForUsage] ERR: exception 'Exception' with message 'KalturaClipAttributes-offset error: Current user does not have permission to use property "KalturaClipAttributes::offset"' in /opt/kaltura/app/infra/log/KalturaLog.php:82
Stack trace:
#0 /opt/kaltura/app/api_v3/lib/types/KalturaObject.php(678): KalturaLog::err('KalturaClipAttr...')
--
#10 {main}
2014-12-10 10:09:32 [0.000203] [127.0.0.1] [1398287983] [API] [KalturaObject->validateForUsage] ERR: exception 'Exception' with message 'KalturaClipAttributes-duration error: Current user does not have permission to use property "KalturaClipAttributes::duration"' in /opt/kaltura/app/infra/log/KalturaLog.php:82
Stack trace:
#0 /opt/kaltura/app/api_v3/lib/types/KalturaObject.php(678): KalturaLog::err('KalturaClipAttr...')
--
2014-12-10 10:09:33 [0.000343] [127.0.0.1] [1072032967] [API] [KalturaStatement->execute] DEBUG: Sql took - 0.0002288818359375 seconds
2014-12-10 10:09:33 [0.000909] [127.0.0.1] [1072032967] [API] [KalturaObject->validateForUsage] ERR: exception 'Exception' with message 'KalturaClipAttributes-offset error: Current user does not have permission to use property "KalturaClipAttributes::offset"' in /opt/kaltura/app/infra/log/KalturaLog.php:82
Stack trace:
#0 /opt/kaltura/app/api_v3/lib/types/KalturaObject.php(678): KalturaLog::err('KalturaClipAttr...')
--
#10 {main}
2014-12-10 10:09:33 [0.000198] [127.0.0.1] [1072032967] [API] [KalturaObject->validateForUsage] ERR: exception 'Exception' with message 'KalturaClipAttributes-duration error: Current user does not have permission to use property "KalturaClipAttributes::duration"' in /opt/kaltura/app/infra/log/KalturaLog.php:82
Stack trace:
#0 /opt/kaltura/app/api_v3/lib/types/KalturaObject.php(678): KalturaLog::err('KalturaClipAttr...')

/opt/kaltura/bin/kaltura-sanity.sh:

[Space on /] [PASSED, RC: 0] - [.002656567]
[Space on /opt/kaltura/web] [PASSED, RC: 0] - [.002347489]
[Check httpd daemon status] [PASSED, RC: 0] - [.015229242]
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit resta                                                                                                                   rted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit resta                                                                                                                   rted it..
[Check httpd daemon is started by Monit] [PASSED, RC: 0] - [8.320947552]
[check daemon httpd init status] [PASSED, RC: 0] - [.005862759]
[Check kaltura-sphinx daemon status] [PASSED, RC: 0] - [.020743679]
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after mo                                                                                                                   nit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after mo                                                                                                                   nit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after mo                                                                                                                   nit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after mo                                                                                                                   nit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after mo                                                                                                                   nit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after mo                                                                                                                   nit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after mo                                                                                                                   nit restarted it..
[Check kaltura-sphinx daemon is started by Monit] [PASSED, RC: 0] - [7.927841112                                                                                                                   ]
[check daemon kaltura-sphinx init status] [PASSED, RC: 0] - [.006461102]
[Check kaltura-batch daemon status] [PASSED, RC: 0] - [.032660236]
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after mon                                                                                                                   it restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after mon                                                                                                                   it restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after mon                                                                                                                   it restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after mon                                                                                                                   it restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after mon                                                                                                                   it restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after mon                                                                                                                   it restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after mon                                                                                                                   it restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after mon                                                                                                                   it restarted it..
[Check kaltura-batch daemon is started by Monit] [PASSED, RC: 0] - [8.334027745]
[check daemon kaltura-batch init status] [PASSED, RC: 0] - [.003189287]
[Check kaltura-monit daemon status] [PASSED, RC: 0] - [.027174950]
[check daemon kaltura-monit init status] [PASSED, RC: 0] - [.006511660]
[Check memcached daemon status] [PASSED, RC: 0] - [.026024618]
Napping 1 seconds to allow the daemon memcached to finish its init after monit r                                                                                                                   estarted it..
Napping 1 seconds to allow the daemon memcached to finish its init after monit r                                                                                                                   estarted it..
Napping 1 seconds to allow the daemon memcached to finish its init after monit r                                                                                                                   estarted it..
Napping 1 seconds to allow the daemon memcached to finish its init after monit r                                                                                                                   estarted it..
Napping 1 seconds to allow the daemon memcached to finish its init after monit r                                                                                                                   estarted it..
Napping 1 seconds to allow the daemon memcached to finish its init after monit r                                                                                                                   estarted it..
[Check memcached daemon is started by Monit] [PASSED, RC: 0] - [6.289382769]
[check daemon memcached init status] [PASSED, RC: 0] - [.005425725]
[kaltura-html5lib ver in KMC config.ini] [PASSED, RC: 0] - [.066969750]
[kaltura-kdp3 ver in KMC config.ini] [PASSED, RC: 0] - [.060476301]
[kaltura-kmc ver in KMC config.ini] [PASSED, RC: 0] - [.048542614]
[Get KMC SWFs] [PASSED, RC: 0] - [.132318944]
[check_testme_page] [PASSED, RC: 0] - [.110956775]
[check_kmc_index_page] [PASSED, RC: 0] - [.039846762]
[check_admin_console_index_page] [PASSED, RC: 0] - [.159439902]
[check_studio_index_page] [PASSED, RC: 0] - [.742526328]
[Create Partner] [PASSED, RC: 0] - [1.116108954]
[Local dropfolder creation succeeded] [PASSED, RC: 0] - [.213581800]
[Upload content kaltura_logo_animated_blue.flv] [PASSED, RC: 0] - [.582438778]
Napping 10 seconds to allow entry 0_wgctbr2n to digest..
Napping 10 seconds to allow entry 0_wgctbr2n to digest..
Napping 10 seconds to allow entry 0_wgctbr2n to digest..
Napping 10 seconds to allow entry 0_wgctbr2n to digest..
Napping 10 seconds to allow entry 0_wgctbr2n to digest..
Napping 10 seconds to allow entry 0_wgctbr2n to digest..
[kaltura_logo_animated_blue.flv - 0_wgctbr2n status] [PASSED, RC: 0] - [60.676847513]
[Thumb for 0_wgctbr2n identical to /opt/kaltura/bin/kaltura_logo_animated_blue_1_sec.jpg] [PASSED, RC: 0] - [.405937982]
[Clipping 0_wgctbr2n Succeeded] [PASSED, RC: 0] - [.284334353]
[Trimming 0_wgctbr2n Succeeded] [PASSED, RC: 0] - [.294835495]
[Mock playback 0_wgctbr2n succeeded] [PASSED, RC: 0] - [.228023375]
[Entry reconversion of 0_wgctbr2n succeeded] [PASSED, RC: 0] - [.241114787]
Napping 30 seconds to allow mail to be sent out..
[Found an email sending entry for mb-localhost.localdomain@kaltura.com[PID is 104] in /var/log/maillog] [PASSED, RC: 0] - [30.008793133]
Testing analytics, be patient..

Please note: if you are running this test on a clustered ENV, it will fail but this does not mean there is an actual problem.
The tech information as to why is available here:
https://github.com/kaltura/platform-install-packages/issues/106#issuecomment-42837404

[DWH cycle] [PASSED, RC: 0] - [30.300992274]
[Upload content kaltura_logo_animated_green.flv] [PASSED, RC: 0] - [.519430769]
[Upload bulk using CSV] [PASSED, RC: 0] - [.286227331]
[Upload bulk using XML] [PASSED, RC: 0] - [.248948826]
[Create player] [PASSED, RC: 0] - [.135348416]
[Generate thumb] [PASSED, RC: 0] - [.246319136]
[Delete parnter] [PASSED, RC: 0] - [.310916344]
[Red5 file upload] [SKIPPED as OflaDemo isn't configured]

Thanks!

Hello,

Are you requesting KMC by IP or domain? either is fine but it should be the same one you inputted as service_url during the install phase and it should be resolvable from both inside the server and the machine running your browser.

Also, can you use an HTTP sniffer [Chrome dev tools is fine for that] and check what request is failing?
Thanks,

Hi and thanks for your reply.
After checking with firebug I added to my host file.

192.168.1.10  kaltura.local localhost.localdomain

kaltura.local - i believe this was used by the service url, I will use IP in case I reinstall.
localhost.localdomain - dont really know where this came from

Logged in now.
Now the issue is that I installed without SSL but I see that when I log in I’m refereed to port 443?

<h1>Not Found</h1>
<p>The requested URL /index.php/kmc/kmc4 was not found on this server.</p>
<hr>
<address>Apache/2.2.15 (CentOS) Server at 192.168.1.10 Port 443</address>
</body></html>

Thanks,
Alex.

Hello and welcome. Can you post the answer file the installation placed under /tmp/kaltura_*.ans?
Be sure to mask out the passwds in it before pasting.

Thanks

Here it is:
/tmp/kaltura_07_12_13_29.ans

TIME_ZONE="Asia/Jerusalem"
KALTURA_FULL_VIRTUAL_HOST_NAME="localhost.localdomain:80"
KALTURA_VIRTUAL_HOST_NAME="localhost.localdomain"
DB1_HOST="127.0.0.1"
DB1_PORT="3306"
DB1_PASS=""
DB1_NAME="kaltura"
DB1_USER="kaltura"
SERVICE_URL="http://kaltura.local"
SPHINX_SERVER1=“127.0.0.1"
SPHINX_SERVER2=” "
DWH_HOST="127.0.0.1"
DWH_PORT="3306"
SPHINX_DB_HOST="127.0.0.1"
SPHINX_DB_PORT="3306"
ADMIN_CONSOLE_ADMIN_MAIL="alex@
.com"
ADMIN_CONSOLE_PASSWORD="
"
CDN_HOST="kaltura.local"
KALTURA_VIRTUAL_HOST_PORT="80"
SUPER_USER=“root"
SUPER_USER_PASSWD=”***"
ENVIRONMENT_NAME="
Video Education"
DWH_PASS="
********"
PROTOCOL="http"
RED5_HOST="kaltura.local"
USER_CONSENT=“1”

/tmp/kaltura_07_12_13_30.ans

CONFIG_CHOICE="0"
IS_SSL=“N”

Looks perfectly fine.
What is the output for:
apachectl -t -DDUMP_VHOSTS?

1 Like

Here it is:

default:443 localhost.localdomain (/etc/httpd/conf.d/ssl.conf:74)
*:80 localhost.localdomain (/etc/httpd/conf.d/zzzkaltura.conf:1)

cat /etc/httpd/conf.d/zzzkaltura.conf

>     <VirtualHost *:80>
>             ErrorLog "/opt/kaltura/log/kaltura_apache_errors.log"
>             CustomLog /opt/kaltura/log/kaltura_apache_access.log vhost_kalt

>             Include "/opt/kaltura/app/configurations/apache/conf.d/enabled.*.conf"
>     </VirtualHost>

cat /etc/httpd/conf.d/zzzkaltura.conf

<VirtualHost *:80>
        ErrorLog "/opt/kaltura/log/kaltura_apache_errors.log"
        CustomLog /opt/kaltura/log/kaltura_apache_access.log vhost_kalt

        Include "/opt/kaltura/app/configurations/apache/conf.d/enabled.*.conf"
</VirtualHost>
[hercules@localhost ~]$
[hercules@localhost ~]$ cat /etc/httpd/conf.d/ssl.conf
#
# This is the Apache server configuration file providing SSL support.
# It contains the configuration directives to instruct the server how to
# serve pages over an https connection. For detailing information about these
# directives see <URL:http://httpd.apache.org/docs/2.2/mod/mod_ssl.html>
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.
#

LoadModule ssl_module modules/mod_ssl.so

#
# When we also provide SSL we have to listen to the
# the HTTPS port in addition.
#
Listen 443

##
##  SSL Global Context
##
##  All SSL configuration in this context applies both to
##  the main server and all SSL-enabled virtual hosts.
##

#   Pass Phrase Dialog:
#   Configure the pass phrase gathering process.
#   The filtering dialog program (`builtin' is a internal
#   terminal dialog) has to provide the pass phrase on stdout.
SSLPassPhraseDialog  builtin

#   Inter-Process Session Cache:
#   Configure the SSL Session Cache: First the mechanism
#   to use and second the expiring timeout (in seconds).
SSLSessionCache         shmcb:/var/cache/mod_ssl/scache(512000)
SSLSessionCacheTimeout  300

#   Semaphore:
#   Configure the path to the mutual exclusion semaphore the
#   SSL engine uses internally for inter-process synchronization.
SSLMutex default

#   Pseudo Random Number Generator (PRNG):
#   Configure one or more sources to seed the PRNG of the
#   SSL library. The seed data should be of good random quality.
#   WARNING! On some platforms /dev/random blocks if not enough entropy
#   is available. This means you then cannot use the /dev/random device
#   because it would lead to very long connection times (as long as
#   it requires to make more entropy available). But usually those
#   platforms additionally provide a /dev/urandom device which doesn't
#   block. So, if available, use this one instead. Read the mod_ssl User
#   Manual for more details.
SSLRandomSeed startup file:/dev/urandom  256
SSLRandomSeed connect builtin
#SSLRandomSeed startup file:/dev/random  512
#SSLRandomSeed connect file:/dev/random  512
#SSLRandomSeed connect file:/dev/urandom 512

#
# Use "SSLCryptoDevice" to enable any supported hardware
# accelerators. Use "openssl engine -v" to list supported
# engine names.  NOTE: If you enable an accelerator and the
# server does not start, consult the error logs and ensure
# your accelerator is functioning properly.
#
SSLCryptoDevice builtin
#SSLCryptoDevice ubsec

##
## SSL Virtual Host Context
##

<VirtualHost _default_:443>

# General setup for the virtual host, inherited from global configuration
#DocumentRoot "/var/www/html"
#ServerName www.example.com:443

# Use separate log files for the SSL virtual host; note that LogLevel
# is not inherited from httpd.conf.
ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log
LogLevel warn

#   SSL Engine Switch:
#   Enable/Disable SSL for this virtual host.
SSLEngine on

#   SSL Protocol support:
# List the enable protocol levels with which clients will be able to
# connect.  Disable SSLv2 access by default:
SSLProtocol all -SSLv2

#   SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
SSLCipherSuite ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW

#   Server Certificate:
# Point SSLCertificateFile at a PEM encoded certificate.  If
# the certificate is encrypted, then you will be prompted for a
# pass phrase.  Note that a kill -HUP will prompt again.  A new
# certificate can be generated using the genkey(1) command.
SSLCertificateFile /etc/pki/tls/certs/localhost.crt

#   Server Private Key:
#   If the key is not combined with the certificate, use this
#   directive to point at the key file.  Keep in mind that if
#   you've both a RSA and a DSA private key you can configure
#   both in parallel (to also allow the use of DSA ciphers, etc.)
SSLCertificateKeyFile /etc/pki/tls/private/localhost.key

#   Server Certificate Chain:
#   Point SSLCertificateChainFile at a file containing the
#   concatenation of PEM encoded CA certificates which form the
#   certificate chain for the server certificate. Alternatively
#   the referenced file can be the same as SSLCertificateFile
#   when the CA certificates are directly appended to the server
#   certificate for convinience.
#SSLCertificateChainFile /etc/pki/tls/certs/server-chain.crt

#   Certificate Authority (CA):
#   Set the CA certificate verification path where to find CA
#   certificates for client authentication or alternatively one
#   huge file containing all of them (file must be PEM encoded)
#SSLCACertificateFile /etc/pki/tls/certs/ca-bundle.crt

#   Client Authentication (Type):
#   Client certificate verification type and depth.  Types are
#   none, optional, require and optional_no_ca.  Depth is a
#   number which specifies how deeply to verify the certificate
#   issuer chain before deciding the certificate is not valid.
#SSLVerifyClient require
#SSLVerifyDepth  10

#   Access Control:
#   With SSLRequire you can do per-directory access control based
#   on arbitrary complex boolean expressions containing server
#   variable checks and other lookup directives.  The syntax is a
#   mixture between C and Perl.  See the mod_ssl documentation
#   for more details.
#<Location />
#SSLRequire (    %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
#            and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
#            and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
#            and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
#            and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20       ) \
#           or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
#</Location>

#   SSL Engine Options:
#   Set various options for the SSL engine.
#   o FakeBasicAuth:
#     Translate the client X.509 into a Basic Authorisation.  This means that
#     the standard Auth/DBMAuth methods can be used for access control.  The
#     user name is the `one line' version of the client's X.509 certificate.
#     Note that no password is obtained from the user. Every entry in the user
#     file needs this password: `xxj31ZMTZzkVA'.
#   o ExportCertData:
#     This exports two additional environment variables: SSL_CLIENT_CERT and
#     SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
#     server (always existing) and the client (only existing when client
#     authentication is used). This can be used to import the certificates
#     into CGI scripts.
#   o StdEnvVars:
#     This exports the standard SSL/TLS related `SSL_*' environment variables.
#     Per default this exportation is switched off for performance reasons,
#     because the extraction step is an expensive operation and is usually
#     useless for serving static content. So one usually enables the
#     exportation for CGI and SSI requests only.
#   o StrictRequire:
#     This denies access when "SSLRequireSSL" or "SSLRequire" applied even
#     under a "Satisfy any" situation, i.e. when it applies access is denied
#     and no other module can change it.
#   o OptRenegotiate:
#     This enables optimized SSL connection renegotiation handling when SSL
#     directives are used in per-directory context.
#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
<Files ~ "\.(cgi|shtml|phtml|php3?)$">
    SSLOptions +StdEnvVars
</Files>
<Directory "/var/www/cgi-bin">
    SSLOptions +StdEnvVars
</Directory>

#   SSL Protocol Adjustments:
#   The safe and default but still SSL/TLS standard compliant shutdown
#   approach is that mod_ssl sends the close notify alert but doesn't wait for
#   the close notify alert from client. When you need a different shutdown
#   approach you can use one of the following variables:
#   o ssl-unclean-shutdown:
#     This forces an unclean shutdown when the connection is closed, i.e. no
#     SSL close notify alert is send or allowed to received.  This violates
#     the SSL/TLS standard but is needed for some brain-dead browsers. Use
#     this when you receive I/O errors because of the standard approach where
#     mod_ssl sends the close notify alert.
#   o ssl-accurate-shutdown:
#     This forces an accurate shutdown when the connection is closed, i.e. a
#     SSL close notify alert is send and mod_ssl waits for the close notify
#     alert of the client. This is 100% SSL/TLS standard compliant, but in
#     practice often causes hanging connections with brain-dead browsers. Use
#     this only for browsers where you know that their SSL implementation
#     works correctly.
#   Notice: Most problems of broken clients are also related to the HTTP
#   keep-alive facility, so you usually additionally want to disable
#   keep-alive for those clients, too. Use variable "nokeepalive" for this.
#   Similarly, one has to force some clients to use HTTP/1.0 to workaround
#   their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
#   "force-response-1.0" for this.
SetEnvIf User-Agent ".*MSIE.*" \
         nokeepalive ssl-unclean-shutdown \
         downgrade-1.0 force-response-1.0

#   Per-Server Logging:
#   The home of a custom SSL log file. Use this when you want a
#   compact non-error SSL logfile on a virtual host basis.
CustomLog logs/ssl_request_log \
          "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

</VirtualHost>

Can you do:
# curl -I -v $SERVICE_URL/kmc
# curl -I -v $SERVICE_URL/api_v3

Thanks,

curl -I -v $SERVICE_URL/kmc

* About to connect() to kaltura.local port 80 (#0)
*   Trying 127.0.0.1... connected
* Connected to kaltura.local (127.0.0.1) port 80 (#0)
> HEAD /kmc HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.16.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: kaltura.local
> Accept: */*
>
* HTTP 1.0, assume close after body
< HTTP/1.0 200 OK
HTTP/1.0 200 OK
< Date: Thu, 11 Dec 2014 11:56:54 GMT
Date: Thu, 11 Dec 2014 11:56:54 GMT
< Server: Apache/2.2.15 (CentOS)
Server: Apache/2.2.15 (CentOS)
< X-Powered-By: PHP/5.3.3
X-Powered-By: PHP/5.3.3
< X-Kaltura-Session: 200532320
X-Kaltura-Session: 200532320
< Expires: Thu, 19 Nov 1981 08:52:00 GMT
Expires: Thu, 19 Nov 1981 08:52:00 GMT
< Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
< Pragma: no-cache
Pragma: no-cache
< X-Frame-Options: DENY
X-Frame-Options: DENY
< Vary: Accept-Encoding
Vary: Accept-Encoding
< X-Me: localhost.localdomain
X-Me: localhost.localdomain
< Connection: close
Connection: close
< Content-Type: text/html; charset=utf-8
Content-Type: text/html; charset=utf-8

curl -I -v $SERVICE_URL/api_v3

* About to connect() to kaltura.local port 80 (#0)
*   Trying 127.0.0.1... connected
* Connected to kaltura.local (127.0.0.1) port 80 (#0)
> HEAD /api_v3 HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.16.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: kaltura.local
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
HTTP/1.1 301 Moved Permanently
< Date: Thu, 11 Dec 2014 11:59:38 GMT
Date: Thu, 11 Dec 2014 11:59:38 GMT
< Server: Apache/2.2.15 (CentOS)
Server: Apache/2.2.15 (CentOS)
< Location: http://kaltura.local/api_v3/
Location: http://kaltura.local/api_v3/
< Connection: close
Connection: close
< Content-Type: text/html; charset=iso-8859-1
Content-Type: text/html; charset=iso-8859-1

<
* Closing connection #0

Reinstalled from scratch. Used IP during installtion on all question: Can login but this is what I have in kallog:

2014-12-12 19:34:54 [0.000207] [10.62.70.149] [2014087547] [PS2] [sfView->initialize] INFO: {sfView} initialize view for "kmc/kmc1"
2014-12-12 19:34:54 [0.000416] [10.62.70.149] [2014087547] [PS2] [sfPHPView->renderFile] INFO: {sfView} render "/opt/kaltura/app/alpha/apps/kaltura/modules/kmc/templates/kmc1Success.php"
2014-12-12 19:34:54 [0.001018] [10.62.70.149] [2014087547] [PS2] [sfPHPView->decorate] INFO: {sfView} decorate content with "/opt/kaltura/app/alpha/apps/kaltura/templates/kmc1layout.php"
2014-12-12 19:34:54 [0.000133] [10.62.70.149] [2014087547] [PS2] [sfPHPView->renderFile] INFO: {sfView} render "/opt/kaltura/app/alpha/apps/kaltura/templates/kmc1layout.php"
2014-12-12 19:34:54 [0.000599] [10.62.70.149] [2014087547] [PS2] [sfRenderingFilter->execute] INFO: {sfFilter} render to client
--
2014-12-12 19:10:00 [394920937] [addPermissionsAndItems.php] [addItemToPermissions] ALERT: exception 'Exception' with message 'ERROR - Permission name [] for partner [0] not found in database - skipping!' in /opt/kaltura/app/infra/log/KalturaLog.php:64
Stack trace:
#0 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(280): KalturaLog::alert('ERROR - Permiss...')

This seems OK, are you still having any issues? and also, can you run:
# /opt/kaltura/bin/kaltura-sanity.sh
to ensure everything passes correctly?

Have this when I log in with my user and password:

http://screencast.com/t/HDZc7QE8q

And the screeen is empty:

Several things failed:

    [Space on /] [PASSED, RC: 0] - [.020507234]
[Space on /opt/kaltura/web] [PASSED, RC: 0] - [.012435346]
[Check httpd daemon status] [PASSED, RC: 0] - [.083575307]
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
[Check httpd daemon is started by Monit] [PASSED, RC: 0] - [3.530012822]
[check daemon httpd init status] [PASSED, RC: 0] - [.003468673]
[Check kaltura-sphinx daemon status] [PASSED, RC: 0] - [.105854174]
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
[Check kaltura-sphinx daemon is started by Monit] [PASSED, RC: 0] - [7.040588661]
[check daemon kaltura-sphinx init status] [PASSED, RC: 0] - [.023309051]
[Check kaltura-batch daemon status] [PASSED, RC: 0] - [.114961712]
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
[Check kaltura-batch daemon is started by Monit] [PASSED, RC: 0] - [6.301828413]
[check daemon kaltura-batch init status] [PASSED, RC: 0] - [.003467095]
[Check kaltura-monit daemon status] [PASSED, RC: 0] - [.014856080]
[check daemon kaltura-monit init status] [PASSED, RC: 0] - [.003117246]
[Check memcached daemon status] [PASSED, RC: 0] - [.014317051]
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
[Check memcached daemon is started by Monit] [PASSED, RC: 0] - [6.256682808]
[check daemon memcached init status] [PASSED, RC: 0] - [.004575496]
[kaltura-html5lib ver in KMC config.ini] [PASSED, RC: 0] - [.054144674]
[kaltura-kdp3 ver in KMC config.ini] [PASSED, RC: 0] - [.031790921]
[kaltura-kmc ver in KMC config.ini] [PASSED, RC: 0] - [.035029931]
PHP Warning:  file_get_contents(10.168.251.14/kmc): failed to open stream: No such file or directory in /opt/kaltura/bin/get_kmc_swfs.php on line 9
[Get KMC SWFs] [FAILED, RC: 255] - [.161152408]
[check_testme_page] [PASSED, RC: 0] - [.154975941]
[check_kmc_index_page] [PASSED, RC: 0] - [.028621015]
[check_admin_console_index_page] [PASSED, RC: 0] - [.307249069]
[check_studio_index_page] [PASSED, RC: 0] - [.770241554]
[Create Partner] [PASSED, RC: 0] - [1.062100400]
[Local dropfolder creation succeeded] [PASSED, RC: 0] - [.205611076]
[Upload content kaltura_logo_animated_blue.flv] [PASSED, RC: 0] - [.500152932]
Napping 10 seconds to allow entry 0_dtkbgkpt to digest..
Napping 10 seconds to allow entry 0_dtkbgkpt to digest..
Napping 10 seconds to allow entry 0_dtkbgkpt to digest..
Napping 10 seconds to allow entry 0_dtkbgkpt to digest..
Napping 10 seconds to allow entry 0_dtkbgkpt to digest..
Napping 10 seconds to allow entry 0_dtkbgkpt to digest..
Napping 10 seconds to allow entry 0_dtkbgkpt to digest..
Napping 10 seconds to allow entry 0_dtkbgkpt to digest..
Napping 10 seconds to allow entry 0_dtkbgkpt to digest..
[kaltura_logo_animated_blue.flv - 0_dtkbgkpt status] [FAILED, RC: 1] - [-.760560991]
Napping 30 seconds to allow mail to be sent out..
[Found an email sending entry for mb-localhost.localdomain@kaltura.com[PID is 102] in /var/log/maillog] [PASSED, RC: 0] - [30.036224667]
Testing analytics, be patient..

Please note: if you are running this test on a clustered ENV, it will fail but this does not mean there is an actual problem.
The tech information as to why is available here:
https://github.com/kaltura/platform-install-packages/issues/106#issuecomment-42837404

[DWH cycle] [PASSED, RC: 0] - [44.979206417]
[Upload content kaltura_logo_animated_green.flv] [PASSED, RC: 0] - [.420621200]
[Upload bulk using CSV] [PASSED, RC: 0] - [.379392130]
[Upload bulk using XML] [PASSED, RC: 0] - [.194908147]
[Create player] [PASSED, RC: 0] - [.129882900]
[Generate thumb] [PASSED, RC: 0] - [.183206274]
[Delete parnter] [PASSED, RC: 0] - [.287851982]
[Red5 file upload] [SKIPPED as OflaDemo isn't configured]
see: https://github.com/kaltura/platform-install-packages/blob/master/doc/install-kaltura-redhat-based.md#configure-red5-server


Thank you for running Kaltura! To keep Kaltura viable, stable and well tested, please join the community and help by contributing sanity tests that verify overall platform stability: http://bit.ly/kaltura-ci , and by contributing to the project roadmap by solving simple tasks and challenges: http://bit.ly/kaltura-tasks.

Hi,

While trying to login, use an HTTP sniffer [you can use your browser’s dev tools for it] to see which call is failing.
Also, from the server run:
# kaltlog
To see the errors generated by the request.

kaltlog

[root@localhost ~]# kaltlog
2014-12-15 08:25:32 [0.000193] [10.61.40.126] [864604672] [PS2] [sfView->initialize] INFO: {sfView} initialize view for "kmc/kmc1"
2014-12-15 08:25:32 [0.000389] [10.61.40.126] [864604672] [PS2] [sfPHPView->renderFile] INFO: {sfView} render "/opt/kaltura/app/alpha/apps/kaltura/modules/kmc/templates/kmc1Success.php"
2014-12-15 08:25:32 [0.000860] [10.61.40.126] [864604672] [PS2] [sfPHPView->decorate] INFO: {sfView} decorate content with "/opt/kaltura/app/alpha/apps/kaltura/templates/kmc1layout.php"
2014-12-15 08:25:32 [0.000096] [10.61.40.126] [864604672] [PS2] [sfPHPView->renderFile] INFO: {sfView} render "/opt/kaltura/app/alpha/apps/kaltura/templates/kmc1layout.php"
2014-12-15 08:25:32 [0.000544] [10.61.40.126] [864604672] [PS2] [sfRenderingFilter->execute] INFO: {sfFilter} render to client
--
2014-12-15 08:12:45 [655382605] [addPermissionsAndItems.php] [addItemToPermissions] ALERT: exception 'Exception' with message 'ERROR - Permission name [] for partner [0] not found in database - skipping!' in /opt/kaltura/app/infra/log/KalturaLog.php:64
Stack trace:
#0 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(280): KalturaLog::alert('ERROR - Permiss...')
--
2014-12-15 08:28:07 [0.000235] [10.61.40.126] [503511992] [PS2] [sfView->initialize] INFO: {sfView} initialize view for "kmc/kmc1"
2014-12-15 08:28:07 [0.000443] [10.61.40.126] [503511992] [PS2] [sfPHPView->renderFile] INFO: {sfView} render "/opt/kaltura/app/alpha/apps/kaltura/modules/kmc/templates/kmc1Success.php"
2014-12-15 08:28:07 [0.001252] [10.61.40.126] [503511992] [PS2] [sfPHPView->decorate] INFO: {sfView} decorate content with "/opt/kaltura/app/alpha/apps/kaltura/templates/kmc1layout.php"
2014-12-15 08:28:07 [0.000134] [10.61.40.126] [503511992] [PS2] [sfPHPView->renderFile] INFO: {sfView} render "/opt/kaltura/app/alpha/apps/kaltura/templates/kmc1layout.php"
2014-12-15 08:28:07 [0.000665] [10.61.40.126] [503511992] [PS2] [sfRenderingFilter->execute] INFO: {sfFilter} render to client

Anything else we can do?

Hi, Alex.

I got the same issue in CentOS 6. I hope some one here who has resolved this issue could help us.

I have not resolved this issue yet. But find some related threads listing here.

http://www.kaltura.org/blank-page-after-login-and-invalid-ks

Finally, I found the issue was caused by I login in with Admin User. When I change to Admin console and created a new publisher account to login. It works.
Hope this could help you.

Hi all
For me the scenario was a local guest and under 192.168.122.0 subnet, which in my laptop had a etc/hosts local resolution.
Once I transfered the VM to another stable server host and the kaltura VM configured to bridge to network , I completely lost the kmc with the error regarding the flash-plugin installation.
Based on Jess input and defining the DNS all became fine by browsing by name
Thanks and may this help other people

Host/guests are both Centos 6.6 64 bit.