Quantcast
Viewing all articles
Browse latest Browse all 7410

Problems installing Kaltura CE on ubuntu 14.x

Still no luck.

Here is my ans file:

local TZ to be used by PHP code. Note that it MUST be the same as your DB TZ.

TIME_ZONE="America/New_York"

Apache port

KALTURA_VIRTUAL_HOST_PORT="443"
KALTURA_VIRTUAL_HOST_NAME="54.174.227.99"

host and port

KALTURA_FULL_VIRTUAL_HOST_NAME="$KALTURA_VIRTUAL_HOST_NAME:$KALTURA_VIRTUAL_HOST_PORT"

operational DB user and passwd

DB1_NAME="kaltura"
DB1_USER="kaltura"
PROTOCOL="https"
SERVICE_URL="$PROTOCOL://$KALTURA_FULL_VIRTUAL_HOST_NAME"
SPHINX_SERVER1="127.0.0.1"
SPHINX_SERVER2=" "
SPHINX_DB_HOST="127.0.0.1"
SPHINX_DB_PORT="3306"

user name for the Kaltura Admin Console, MUST be in the form of an email

ADMIN_CONSOLE_ADMIN_MAIL="timothy.roberts@ymail.com"

passwd for the Kaltura Admin Console

ADMIN_CONSOLE_PASSWORD="blackstrawberry"

for installs that have no remote CDN storage, use the same as $KALTURA_VIRTUAL_HOST_NAME

CDN_HOST="$KALTURA_VIRTUAL_HOST_NAME"

display name used when sending the 'welcome' mail.

ENVIRONMENT_NAME="Kaltura Video Platform"

what web I/F would you want to enable, options:

0 - All web interfaces

1 - Kaltura Management Console [KMC], Hosted Apps, HTML5 lib and ClipAp

2 - KAC - Kaltura Admin Console

CONFIG_CHOICE="0"

are we working over SSL? needed since, if so, we perform cert validity checks

IS_SSL="N"

hostname for Red5

RED5_HOST="127.0.0.1"

allow the install scripts to send install data for analytics and support purposes:

1 - allow

0 - prevent

USER_CONSENT=1

SSL cert path

CRT_FILE=/etc/ssl/certs/localhost.crt

SSL key path

KEY_FILE=/etc/pki/tls/private/localhost.key

if such exists enter path here, otherwise leave as is.

CHAIN_FILE=NONE

Operational DB MySQL

DB1_HOST="127.0.0.1"

MySQL PORT

DB1_PORT="3306"

desired passwd, make it good.

DB1_PASS="KALT_DB_PASS"

analytics MySQL DB

DWH_HOST="127.0.0.1"

analytics MySQL port

DWH_PORT="80"

analytics MySQL port

DWH_PASS="80"

MySQL super user, this is only used for bootstrap, the app itself will not connect with it.

SUPER_USER="root"
SUPER_USER_PASSWD="MYSQL_SUPER_USER_PASSWD"

For nginx packager module

VOD_PACKAGER_HOST="127.0.0.1"
VOD_PACKAGER_PORT="8080"

whether or not to configure Nginx over SSL

IS_NGINX_SSL="N"

path to SSL cert

SSL_CERT

path to SSL key

SSL_KEY

NGINX SSL PORT - note, if you have Apache running over SSL as well and on port 443, do not select 443 here too

VOD_PACKAGER_SSL_PORT=8443

WWW_HOST="127.0.0.1"

Range of ip addresses belonging to internal kaltura servers

The range is used when checking service actions permissions and allowing to access certain services without KS from the internal servers.

The default is only good for testing, on a production ENV you should adjust according to your network.

IP_RANGE="0.0.0.0-255.255.255.255"

=======================

Here is my error:
ERROR: Couldn't make an API request to (http)://54.174.227.99:443/api_v3/index.php?service=system&action=ping.
Please check your setup and then run /opt/kaltura/bin/kaltura-db-config.sh again.

=========

root@ip-172-31-59-69:~# curl -I -v https://54.174.227.99:443/api_v3/index.php?service=system&action=ping
[1] 833
root@ip-172-31-59-69:~# * Hostname was NOT found in DNS cache
* Trying 54.174.227.99...
* Connected to 54.174.227.99 (54.174.227.99) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS alert, Server hello (2):
* SSL certificate problem: unable to get local issuer certificate
* Closing connection 0
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.


Viewing all articles
Browse latest Browse all 7410

Trending Articles